👾 An Evolutionary Database System for Modern Hardware

SirixDB is an evolutionary, accumulate-only database system. Each new commit stores more data in a new snapshot, which shares common data with the previous revisions. The system never overwrites data. It supports a single read-write transaction per resource concurrently to N read-only transactions. Furthermore, in stark contrast to other database systems, the persistent, durable tree consists of variable-sized database pages. Versioning takes place at a sub-page level according to a novel sliding.

🐣 Svelte based Frontend

Moshe Uminer and I are looking for contributions to a frontend for the system mentioned above. The frontend is pretty new (the project started a few months ago), thus there's a lot of work to do.

sirixdb / sirix-svelte-frontend

A GUI console for SirixDB, using Svelte/Sapper.

Project Setup - Setting up SirixDB locally

Unfortunately, this is currently a bit messy, but still rather straightforward.

There are several resources required to run SirixDB, and they can all be found in the resources directory of this repository.

SirixDB depends on keycloak for authentication, so we first need to run (in the directory in which you have the above resources):

docker-compose up -d keycloak

It can take a minute for keycloak to be ready for connections. If you like, you can use the wait.sh script in the above mentioned resources directory to wait until keycloak is ready. A script from the resources folder initializing keycloak with a user "admin" with the password "admin" is run automatically.

Once keycloak is ready, navigate to http://localhost:8080/admin and login using the credentials admin/admin. Click on Users in the sidebar navigation, then click Add user. Enter the name of the…

View on GitHub

XML display #10

mosheduminer posted on Apr 03, 2020

Currently, the /databases route is only capable of displaying JSON. We need to add complete XML functionality.

View on GitHub

Layout customization #249

mosheduminer posted on Sep 30, 2020

Enable resizing the various "sections" in each route,
as well as allow drag-and-drop to rearrange the layout. (a section would be, for example, (in the resource route) the bar showing database/resource names, the history timeline, the resource view. (in the query route) the query box, the query result display, the saved/old queries bar).

I imagine this would require

using something like svelte-dnd-action to allow rearranging the layout,
and using the resize CSS property to allow native element resize.
I imagine the resize property would exist on containers that would each containe a single "region" that is draggable.
There should be listeners to resize the container region when a large section is moved to a small region (and swap the small section to the other region).
There should be listeners to accommodate the resize of a region by resizing other regions.

This would require refactoring the layouts to be compatible with drag and drop.

View on GitHub

The idea is to build a frontend, which can interactively depict the differences between revisions of the data and visualize the result of time-travel queries.

In general, it would be great to provide a similar space-filling approach (modified Sunburst-View) like the one I once developed for my master's thesis: