Scaling Your Architecture with Services and Events
February 19 @ 9:00 am - 5:00 pm₪1,530.00
Most successful large-scale software organizations have evolved their architecture over time from a monolithic application with a monolithic database to a loosely coupled set of components we now call microservices. This session will outline the pros and cons of the different stages of evolution, and will make practical suggestions about when and how organizations should consider breaking up their monolith. We will discuss how to justify, organize, and fund an architectural transformation. We will discuss how to set up an initial pilot and then how to incrementally migrate from there.
Most of the session will be a deep dive into the modern best practices around asynchronous decoupling, resilience, and scalability that allow us to implement a large-scale software system from the building blocks of services and events. This will detail the practices used at Google, eBay, Amazon, and other high-performing technology organizations.
You will leave with practical suggestions to help you accelerate your development velocity and drive business results.
Intended audience is technical – architect, tech lead, senior developer.
- Choosing the Right Architecture – Monoliths and Microservices
- When to Migrate
- Funding the Migration
- Defining and Running the Pilot
- Incremental Migration
Module 2: Best Practices for Service Architecture
- The Service Interface
- Technology Choices
- Patterns for a Microservices Ecosystem
Module 3: Best Practices for Event-Driven Systems
- Events and Decoupling
- Delivery and Ordering
- Events, Data, and Persistence
- Event Sourcing and CQRS
Module 4: Putting it All Together – Managing Data in Microservices
- Shared Data
Your trainer: Randy Shoup
Randy Shoup is a 25-year veteran of Silicon Valley, and has worked as a senior technology leader and executive at companies ranging from small startups to mid-sized places to eBay and Google. Randy is currently VP Engineering at Stitch Fix in San Francisco.
Earlier, Randy was Chief Engineer at eBay for 6 1/2 years, where he was responsible for multiple generations of eBay’s realtime search infrastructure. He was CTO and co-founder of a startup, and learned just how difficult and different it is to build a company from scratch. He was Director of Engineering at Google for Google App Engine, building and operating the world’s largest platform-as-a-service. He also spent a year and a half applying eBay and Google lessons consulting with startups and large enterprises on how to improve their organizations and technology.
He is particularly passionate about the nexus of culture, technology, and organization.