Overview
Syllabus
Intro
INDUSTRY OF EXTREMES
WHY ACID? HOW DID BUSINESS WORK BEFORE
EXTREME: SERVICE SIZE MONOLITH MICRO
THINK INFRA- STRUCTURE
PRACTICAL?
BUILDING MICROSERVICES
WHAT IS THE SIZE OF A BOUNDED CONTEXT?
SHOULD IT HAVE JUST ONE ENTITY TYPE?
ASK YOUR UBIQUITOUS LANGUAGE
LINGUISTIC COMPONENTS ARE COHESIVE
LARGER THAN ONE ENTITY FAR SMALLER THAN A MONOLITH
UBIQUITOUS LANGUAGE IS GREATER THAN ENTITY NAMES
UBIQUITOUS LANGUAGE INCLUDES ENTITIES / COMMAND MESSAGES / EVENT MESSAGES
MICROSERVICE DATABASE(S)
QUERY MODEL
ACTORS ARE ASYNCHRONOUS SERVICES
RAPIDS: PUBLISH EVERY EVENT
HIGH-PERFORMANCE BUS REST (ATOM) KAFKA RABBITMO
PONDS: AGGREGATE ACTOR STATES
ACTORS EMIT EVENTS TO RAPIDS
RESILIENT PARENT CRASH DETECTION, NOT CLIENT
MESSAGE DRIVEN ACTORS ARE MESSAGE DRIVEN RAPIDS ARE MESSAGE DRIVEN
HOW TO IMPLEMENT MICROSERVICES SCALA & AKKA
SERVICE START UP (THE CODE)
PROCESS MANAGER WHEN NEEDED. OTHERWISE DON'T
ACTOR AGGREGATE (THE CODE)
TOPICS FEEDER (THE CODE)
Taught by
Scala Days Conferences