#evitadb — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #evitadb, aggregated by home.social.
-
In the last release of #evitaDB, we shipped change data capture. From now on, you can connect your application to the database's change stream via gRPC, GraphQL, or REST APIs. If you're curious about how CDC works behind the scenes, check out our blog post: https://evitadb.io/blog/20-change-data-capture
Kudos to our team and namely Lukáš Hornych for breaking the GQL/REST implementation barrier!
-
In the last release of #evitaDB, we shipped change data capture. From now on, you can connect your application to the database's change stream via gRPC, GraphQL, or REST APIs. If you're curious about how CDC works behind the scenes, check out our blog post: https://evitadb.io/blog/20-change-data-capture
Kudos to our team and namely Lukáš Hornych for breaking the GQL/REST implementation barrier!
-
In the last release of #evitaDB, we shipped change data capture. From now on, you can connect your application to the database's change stream via gRPC, GraphQL, or REST APIs. If you're curious about how CDC works behind the scenes, check out our blog post: https://evitadb.io/blog/20-change-data-capture
Kudos to our team and namely Lukáš Hornych for breaking the GQL/REST implementation barrier!
-
The Java API of #evitaDB supports both the old synchronous approach and the new reactive approach. We've recently published an article about this feature related to transaction handling in #evitaDB. You can easily observe when your changes are propagated to the shared view (or the cluster-wide view) in your client, regardless of whether you use an embedded database or communicate with a remote database instance via gRPC.
Warning: you will need some prior IT knowledge to understand the article 🫣
-
The Java API of #evitaDB supports both the old synchronous approach and the new reactive approach. We've recently published an article about this feature related to transaction handling in #evitaDB. You can easily observe when your changes are propagated to the shared view (or the cluster-wide view) in your client, regardless of whether you use an embedded database or communicate with a remote database instance via gRPC.
Warning: you will need some prior IT knowledge to understand the article 🫣
-
The Java API of #evitaDB supports both the old synchronous approach and the new reactive approach. We've recently published an article about this feature related to transaction handling in #evitaDB. You can easily observe when your changes are propagated to the shared view (or the cluster-wide view) in your client, regardless of whether you use an embedded database or communicate with a remote database instance via gRPC.
Warning: you will need some prior IT knowledge to understand the article 🫣
-
Java runs on every platform. But does your application built on the JVM? You can't be completely sure unless you test it, and test it regularly. From now on, #evitaDB runs all its tests on a weekly basis for all 3 major OS architectures.
So the answer to the question in the title is no - #evitaDB could have had problems running on anything other than Linux. But not anymore! 🎉
-
Java runs on every platform. But does your application built on the JVM? You can't be completely sure unless you test it, and test it regularly. From now on, #evitaDB runs all its tests on a weekly basis for all 3 major OS architectures.
So the answer to the question in the title is no - #evitaDB could have had problems running on anything other than Linux. But not anymore! 🎉
-
Java runs on every platform. But does your application built on the JVM? You can't be completely sure unless you test it, and test it regularly. From now on, #evitaDB runs all its tests on a weekly basis for all 3 major OS architectures.
So the answer to the question in the title is no - #evitaDB could have had problems running on anything other than Linux. But not anymore! 🎉
-
29. února 2024 budeme přednášet o #evitaDB na pravidelném setkání Google Developer Group v Jihlavě - jste srdečně zváni! https://talkbase.io/event/evitadb-rychla-databaze-pro-e-commerce/gugcz
-
29. února 2024 budeme přednášet o #evitaDB na pravidelném setkání Google Developer Group v Jihlavě - jste srdečně zváni! https://talkbase.io/event/evitadb-rychla-databaze-pro-e-commerce/gugcz
-
29. února 2024 budeme přednášet o #evitaDB na pravidelném setkání Google Developer Group v Jihlavě - jste srdečně zváni! https://talkbase.io/event/evitadb-rychla-databaze-pro-e-commerce/gugcz
-
29. února 2024 budeme přednášet o #evitaDB na pravidelném setkání Google Developer Group v Jihlavě - jste srdečně zváni! https://talkbase.io/event/evitadb-rychla-databaze-pro-e-commerce/gugcz
-
29. února 2024 budeme přednášet o #evitaDB na pravidelném setkání Google Developer Group v Jihlavě - jste srdečně zváni! https://talkbase.io/event/evitadb-rychla-databaze-pro-e-commerce/gugcz
-
Two weeks ago I promised a blog post about the process we use for automating code samples verification in our #evitaDB documentation and now I'm keeping that promise.
The approach described, which takes advantage of #JUnit5 dynamic testing and #JShell REPL, looks like a novel approach. I haven't been able to Google any other project that documents something similar.
So if you have a similar use case, read on and get inspired.
-
The documentation on #evitaDB https://evitadb.io/documentation/index is getting bigger and bigger. The more examples we add, the more we're afraid they'll become obsolete or broken. How do we tame this beast of hundreds of examples?
Fortunately, #Java provides a JShell REPL that allows you to interactively enter, and run Java source code. The JShell can also be run automatically and #JUnit5 allows to create dynamic tests. Combining these two features we've created an automated test suite. Blog post coming.
-
How to calculate and render the four most common catalog menu styles using #evitaDB is explained in this article: https://evitadb.io/documentation/solve/render-category-menu
Hard things don't have to be that hard.
-
How to calculate and render the four most common catalog menu styles using #evitaDB is explained in this article: https://evitadb.io/documentation/solve/render-category-menu
Hard things don't have to be that hard.
-
How to calculate and render the four most common catalog menu styles using #evitaDB is explained in this article: https://evitadb.io/documentation/solve/render-category-menu
Hard things don't have to be that hard.
-
The development of our web studio #evitaLab for #evitaDB has undergone significant enhancements and expansions in the last six months. My colleague (and its author) Lukáš Hornych has summarized them in a new blog post: https://evitadb.io/blog/12-evitalab-after-6-months
-
The development of our web studio #evitaLab for #evitaDB has undergone significant enhancements and expansions in the last six months. My colleague (and its author) Lukáš Hornych has summarized them in a new blog post: https://evitadb.io/blog/12-evitalab-after-6-months
-
The development of our web studio #evitaLab for #evitaDB has undergone significant enhancements and expansions in the last six months. My colleague (and its author) Lukáš Hornych has summarized them in a new blog post: https://evitadb.io/blog/12-evitalab-after-6-months
-
🎉 We have big news for you today. evitaDB has its official web console called evitaLab. It allows you to browse data in evitaDB, inspect schemas, try out your queries. Read about the cool features it has:
https://evitadb.io/blog/09-our-new-web-client-evitalab
At the moment it's a read-only tool, but we have plans to change that in the foreseeable future. Big thanks to the team behind this tool: Lukáš Hornych, Miroslav Alt and Lukáš Sucharda for graphic design.
-
🎉 We have big news for you today. evitaDB has its official web console called evitaLab. It allows you to browse data in evitaDB, inspect schemas, try out your queries. Read about the cool features it has:
https://evitadb.io/blog/09-our-new-web-client-evitalab
At the moment it's a read-only tool, but we have plans to change that in the foreseeable future. Big thanks to the team behind this tool: Lukáš Hornych, Miroslav Alt and Lukáš Sucharda for graphic design.
-
🎉 We have big news for you today. evitaDB has its official web console called evitaLab. It allows you to browse data in evitaDB, inspect schemas, try out your queries. Read about the cool features it has:
https://evitadb.io/blog/09-our-new-web-client-evitalab
At the moment it's a read-only tool, but we have plans to change that in the foreseeable future. Big thanks to the team behind this tool: Lukáš Hornych, Miroslav Alt and Lukáš Sucharda for graphic design.
-
🎉 We have big news for you today. evitaDB has its official web console called evitaLab. It allows you to browse data in evitaDB, inspect schemas, try out your queries. Read about the cool features it has:
https://evitadb.io/blog/09-our-new-web-client-evitalab
At the moment it's a read-only tool, but we have plans to change that in the foreseeable future. Big thanks to the team behind this tool: Lukáš Hornych, Miroslav Alt and Lukáš Sucharda for graphic design.
-
Jak řešíte analýzu zpětné kompatibility REST / GraphQL API? Máte na to nějaké nástroje a automatizaci v rámci CI/CD pipeline, která vám odhalí, že API v nové verzi aplikace není zpětně kompatibilní s předchozí verzí?!
Podělte se o zkušenosti. V souvislosti s #evitaDB řešíme v issue https://github.com/FgForrest/evitaDB/issues/219
-
Jak řešíte analýzu zpětné kompatibility REST / GraphQL API? Máte na to nějaké nástroje a automatizaci v rámci CI/CD pipeline, která vám odhalí, že API v nové verzi aplikace není zpětně kompatibilní s předchozí verzí?!
Podělte se o zkušenosti. V souvislosti s #evitaDB řešíme v issue https://github.com/FgForrest/evitaDB/issues/219
-
Jak řešíte analýzu zpětné kompatibility REST / GraphQL API? Máte na to nějaké nástroje a automatizaci v rámci CI/CD pipeline, která vám odhalí, že API v nové verzi aplikace není zpětně kompatibilní s předchozí verzí?!
Podělte se o zkušenosti. V souvislosti s #evitaDB řešíme v issue https://github.com/FgForrest/evitaDB/issues/219
-
Jak řešíte analýzu zpětné kompatibility REST / GraphQL API? Máte na to nějaké nástroje a automatizaci v rámci CI/CD pipeline, která vám odhalí, že API v nové verzi aplikace není zpětně kompatibilní s předchozí verzí?!
Podělte se o zkušenosti. V souvislosti s #evitaDB řešíme v issue https://github.com/FgForrest/evitaDB/issues/219
-
Na JavaDays '23 (https://www.javadays.cz/cs/) pořádané GOPAS budu ukazovat, jak vám #evitaDB pomůže zkrotit požadavky webových katalogů v e-commerce oblasti nebo i mimo ni. Facetové filtrování, hierarchické struktury, cenové vyhledávání, lokalizace, rozsahové vyhledávání okamžitě připravené k dotazování jak pro backendisty (#Java, #CSharp, #gRPC), tak frontendový tým přes #GraphQL, #REST.
-
Na JavaDays '23 (https://www.javadays.cz/cs/) pořádané GOPAS budu ukazovat, jak vám #evitaDB pomůže zkrotit požadavky webových katalogů v e-commerce oblasti nebo i mimo ni. Facetové filtrování, hierarchické struktury, cenové vyhledávání, lokalizace, rozsahové vyhledávání okamžitě připravené k dotazování jak pro backendisty (#Java, #CSharp, #gRPC), tak frontendový tým přes #GraphQL, #REST.
-
Na JavaDays '23 (https://www.javadays.cz/cs/) pořádané GOPAS budu ukazovat, jak vám #evitaDB pomůže zkrotit požadavky webových katalogů v e-commerce oblasti nebo i mimo ni. Facetové filtrování, hierarchické struktury, cenové vyhledávání, lokalizace, rozsahové vyhledávání okamžitě připravené k dotazování jak pro backendisty (#Java, #CSharp, #gRPC), tak frontendový tým přes #GraphQL, #REST.
-
Two weeks ago I promised a blog post about the process we use for automating code samples verification in our #evitaDB documentation and now I'm keeping that promise.
The approach described, which takes advantage of #JUnit5 dynamic testing and #JShell REPL, looks like a novel approach. I haven't been able to Google any other project that documents something similar.
So if you have a similar use case, read on and get inspired.
-
Two weeks ago I promised a blog post about the process we use for automating code samples verification in our #evitaDB documentation and now I'm keeping that promise.
The approach described, which takes advantage of #JUnit5 dynamic testing and #JShell REPL, looks like a novel approach. I haven't been able to Google any other project that documents something similar.
So if you have a similar use case, read on and get inspired.
-
The documentation on #evitaDB https://evitadb.io/documentation/index is getting bigger and bigger. The more examples we add, the more we're afraid they'll become obsolete or broken. How do we tame this beast of hundreds of examples?
Fortunately, #Java provides a JShell REPL that allows you to interactively enter, and run Java source code. The JShell can also be run automatically and #JUnit5 allows to create dynamic tests. Combining these two features we've created an automated test suite. Blog post coming.
-
The documentation on #evitaDB https://evitadb.io/documentation/index is getting bigger and bigger. The more examples we add, the more we're afraid they'll become obsolete or broken. How do we tame this beast of hundreds of examples?
Fortunately, #Java provides a JShell REPL that allows you to interactively enter, and run Java source code. The JShell can also be run automatically and #JUnit5 allows to create dynamic tests. Combining these two features we've created an automated test suite. Blog post coming.
-
The documentation on #evitaDB https://evitadb.io/documentation/index is getting bigger and bigger. The more examples we add, the more we're afraid they'll become obsolete or broken. How do we tame this beast of hundreds of examples?
Fortunately, #Java provides a JShell REPL that allows you to interactively enter, and run Java source code. The JShell can also be run automatically and #JUnit5 allows to create dynamic tests. Combining these two features we've created an automated test suite. Blog post coming.
-
The documentation on #evitaDB https://evitadb.io/documentation/index is getting bigger and bigger. The more examples we add, the more we're afraid they'll become obsolete or broken. How do we tame this beast of hundreds of examples?
Fortunately, #Java provides a JShell REPL that allows you to interactively enter, and run Java source code. The JShell can also be run automatically and #JUnit5 allows to create dynamic tests. Combining these two features we've created an automated test suite. Blog post coming.
-
Why did we choose @RedHat #Undertow server for #evitaDB web APIs (GraphQL/REST)?
It has a decent performance, nice API and is easy to embed. Read more about our testing and conclusions in the blog post: https://evitadb.io/blog/03-choosing-http-server
-
Why did we choose @RedHat #Undertow server for #evitaDB web APIs (GraphQL/REST)?
It has a decent performance, nice API and is easy to embed. Read more about our testing and conclusions in the blog post: https://evitadb.io/blog/03-choosing-http-server
-
Why did we choose @RedHat #Undertow server for #evitaDB web APIs (GraphQL/REST)?
It has a decent performance, nice API and is easy to embed. Read more about our testing and conclusions in the blog post: https://evitadb.io/blog/03-choosing-http-server