Download JAR files tagged by databases with all dependencies

Quark (/ˈkwɔrk/ or /ˈkwɑrk/) is a federation layer over the databases in a analytics stack. It provides a federated schema that maps tables in multiple database systems. With the help of the federated schema, Quark makes it possible to define and use materialized views, olap cubes and other relationships between tables stored in different databases. Quark comes with a simple execution layer that redirects queries to use materialized views or cubes. Quark is distributed as a JDBC jar and will work with most tools that integrate through JDBC.

ADIF Processor visualizes contacts in your input file on Google Earth. It generates a Google Earth Project file, also known as a KML file, with a visualization of each contact in the ADIF/SOTA CSV input file where station locations can be determined. It parses structured tags in comments to enrich the correct ADIF output file. QRZ.com is used to determine station locations and provide additional information in the ADIF output file. The markdown/text file output contains a listing of contacts. The processor contains activity databases for the main outdoor activities such as SOTA, POTA, GMA, HEMA etc.

Evita is a specialized database with easy-to-use API for e-commerce systems. Purpose of this research is creating fast and scalable engine that handles all complex tasks that e-commerce systems has to deal with on daily basis. Evita should operate as a fast secondary lookup / search index used by application frontends. We aim for order of magnitude better latency (10x faster or better) for common e-commerce tasks than other solutions based on SQL or NoSQL databases on the same hardware specification. Evita should not be used for storing and handling primary data, and we don't aim for ACID properties nor data corruption guarantees. Evita "index" must be treated as something that could be dropped any time and built up from scratch easily again.