Lukasz Panusz

Financial institutions require operational reliability and international connectivity to process millions of daily transactions across time zones. But maintaining global consistency, data integrity, and availability is complex.

Command query responsibility segregation (CQRS) is often presented as a specific architectural pattern focused on scaling the infrastructure storage layer by separating read and write paths. However, originally this was a code-level pattern that had nothing to do with infrastructure.

When applying DevOps best practices and implementing infrastructure as code (IaC) for your projects, you have to make a decision: should you combine or separate components that store information (like databases) and other components that don’t?

According to the estimates, by 2030, humans will generate an ocean of data up to 572 zettabytes, which is equal to 572 million petabytes. This poses the question: How do we prepare our IT environments for the challenges of continually growing demand for infrastructure without inflating infrastructure costs and spending countless hours on maintenance?