Implementing Microservices with Scale and Akka

Explore microservices implementation using Scala and Akka in this 51-minute conference talk from Scala Days Berlin 2016. Delve into the practical aspects of microservices for enterprise applications, focusing on determining appropriate service boundaries and ensuring effective communication in distributed environments. Learn how to adhere to reactive software principles, making your microservices responsive, resilient, elastic, and message-driven. Gain insights into crafting microservices that accurately model business domains, with demonstrations of advanced Akka usage throughout. Examine topics such as bounded contexts, ubiquitous language, microservice databases, query models, asynchronous services, event publishing, and resilient architectures. Witness practical code examples for service start-up, actor aggregates, and topic feeders, equipping you with the knowledge to implement scalable and efficient microservices in your own projects.

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)