DBS: A Secure, Fast & Self-Managed RDBMS Alternative

DBS is a Relational Database Management System (RDBMS) whose development primarily focuses on security, speed, and ease of management. It is offered as an alternative solution to any developer or organisation concerned about data privacy, OLTP performances, flexibility and operating costs.

To foster efficiency, the solution is intentionally limited to a restricted number of functions. Whilst DBS can execute very complex queries, it not designed to relocate the applications' business logic within database(s), using stored procedures for instance; it is rather developed to ensure a robust, high-reliable service to manipulate relational data stores at a rapid pace, whether the volume is large or not, and to deliver appropriate information to end-users according to their functional responsibility/accountability, without the need to define cumbersome read/write access rights per column, per user.

Schema Oriented


DBS is schema oriented

DBS Schema = Logical Representation of Data Collections & Basis of RBAC Privileges


With DBS, schemas are not only the logical representation of a coherent set of data collections, they are also the fundamental objects to grant specific privileges on information to user roles when assigned users execute DQL & DML queries.

Secure How and Whom can Access the Information


DBS Access & Privileges

Dual Security Model to Manage Access & Privileges


DBS relies on 2 security models when dealing with end-user or application accesses & privileges:

  1. User Access Control (UAC)
    • Authentication, MFA can be enabled at user level and/or at client-application level.
    • Privileges granted to users to change object structures (DDL).
  2. Role Base Access Control (RBAC)
    • Privileges granted to users to read (DQL), and how, as well as to write (DML).

Protecting Privacy by Design


DBS natively embeds K-anonymity technics to protect information from actors who do not require to view intrinsic data to perform their duties.

These features aim to:

  • Secure the organisation in front of the numerous regulations relating to data-privacy, also from a business perspective, since adequate information is provided in a consistent way with the receivers' responsibilities from the source.
  • Save developers quite a significant time in code implementation.
  • Save the organisation money and time in data transfer/copy burden when, for instance, IT people need access to the production data in order to debug issues.
DBS Anonymization

Performances


DBS benchmark

Benchmark Results Speak for Themselves


DBS demonstrated from the early stages, during the prototyping phase, great performances in front of existing well-known solutions.

Benchmarks were carried out using datasets of several thousands of records to load and to collect with multiple JOINs.
All the results indicate that DBS is constantly faster on lookup queries.

Those benchmark results can be easily reproduced by anyone. Benchmark methodology and datasets are available here.

Self-Managed & Auto-Tuned


The goal here is to make DBS adapt to its environment the easiest way.
Depending on the host configuration, it tunes itself to ensure the maximum performances according to the (virtual) system capabilities. DBS automatically ajusts its parameters to maximize the use of the system resources available to it.

Nevertheless, for the config & params tweak afficionados, it is totally possible to adjust settings manually.

DBS Self-Management and Auto-Tune

Web Apps Integration Ready


SaWS companion

SaWS: Expose DBS Schemas as Web Services


SaWS is an optional companion service to DBS. When it is installed beside, dedicated DBS schemas and parameterized queries can be securely exposed as Restful Web Services.

DBS can therefore take part in cohesive application workflows with ease.

FAQ

As of today, no. It is not in the roadmap, but things might change in the future.