What we have
We invented and patented a better approach to database scalability and distribution, which is comparable in performance with others, but which can be run on the client’s machines. Even better, we can enable our customers to manage global-scale databases that are both geo-replicated, highly available and strongly consistent. Our technology has the potential to be the world’s first unified SQL database platform, providing a single logical view over many databases.
We have implemented the first working version of the software and are a few months away from supplying the first full-fledged database which provides clients with an industry standard (JDBC or ODBC) API they can use with their existing solutions and tools.
We’ve gained quite a bit of industry recognition in the distributed systems field (in computer science) and we have been invited to talk about the solution at HydraConf.
We’ve also established a professional corporate network across multiple legal entities and jurisdictions, overseen by professional advisors, to maximise potential income from both the patent IP and the software implementation.
The problem we solve
When using databases, developers have lots of options around the safety guarantees of their information. Household database names like Oracle, Postgres or MySQL provide these, but are single-server solutions. Their approach is known as the strong consistency model, but it is prone to failures and also that if the software is successful and outgrows the database’s capacity, the solution has to be rewritten, often from the ground up. Thus, the strong consistency model leads to the scalability problem. Due to this, large software-providers employ more complicated solutions, which are much costlier to run and develop, and which can only be developed by highly qualified experts. This solution is called eventual consistency.
If we take Google’s example, they started out initially with an eventual consistency model called BigTable. This worked for them for a while until they realised how much extra development effort this approach needed. Google is renowned for having the best talent, so one can imagine what sort of problems others encounter. To move towards a simpler developer model, Google invented Spanner, which provides strong consistency over a distributed database. To achieve this, they use atomic clocks and GPS to coordinate time information between their servers, which makes the solution prohibitively complex, expensive and proprietary, so market adoption is low.
For legal reasons, many enterprise users, such as financial institutions or government bodies don’t even have the option of handing over their data-management to external providers, even if they would be happy to pay much more for databases alone. They cobble together some half-way solution where they use separate databases for different functions and design services to exchange information between them. They are conservative in their approach and for a good reason as their business largely depends on the stability of the existing solution. This leads to a complicated eventual consistency model with all its problems.
Which is where we come in.
Our technology is not only a lot simpler to maintain and manage. It also has the potential to merge existing databases into one service, thus creating a unified database platform for the world.
Our immediate goal is our technology to be recognised as an innovative solution in the distributed database space. We have a number of grand, but true statements to make, which all stand up to academic scrutiny.
Next, we want to offer a distributed database solution to early enterprise adopters. This solution already has a number of benefits over the competition, namely that it addresses the most pressing concern, which is complexity.
Depending on funding, we want to provide the world’s first unifying database protocol, which can retrofit strong consistency over eventually consistent systems, by supporting different kinds of databases. This would have a unique advantage over the competition for enterprises, which are mostly reluctant to change much of their existing systems, due to fears of disruption of their (largely) working setup and processes.
© DIANEMODB 2021 | www.dianemodb.com | email@example.com