blob: 1cb53b316953d066ffdba757e1f2cadde9d7a12a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
Microservices gone wrong
- starting from scratch
api gateway
middleware for extrenal requests
message-bus rabbitMQ
Service oer domain entity
Meta service using ES
Kurbenetes
Why local dev failed?
Slow.
Incosistent
Would break
mainly: "Someone elses problem" - all devs
Production release took 1 week
Cost of context switching
Smoke Test
- Lessons Learned
- service call's are unreliable
- "microlyth"
1. DOnt do micorservices
a. unless you have a dedicated tooling and automation team
2. Start with big services
a/ Split if you require
3. Auomate everything
a spin up, deployment migration, backup state resortation Elliptic
4. Dont plan for failure, live it
a. failure modes should bebuilt first, tested first, and relied upon
5. Define SLO early
a. Define business objectives for each service and system before building
|
