1.
1
From Monolith to K8s
https://2020.jnation.pt/talks/from-java-monoliths-to-k8s/

2.
2
@Salaboy
Mauricio Salatino
http://salaboy.com
@Camunda / @ZeebeHQ / @LearnK8s

3.
3

4.
4
https://github.com/salaboy/fmtok8s-monolith/
A
http://fmtok8s-monolith-jx-staging.X.X.X.X.nip.io

5.
5
https://github.com/salaboy?tab=repositories&q=fmtok8s
B

6.
6
http://fmtok8s-api-gateway-jx-staging.X.X.X.X.nip.io/

7.
7
- Understand Technical Implica3ons
- Kubernetes & CI/CD
- Microservices tools / landscape
- Understand your Business
- Domian-Driven Design
How?

8.
8
Jenkins X
CI/CD for Kubernetes
Part of the http://cd.foundation

9.
9
hOps://github.com/salaboy/fmtok8s-email/

10.
10
- Well scoped feature set
- Well Defined APIs (ex REST and events)
- Small Team with Domain Experts
- Prac3cal Considera3ons
- 1 Repository = 1 Service (release cycle)
- Open APIs
Bounded Context

11.
11
- How bounded context are related to each other
- How all these services are going to integrate
- Prac3cal Considera3ons
- Consumer Driven Contract TesNng
- Contract
- Stub
- Test
Context Maps

12.
12
NEW PROPOSALS FLOW
Implementation Code

13.
13
- Dependencies between Services
- Flow buried in code
- Edge Cases and UnHappy Paths
- Time Based Constraints
- ImplemenNng queries / analyNcs
Considerations

14.
14
- Sequence of things to do + flow control
- Delegate the execuNon of the business flow
- Business visibility and conNnuous improvement
- Prac3cal Side
- Service OrchestraNon
Workflows

15.
15
Zeebe
Microservices Orchestration
Cloud Native Architecture
•Super Scalable
•Low latency / High throughput
•Available as
•SaaS (console.cloud.camunda.io)
•On-Prem (helm.zeebe.io)
@ZeebeHQ
http://zeebe.io

16.
16
Operate

17.
17
Operate

18.
18
- Kubernetes is Hard
- OpNmize decisions around what to build and what
to integrate
- Focus on business value
Takeaways
Questions?