Renovate or Reinvent? KISS your Open Banking API Strategy
summary
Argues for pragmatic KISS choices: keep or update existing APIs rather than rebuild unless data boundaries force it. Warns that serverless patterns rapidly produce vendor lock‑in — examples include Lambda/DynamoDB/SQS/ElastiCache — so use serverless for throwaway prototypes, reporting jobs and admin tasks only. Shows microservice pain: one org runs 1,500 microservices / 150 engineers and says simple domains (shopping cart) are better as well‑designed monoliths; split services by clear data ownership. Notes Tyk is implemented in Go.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:09Boring is dependable...
- 11:08So what does the grumpy one soy?
- 13:38A real world microservice setup.
- 16:17A simple microservice setup...
related talks
45mMicroservices: A retrospective
45mThe Evolution From Monolith to Microservices to Serverless and Beyond
40mKill "Microservices" before its too late
23mLightning Talk: Rethinking Microservices
32mAdopting a Modern API Strategy for Hybrid, Multi-Cloud Architectures
34mArchitektury Aplikacji: The last mile of microservices
56mArchitecting Cloud Native Microservices
01h 03mThe Magic of Small Things - 10 Years of Microservices
