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 🫣
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! 🎉
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.
We visited "nerdy" conference @openalt in Brno, which took place on 11. - 12. November. The picture features Lukáš Hornych and me in the background supporting him.
When the lecture is online, we will share it with you. #evitaDB
🎉 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
Jan Novotný ♥️🇺🇦
