APIs are Evolving. Again.
summary
Overview states that an open source toolkit named platformatic runtime runs multiple apps inside one Node.js process and turns microservices into “nano services,” routing fetch calls in‑process over a virtual mesh so services aren’t automatically internet‑exposed. A composer merges multiple OpenAPI/REST services into a single endpoint. A platformatic DB scaffolds APIs from migrations. The stack ships live via GitHub Actions to platformatic.cloud and the onstage release completes successfully during the 20‑minute slot.
AI-written summary · about
chapters (10)
- 0:00API evolution history
- 2:50Java monoliths to web services
- 5:43Ruby on Rails developer experience
- 8:13Node.js breaking monolith
- 10:21Microservices challenges
- 13:17Platformatic and its tools
- 15:46Platformatic Composer
- 16:50Platformatic Runtime and Nano services
- 19:59Platformatic Cloud pricing
- 21:31Live release demo
related talks
30mDX is not magic, and neither should your backend be!
34mA Platformized Approach to Node.js Development
21mPragmatic Strategies for Global API Integration
15mThe changing API problem
26mMetamorphosis: Microservices & Event-driven Architecture
48mTransforming a monolith to an API platform
30mFull Stack Agnostic Apps in the Agentic Era
01h 01mESB, iPaaS, API Management, Microservices...