Home / Companies / Cockroach Labs / Blog / Post Details
Content Deep Dive

Core Banking Modernization with Temenos | CockroachDB

Blog post from Cockroach Labs

Post Details
Company
Date Published
Author
Nanda Badrappan
Word Count
1,309
Company Posts That Month
6
Language
English
Hacker News Points
-
Post removed?
No
Summary

Temenos and Cockroach Labs are positioning Temenos Core on CockroachDB as a modernization option for banks seeking always-on, real-time, and resilient core banking operations amid legacy batch systems, costly outages, and stricter regulations such as the EU’s Digital Operational Resilience Act. Temenos Core, formerly T24 and Temenos Transact, provides cloud-native, microservices-based functions including high-volume transaction processing, multi-currency and multi-entity support, Close of Business processing, and API-based extensibility. CockroachDB contributes distributed SQL capabilities such as horizontal scaling, replicated high availability, serializable ACID transactions, hybrid and multi-cloud deployment options, data-sovereignty geo-partitioning, and PostgreSQL-compatible integration through Temenos’s TAFJ runtime. Joint testing on Kubernetes and Microsoft Azure processed 2 million transactions across 20,000 accounts, including high-volume and multi-currency workloads, and found near-linear scaling in tested configurations while concurrent transaction, HVT Merge Service, and Close of Business processes completed successfully. The companies plan further large-scale testing, deployment reference architectures, migration tools, multi-region patterns, and broader Temenos-suite integration, while noting that performance outcomes depend on configuration, infrastructure, and workloads.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 4 2,940 753 191 -50%
Kubernetes 2 1,897 245 89 -31%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.