On today’s podcast, Wes Reisz talks with Jason Maude of Starling Bank. Starling Bank is a relatively new startup in the United Kingdom working in the banking sector. The two discuss the architecture, technology choices, and design processes used at Starling. In addition, Maude goes into some of the realities of building in the cloud, working with regulators, and proven robustness with practices like chaos testing.
Why listen to this podcast:
- Starling Bank was created because the government lowered the barrier to entry for banking startups in reaction to previous industry bailouts.
- The system is composed of around 19 applications hosted on AWS and running Java and backed by a PostgreSQL database.
- These applications are not monolithic but are focused around common functionality (such as a Card or Payment Service).
- Java was chosen primarily because of its maturity and long term viability/reliability in the market.
- The heart of Starling is every action the system takes happens at least once and at most once. To help with these rules, everything in their system uses as a correlation id (UUID) and are used to make sure these two rules are met.
You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq