Beyond Rest and Crud
summary
Argues that integration logic belongs in lightweight routes, not bulky services, and shows it by building a Dungeons & Dragons inventory app that runs as both CLI and web UI using Apache Camel, Quarkus templates and Jackson. Routes use wiretap and recipient list patterns, direct endpoints and a transactional DB to fork work and emit JSON logs, Markdown files and files to dynamic directories in parallel. Demo logs show multiple threads and parallel emissions completing; a few concise route definitions handle the glue.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 4:36Microservices and independence
- 10:55Building the D&D app demo
- 15:30REST endpoints with Camel
- 21:46Wiretap and parallel routing
- 26:43Markdown and JSON emitters
- 32:29Camel's flexibility and Q&A
related talks
51mREST next level: Crafting domain-driven web APIs
56mDDD & REST - Domain Driven APIs for the Web
44mWriting queryable APIs with MicroProfile GraphQL
46mLet’s have some effective REST!
01h 39mLet’s have some Effective REST
46mFrom Untested Spaghetti to Well-Rested Developers
46mREST next level: writing business-oriented web APIs
41mLiving on the Edge (Service): Bunding Microservices