Blog

Native soft-delete support in evitaDB simplifies application data models, enhances performance, and reduces complexity by handling archived entities directly within the database.

We're excited to introduce a powerful new feature in evitaDB — the priceDiscount ordering constraint. This feature allows you to sort your product listings based on the discount amount, helping you highlight the best deals to your customers. In this post, we'll explore how to use this feature effectively, with real-world examples, practical query snippets, and insights into different pricing strategies, including handling products with variants and product sets.

evitaDB started its journey with the Undertow server from JBoss. It was chosen because of its performance and ease of use. However, due to the gRPC API, we still had to run a separate Netty server under the hood. This was far from ideal, and we hoped that with Undertow 3.0, which promised to move to Netty, we could unify all APIs under one server. Unfortunately, the development of Undertow 3.0 has not progressed in years and we had to look for alternatives.

evitaLab is still being actively developed alongside evitaDB and there are many new features that are worth mentioning. There are features for learning evitaDB as well as for debugging data.

I have always used the semantic versioning (SemVer) scheme for my projects. However, after discussing with my friend Lukáš Hornych and conducting further research with the team, we have decided to change the versioning scheme for evitaDB. The new scheme will be a Calendar Versioning. If you are interested in following our debate, read on.

A lot has happened this year - and a lot is being prepared for next year. For those who want to follow the development of the project, we have prepared a summary of the most important events of the year 2023 and a brief overview of the plans for next year.

It's always a bit painful to troubleshoot a problem with your production data inside a database if you don't have a handy tool to look inside easily, and instead, you have to write different kinds of queries using different tools to get the information that you need. We feel the same way. That's why we've created a hopefully handy GUI client for evitaDB called evitaLab, so you have a buddy when you're either just playing with evitaDB or you're already debugging production data.

This article is a continuation of a series of articles about the documentation portal of our database. This time we will look at it from a different point of view - from the perspective of the developer who creates the documentation, and whose interest is that the documentation written is correct and does not become outdated over time.

The documentation on evitaDB site is getting bigger and bigger. The more examples we add, the more we're afraid they will become obsolete or broken. How do we tame this beast of hundreds of examples?

A fast test suite is a critical aspect that motivates developers to write more tests and run the suite frequently. The ideal test suite should finish in a matter of seconds or low units of minutes.