Hot Swapping a Bank Part 1: The Problem and The Solution

Transaction processing is at the very core of Clear Street’s business. It’s what hydrates our ledger and manages the lifecycle of trades that go through our system. It’s the obvious choke point for all data, and for this reason it needs to be scalable, resilient, and extensible.

Over the past year and a half, Clear Street’s engineering teams took on the daunting task of replacing our core transaction processing engine, Bank, and changing the many moving parts that were necessary to ensure a successful migration to our new system, BK.

We cover BK’s design in another engineering blog, “Scaling Clear Street’s Trade Capture System”, but here I want to focus on our mission to replace our legacy system with the new, shiny BK. In this three part series, I’ll discuss how we pulled off this complex system change through validation, planning, testing, and re-testing, and collaboration within our engineering team and across the organization.

Keep reading on our blog:

www.clearstreet.io/insights/hot-swapping-a-bank-part-1-the-problem-and-the-solution