API Abstraction and API Chaining in Grails
summary
Grails project builds a runtime api toolkit plugin that loads reloadable api object JSON configs into a shared cache so proxies, message queues and app instances see the same rules; logic runs in pre/post filters (handler interceptors) so controllers only emit resources. It implements API chaining (pre/post/blank chains), batching inside the communication layer, and claims up to 50% throughput reduction for mobile; benchmarks show ~0.10–0.20 ms/request on a laptop and the demo is functional with minor glitches.
AI-written summary · about
chapters (12)
- 0:00Start
- 12:23Scattered: API Functionality Redundant; Not Dry
- 15:15Entangled & Scattered: Role Checks Not Atomic
- 26:32Test.json
- 30:51Why A Reloadable ApiObject?
- 36:11What Are The Benefits?
- 45:04ApiChaining Definition
- 45:50How To Send An ApiChain
- 47:29ApiChaining Flow in 2.3+
- 48:18ApiChaining Chain Branching
- 48:47ApiChaining Benefits
- 55:26Additional Info
related talks
40mSticky API: Connect Bricks and enter a global IT-ecosystem
01h 07mAPI Toolbox with Spring
38mAdvanced API Design for Scalable Distributed Systems
39mAPI Development in 2017
28mAPIs and GenAI : Your Perfect Combo with LLM-Powered Frameworks.
28mWhy is API Gateway essential to business
25mEverything is an API
36mWiring Prismatic's API with