How to calculate and render the four most common catalog menu styles using #evitaDB is explained in this article: evitadb.io/documentation/… Hard things don't have to be that hard.

On February 29, our team will be speaking at the Google Developer Group in Jihlava - you're welcome! talkbase.io/event/evitadb-…

Conditional directives in DB query language seems like a good idea: github.com/FgForrest/evit… We could avoid some roundtrips between client and server. It's kind of like CASE statements in relational databases, but with GraphQL it could be quite powerful.

Most of the transactional system is now rewritten to SNAPSHOT isolation with proper WAL, which opens the door to change data capture, cluster replication, time machine, and many other cool things to come. But it takes another month to get it to the `dev` / `master` branch.

Another database (Redis) switches to a similar licensing model to evitaDB: redis.com/blog/redis-ado…

The third part of the series about evitaDB was published on Root.cz. This time about evitaQL. Article is available in Czech only: root.cz/clanky/evitadb…

Our presentation from the OpenAlt conference in Brno 2023 is finally online: youtu.be/J2RBSIHlt4U?si… ... if you weren't there and didn't see any of our talks, you're welcome to do so.

evitaDB 2024.4 has a proper multi-version concurrency control implementation that provides SNAPSHOT isolation for all your sessions. We have also integrated OpenTelemetry so that you can view evitaDB queries in your overall application traces. Read more: github.com/FgForrest/evit…

We're migrating from #JBoss #Undertow to the Armeria web server in the next `2014.10` release. You can read more about the reasons in our blog post evitadb.io/blog/13-migrat… We can say now that the Armeria team has welcomed us warmly and we're happy to make the change.

Soft-delete is a commonly used technique that has no direct support in most database systems. This fact forces developers to handle it at the service layer, which makes both the model and the application code more complex and error-prone. But why? evitadb.io/blog/15-soft-d…

Developer experience is key when adopting new technology. To solve multiple problems, we introduced a traffic recording prototype that logs queries, mutations and other requests on database. How it can help developers read here: evitadb.io/blog/16-traffi…

B-trees may be decades old, but we still use them extensively in CedarDB. Read our latest blog post to learn how to scale B-tree operations to hundreds of cores. cedardb.com/blog/optimisti…

New version `2025.2` released. New features described in release notes: github.com/FgForrest/evit… There is a lot of news: - ordering, paging, segmentation, spacing by 1:N references - hierarchy entities support in facets - enhancement for containerized environments and more ...

So simple and common, those "one to many" relations are, and yet they can be a source of frustration for developers. Not to mention, when we entangle the organization of referenced entities into tree structures, that's when the real hell starts. evitadb.io/blog/17-one-to…

The data layer of @evitaDB allows you to have: - built-in data compression - run-time file copy backups - access to old versions of data - point-in-time backup & recovery of your data. All these features are covered in the following article: evitadb.io/documentation/…

evitaLab has been packaged into a standalone Electron application. The reasons behind this decision and how it benefits us and simplifies the tool development are described by Lukáš Hornych in a new blog post: evitadb.io/blog/18-introd…

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 evitadb.io/blog/19-transa…

In newly released version of evitaDB `2025.4` we bring compression to the data storage layer. Impact still needs to be evaluated (currently disabled by default), but could be significant. Release details: github.com/FgForrest/evit…

In the last release of #evitaDB, we shipped change data capture. From now on, you can connect your application to the DB'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: evitadb.io/blog/20-change…

evitaDB had 8 milestone releases this year and gained a number of new interesting features. We offer you a brief summary of them and also a preview of our plans for the coming year. evitadb.io/blog/21-year-2… Enjoy reading, and happy New Year!