Apps Need Data

on YouTube ↗36m

" summary

Jamie builds a vacation-request microservice that must read HR data from a monolith, use Spring Boot and spring cloud services, and deploy on Cloud Foundry. The solution is a data-API layer with caching as a bulkhead (Pivotal Cloud Cache or Redis), on‑demand MySQL/Postgres or document stores, API gateway for mobile-friendly payloads, and schema-versioned endpoints that let an MVP ship in about four weeks while avoiding monolith lockstep releases. pivotal cloud cache strangler pattern

AI-written summary · about

" chapters (6)

1. 0:00Introduction and setup
2. 1:06Why build microservices
3. 8:10Data challenges in microservices
4. 26:58Frontend and API gateway considerations
5. 31:12Cloud Foundry and MVP deployment
6. 33:19Resources and closing

" related talks

• 49mDDD Strategic Design with Spring BootMichael Plöd · Spring I/O 2017
• 29mIntro to Development of Java Spring Microservices with Cloud FoundryJan Svoboda · Cloud Foundry Summit Europe 2019
• 22mOperationalising Data Science on Cloud FoundryIan Huston · Cloud Foundry Summit Europe 2016
• 32mCaching for Microservices - Introduction to Pivotal Cloud Cache - Pulkit ChandraPulkit Chandra · SpringOne Platform 2017
• 56mArchitecting Cloud Native MicroservicesRohit Bhardwaj · Great International Developer Summit 2023
• 02h 30mBuilding Cloud Native Progressive Web AppsJosh Long, Matt Raible · Devoxx Belgium 2017
• 28mThe journey from monolith to microservicesMike Gehard · The Lead Developer 2016
• 56mModern Java microservices in the Cloud!Andrzej Grzesik · Confitura 2022