Starling Bank’s back end is made up of 40 services. These were all being deployed as a monolith, an approach that was slowing us down. We migrated our delivery pipelines to deliver these services in 5 separate groups, and are now starting to use Kube.
But why did we start by deploying our services as a monolith? Why are we now deploying our services in 5 groups as opposed to all individually? Why are we only starting to use Kube now?
This talk will explore Starling’s technical philosophy of rampant pragmatism and how we applied it to our delivery pipeline. We will examine how to develop a pipeline that can evolve with your needs, rather than one that has to be overhauled every 5 years.
Required audience experience
Some knowledge of continuous integration & deployment required
Objectives of the talk
This talk will examine the philosophy of rampant pragmatism in technology. It will explain how to distinguish between necessary and unnecessary complexity, and how you can avoid the latter. It will explain how we applied this philosophy to Starling Bank’s delivery pipeline.