Dual-engine database · PostgreSQL-compatible
GritDB is a dual-engine database that adds a columnar analytics engine to the PostgreSQL engine. It receives changes from your operational database and runs heavy reports in its place.
Validated by a financial services customerA report query that took 229 seconds on 200,000 rows in the existing PostgreSQL ran in 8.8 seconds on 10 million rows, 50 times the dataSee the case
Aggregation and report queries run on the same database as your business queries, so business work slows down or stops.
You need a separate ETL pipeline that takes data out of the operational database, transforms it and moves it. Building and maintaining that pipeline takes people and money.
Cloud analytics services need your data moved into them, and once it is there, switching elsewhere is hard. Data that cannot leave the company, such as personal credit information, is hard to use there at all.
The analytics system is one GritDB server next to your operational database. The operational database keeps its binaries and data, and your applications stay as they are. If your operational database is PostgreSQL, you set up built-in replication instead of building a separate ETL pipeline. If you need to change the replication settings, the operational database needs one restart. For other databases, a CDC/ETL tool that writes to PostgreSQL sends the changes. If you already use such a tool, you only change its target to GritDB. Reporting and BI tools connect to the analytics system and turn on an analytics session with a connection option.
GritDB installs on the servers you choose. The same installation files work on your own servers (on-premises) and on cloud virtual servers such as Amazon EC2, so you are not tied to one cloud. On a network without internet access, you install it from installation files and OS packages you bring in.
Changes to registered tables are stored in columnar files. For queries in an analytics session, the analytics engine (GritDB engine) reads only the columns it needs, splits the work by file and runs it on many CPU cores.
The Architecture page explains what happens on your operational database when you add the analytics system: during setup, in normal operation and when the analytics system stops.
GritDB
Connect with PostgreSQL drivers · SQL
PLUG UNIFY BURST
The transaction engine is the PostgreSQL engine. So applications and BI tools connect to GritDB with the PostgreSQL drivers and SQL they already use. CDC/ETL tools that write to PostgreSQL also work with GritDB as they are. The analytics engine runs queries in analytics sessions, that is, queries that read only registered tables. The transaction engine handles writes and all other queries. For the exact conditions, see the query paths on the Architecture page. For 1.1, we recommend adding GritDB next to your operational database as an analytics system. Business applications stay connected to the operational database as they are now. For details, see the Ways to adopt section on the Architecture page.
You turn on logical replication (rds.logical_replication) in Amazon RDS and Amazon Aurora PostgreSQL and create a publication. GritDB subscribes to it and receives the changes, and you query the data in an analytics session.
TPC-H data (SF10, 86.58 million rows in 8 tables) is loaded into Oracle and synced to GritDB with a CDC tool.
The videos open in a YouTube player when you click them.
Amazon RDS, Amazon Aurora and Amazon EC2 are trademarks of Amazon.com, Inc. or its affiliates. Oracle is a registered trademark of Oracle and/or its affiliates. TPC-H is a trademark of the Transaction Processing Performance Council.
It fits settlement and performance analysis, post-close ledger aggregation and audit queries at insurance, credit card and securities companies. With an in-house analytics system, you can analyze data that cannot leave the company.
Agencies that moved to PostgreSQL can add an analytics system with built-in replication, and agencies on other databases can add one with a CDC/ETL tool. GritDB also installs on networks without internet access.
Services that run on PostgreSQL can add an analytics system with built-in replication instead of an ETL pipeline, and move report load from the operational database to the analytics system.
We look at a few slow reports with your DBA and check whether GritDB fits. We also set the scope, length and cost of the PoC.
We test with your data and reports. The PoC is paid. If you subscribe, we deduct the PoC fee from your first-year subscription fee. The evaluation license runs for up to 90 days.
Datagrit works out the number of Units with you and sends you a quote. You sign the order form and the license agreement.
You can install GritDB yourself or have it installed for you. You renew the subscription every year.
The full purchase steps, from quote and contract to getting the installation files and renewal, are on the Subscription page.
In analytics sessions, the analytics engine runs queries that read only registered tables. These queries read changes after they are batched into columnar files, so a change you just committed is not visible right away. In our tests, it usually became visible after 12 seconds, and 99 times out of 100 within 22 seconds. If you added GritDB as an analytics system, replication time from the operational database adds to this. Run queries that must have the latest values in a regular session, or on the operational database if you added GritDB as an analytics system. From the next version, we will expand the range of operations and analytics that a single GritDB can handle together.
Create columns that must be exact, such as amounts, as numeric(p, s) with a declared precision, and keep p at 38 or less. The analytics engine computes numeric columns without a declared precision as approximate values.
The two engines, the ways to adopt GritDB and the query paths are on the Architecture page. Things to know about 1.1, such as high availability, row-level security (RLS) and supported column types, are collected in Notes for 1.1 on the Architecture page.
Ask for a discovery meeting or a PoC, and we will get in touch.
