Operational Service Views - Reactive Web Programming with Baratine
summary
Baratine enforces single-thread ownership per service with an efficient inbox and automatic batching, keeps service state in memory and persists it to an internal reactive document DB (Crackin) via two annotations, and journals inboxes in an append-only journal for replay and failover. Demos include a persistent bookstore and a full auction system with PayPal settlement that survives restarts. Benchmarks claim about 9M messages/sec and ~4M synchronous calls/sec, with async staying above 2M, and RESTEasy parity shows ~2x throughput.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:23Operational Service Overview
- 3:20Database Persistence
- 4:00API Engine
- 11:16Threading
- 13:44In Memory
- 16:57asynchronous performance
- 17:55microservice
- 18:06auction microservice
related talks
01h 01mReactive web services
01h 21mReactive Web Applications
42mReactive applications with WebSockets
57mBeyond the buzzword: A reactive web application in practice
45mKeeping it Real(time)
29mRealtime web applications with streaming REST
52mBeyond the Buzzword: A Reactive Web Application in Practice
39mAsynchronous and Non-Blocking IO with JRuby