From Teams Running Grit Core Lab in Production
We migrated our settlement ledger to Grit Core Lab in March 2024. In seventeen months of production use, we have had zero reconciliation failures. The previous system averaged two per quarter.
— Hiroshi Tanaka, Head of Infrastructure, regional securities firm, OsakaThe on-premises deployment took four hours from binary download to first production write. The configuration validator caught two mistakes in our network topology before we went live, which would have cost us replication guarantees.
— Yuki Sato, Database Engineer, fintech startup, TokyoSelected client feedback. Individual experiences vary and may not be representative.
A bit more
Grit Core Lab incorporated formally in Okayama in 2019 and opened its first managed cloud region in Osaka in early 2021, followed by Tokyo later that year. The team is small by design: seven engineers, two of whom focus exclusively on correctness testing and fault injection. The test suite runs 14,000 scenarios nightly, including network partition simulations, disk-failure injections, and clock-skew tests. If a scenario causes a consistency violation, the build does not ship. That constraint has held since the first public release.
The patches worked, mostly. But every quarter brought a new edge case.News & Announcements
Why Strict Serializability Matters for Financial Databases
Most relational databases offer serializable isolation as their strongest consistency guarantee. Strict serializability is stronger, and the difference is not academic. For a financial settlement ledger, the gap between the two can be the difference between a system that requires a reconciliation job and one that does not.
Read more →Synchronous vs Asynchronous Replication in Financial Systems
Replication is how a database survives the failure of a single node. The question of whether that replication is synchronous or asynchronous is one of the most consequential architectural decisions in a financial system, and it is frequently made without a full understanding of what asynchronous replication actually risks.
Read more →WAL Archival and FSA Compliance for Transaction Databases in Japan
Japan's Financial Services Agency requires financial institutions to maintain accurate and complete records of transactions for specified retention periods. For a database-backed system, the most reliable way to satisfy this requirement is to archive the write-ahead log in a verifiable format, rather than relying on periodic backups or application-level export jobs.
Read more →Which Grit Core Lab deployment fits your workload?
Answer three questions about your infrastructure and compliance requirements. The result will point you to the deployment option most likely to fit your situation.
With respect
Kenji Murakami
Kenji Murakami is the founder and lead engineer of Grit Core Lab. He spent eight years at a Tokyo payment processor, where he maintained the transaction ledger and eventually led the database infrastructure team. Before that, he contributed to the open-source Paxos implementation used in a distributed key-value store maintained by a university research group in Kyoto. He holds a degree in information engineering from Osaka University. Outside of work, he runs a small reading group in Okayama that works through distributed systems papers one chapter at a time.
Tell us about your workload
Submit this form and a Grit Core Lab engineer will respond within one business day with information relevant to your deployment scenario. We do not pass your details to third parties.