Completed
Account - command processing
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Developing Event-Driven Microservices with Event Sourcing and CQRS - Philly ETE 2015
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Traditional application architecture
- 3 Obstacle to frequent deployments
- 4 Overloads your IDE and container
- 5 Obstacle to scaling development
- 6 Requires long-term commitment to a technology stack
- 7 Limitations of a single relational database
- 8 Apply the scale cube
- 9 Use a microservice architecture
- 10 Use NoSQL databases
- 11 Different modules use different types of databases
- 12 Update two entities in a NoSQL database
- 13 Cassandra main table index table
- 14 Event-based architecture to the rescue
- 15 Eventually consistent money transfer transfer Money
- 16 Update and publish using 2PC
- 17 Use data store as message queue
- 18 Persists events NOT current state
- 19 Replay events to recreate state
- 20 Event store implementations
- 21 Optimizing using snapshots
- 22 Aggregate traits
- 23 Account - command processing
- 24 Aggregate type classes/implicits
- 25 Business benefits of event
- 26 Technical benefits of event
- 27 Drawbacks of event sourcing
- 28 Strategic design: identify sub- domains
- 29 Strategic design: define microservices
- 30 Decide inter-service communication mechanisms
- 31 Use the familiar building blocks of DDD
- 32 Designing domain events
- 33 The anatomy of a microservice
- 34 Asynchronous Spring MVC controller
- 35 Handling events published by Accounts
- 36 Command Query Responsibility Segregation (CQRS)
- 37 Query-side microservices
- 38 Benefits and drawbacks of
- 39 Summary
