WHAT COMES AFTER MICROSERVICES? MATT RANNEY WHAT COMES AFTER - - PowerPoint PPT Presentation

▶
what comes after microservices
SMART_READER_LITE
LIVE PREVIEW

WHAT COMES AFTER MICROSERVICES? MATT RANNEY WHAT COMES AFTER - - PowerPoint PPT Presentation

Jan 28, 2023 156 likes •709 views

WHAT COMES AFTER MICROSERVICES? MATT RANNEY WHAT COMES AFTER MICROSERVICES? MATT RANNEY We hired lots of engineers. They wrote lots of software. This causes lots of problems. Why use microservices at all? Easier releases? Ef fj ciency

slide-1
SLIDE 1

WHAT COMES AFTER MICROSERVICES?

MATT RANNEY

slide-2
SLIDE 2

WHAT COMES AFTER MICROSERVICES?

MATT RANNEY

slide-3
SLIDE 3

We hired lots of engineers.

slide-4
SLIDE 4

They wrote lots of software.

slide-5
SLIDE 5
slide-6
SLIDE 6
slide-7
SLIDE 7

This causes lots of problems.

slide-8
SLIDE 8

Why use microservices at all?

slide-9
SLIDE 9

Easier releases?

slide-10
SLIDE 10

Effjciency somehow?

slide-11
SLIDE 11

Scaling the organization?

slide-12
SLIDE 12

Coupling

slide-13
SLIDE 13

APRIL 2016 MAY 2016 OCTOBER 2016

slide-14
SLIDE 14

New problems

slide-15
SLIDE 15

Sharded database RPC Service discovery Rate limiting Circuit breaking Tracing Release management

slide-16
SLIDE 16

New problems

slide-17
SLIDE 17

Composability

slide-18
SLIDE 18
slide-19
SLIDE 19
slide-20
SLIDE 20
slide-21
SLIDE 21
slide-22
SLIDE 22
slide-23
SLIDE 23
slide-24
SLIDE 24
slide-25
SLIDE 25
slide-26
SLIDE 26

Composability

slide-27
SLIDE 27

Services want their own storage.

slide-28
SLIDE 28
slide-29
SLIDE 29

Developing against this system is hard.

slide-30
SLIDE 30

Evolving schemas is hard.

slide-31
SLIDE 31
slide-32
SLIDE 32

Having 1M services should be as easy as 1K or 10. Provisioning storage should be easy as checking in code. Devs should be able to safely test with real production data. Fancy types are useful.

slide-33
SLIDE 33

DOSA

slide-34
SLIDE 34
slide-35
SLIDE 35
slide-36
SLIDE 36
slide-37
SLIDE 37
slide-38
SLIDE 38
slide-39
SLIDE 39

Composability

slide-40
SLIDE 40
slide-41
SLIDE 41
slide-42
SLIDE 42

RPC

slide-43
SLIDE 43
slide-44
SLIDE 44

Asynchronous message passing FTW

slide-45
SLIDE 45

“Does developer convenience really trump correctness, scalability, performance, separation of concerns, extensibility, and accidental complexity?” [Vinoski (2008)]

slide-46
SLIDE 46
slide-47
SLIDE 47
slide-48
SLIDE 48
slide-49
SLIDE 49

Composable event processors

slide-50
SLIDE 50

Workfmow? Serverless?

slide-51
SLIDE 51

Why are we here?

slide-52
SLIDE 52

Let’s make the tools for building big be better than the tools for starting small.

slide-53
SLIDE 53

“Does developer convenience really trump correctness, scalability, performance, separation of concerns, extensibility, and accidental complexity?” [Vinoski (2008)]

slide-54
SLIDE 54

Composability

slide-55
SLIDE 55

THANKS