Fast and Slow

The project

When using data provided by others, you will most likely not find the right API to do so. You try to solve this by making a replication of all the data and thus create a replication hell. This not only makes it hard to maintain, but for evolving datasets also makes the data outdated quickly, leading to a huge integration cost for the developer that uses multiple datasets.

The solution to this is making use of event streams. Querying these event streams directly will be fast only for simple questions such as asking for the last few events. In order to allow third parties to also have faster response times for any other query, we need to balance maintenance costs and query performance. This can be done by selecting the right fragmentation strategies for a specific event stream.

This project allows intermediaries to configure the right fragmentation strategy!

Query interface

We also provided a query interface that allow users to execute sparql queries on the fragmentations that are created using admin interface. This allows them to see the difference in performance between different fragmentation strategies on the properties in the event streams.