Completed
WHAT IS THE SIZE OF A BOUNDED CONTEXT?
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Implementing Microservices with Scale and Akka
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 INDUSTRY OF EXTREMES
- 3 WHY ACID? HOW DID BUSINESS WORK BEFORE
- 4 EXTREME: SERVICE SIZE MONOLITH MICRO
- 5 THINK INFRA- STRUCTURE
- 6 PRACTICAL?
- 7 BUILDING MICROSERVICES
- 8 WHAT IS THE SIZE OF A BOUNDED CONTEXT?
- 9 SHOULD IT HAVE JUST ONE ENTITY TYPE?
- 10 ASK YOUR UBIQUITOUS LANGUAGE
- 11 LINGUISTIC COMPONENTS ARE COHESIVE
- 12 LARGER THAN ONE ENTITY FAR SMALLER THAN A MONOLITH
- 13 UBIQUITOUS LANGUAGE IS GREATER THAN ENTITY NAMES
- 14 UBIQUITOUS LANGUAGE INCLUDES ENTITIES / COMMAND MESSAGES / EVENT MESSAGES
- 15 MICROSERVICE DATABASE(S)
- 16 QUERY MODEL
- 17 ACTORS ARE ASYNCHRONOUS SERVICES
- 18 RAPIDS: PUBLISH EVERY EVENT
- 19 HIGH-PERFORMANCE BUS REST (ATOM) KAFKA RABBITMO
- 20 PONDS: AGGREGATE ACTOR STATES
- 21 ACTORS EMIT EVENTS TO RAPIDS
- 22 RESILIENT PARENT CRASH DETECTION, NOT CLIENT
- 23 MESSAGE DRIVEN ACTORS ARE MESSAGE DRIVEN RAPIDS ARE MESSAGE DRIVEN
- 24 HOW TO IMPLEMENT MICROSERVICES SCALA & AKKA
- 25 SERVICE START UP (THE CODE)
- 26 PROCESS MANAGER WHEN NEEDED. OTHERWISE DON'T
- 27 ACTOR AGGREGATE (THE CODE)
- 28 TOPICS FEEDER (THE CODE)
