Raising Abstractions for the Software Defined Business
summary
A lightweight middleware replaces stacks with a unified graph/object model that stores resources as immutable, metadata-tagged entries, runs on the JVM and deploys in ~15 minutes, and exposes ACID transactions, rollback and end-to-end traces. The system ships as a 32 megabyte footprint web-style key/value graph, claims 50–100x I/O and compute improvement, has been production for years without crashing, and converts fragmented sources into a composite master-entity in about a week for real-time, declarative integration and governance.
AI-written summary · about
chapters (22)
- 0:00Intro
- 4:36Dynamic Distributed Diverse
- 7:23The Problem
- 9:48Fragment Management
- 10:15Application Model
- 10:43Continuous Manual Integration
- 11:42Flexibility
- 12:05Interoperability
- 12:31Reinventing middleware
- 14:15Unified object model
- 19:03Plugin fabric
- 19:19Stacks
- 22:19Graphs
- 23:04Complex Computation
- 24:35middleware stack
- 24:54simple transaction
- 25:26increasing complexity
- 25:40non differentiated middleware
- 29:11Unified horizontal application architecture
- 30:45The abstraction
- 32:08The 12F
- 39:12Time left
related talks
11mAbstracting infrastructure away from developers
25mAutobahn in the cloud
43mThe Java Cloud-Native Stack for Microservices and Serverless Architecture
15mFaster Data Access with MicroStream
49mReactive microsystems
47mSay Goodbye to Microservices, Say Hello to Self-Contained Systems
46mLost in transaction? Strategies to deal with (in-)consistency in distributed systems
37mHow to manage complexity in distributed applications