Tweet
Tweet

Slide 1

Slide 1 text

Mofizur Rahman Developer Advocate, IBM You Probably Don’t Need Kubernetes @moficodes

Slide 2

Slide 2 text

@moficodes Want ≠ Need

Slide 3

Slide 3 text

@moficodes Ask Why

Slide 4

Slide 4 text

@moficodes Microservice Envy

Slide 5

Slide 5 text

@moficodes Distributed Monolith

Slide 6

Slide 6 text

@moficodes “Don't even consider microservices unless you have a system that's too complex to manage as a monolith.” Martin Fowler

Slide 7

Slide 7 text

@moficodes

Slide 8

Slide 8 text

@moficodes Kubernetes is Hard

Slide 9

Slide 9 text

@moficodes Don’t fit your problem to a solution

Slide 10

Slide 10 text

@moficodes You will never future proof 100%

Slide 11

Slide 11 text

@moficodes Kubernetes ≠ Speed New ≠ Better Useful ≠ Useful for You

Slide 12

Slide 12 text

@moficodes If not K8s, then what?

Slide 13

Slide 13 text

@moficodes Culture > Tools

Slide 14

Slide 14 text

@moficodes Communication > Abstraction

Slide 15

Slide 15 text

@moficodes Restructure > Refactor

Slide 16

Slide 16 text

@moficodes Automate Everything

Slide 17

Slide 17 text

@moficodes Code Once Test Twice

Slide 18

Slide 18 text

@moficodes There is no cure for bad architecture

Slide 19

Slide 19 text

@moficodes Kubernetes Will Be Here (Or something similar will...)

Slide 20

Slide 20 text

@moficodes What is right is not always popular and what is popular is not always right. ― Albert Einstein