Simplify data and event-driven microservices with Oracle Database
summary
Demo GrabDish app and workshop show Oracle Database hosting JSON, relational, graph and spatial data, running an in‑DB messaging engine (AQ/TEQ) that gives exactly-once messaging and a JDBC/JMS local transaction bridge, plus Kafka compatibility via okafka.jar and a Mongo-compatible API. A saga engine and a forthcoming automatic compensating data type keep recovery state and automate rollbacks so teams avoid the ~80% development cost often spent on compensation. OpenTelemetry exporters feed traces, logs and metrics into a single Grafana console.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:38Real World Microservices Example
- 1:34Decoupled Microservice Architecture
- 8:28Event Sourcing
- 9:01Command Query Responsibility Segregation
- 11:05Simplifying of Polyglot Persistence
- 11:17Pro and Con of Single versus Multi-Model Databases
- 14:03Data Maintenance
- 17:01Orchestrated Saga Pattern
- 20:52Observability
related talks
28mKubernetes and Microservices with Database
24mRethinking Database Architecture to Embrace Modern App Dev
46mDiscover Oracle Database@Azure a new opportunity for developers
44mWho is Jason, and what’s he doing in my database?
34mCloud native database development
32mModern application development with REST Data Services
27mAutomating Data Management for All
31mSuperfast event stream processing with a converged database