A financial services company runs a monolithic relational database that has become the bottleneck for a rapidly growing transaction-processing application. Read replicas have already been added, but the primary node is now saturated by write throughput during peak trading hours, and vertical scaling has reached the largest available instance size. The architecture team must design a solution that allows write capacity to scale beyond a single node. Which approach BEST meets this requirement?