Building Reactive Microservices with Kotlin & running on Kubernetes

Transcript

1. Sendil Kumar N & 03 Nov 2022 Building Reactive Microservices & Running on Kubernetes using KHipster @sendilkumarn
2. @sendilkumarn
3. Agenda • Why Microservices? • Why Kubernetes? • Why Reactive? • Why KHipster? • Demo @sendilkumarn
4. Why Microservices? @sendilkumarn
5. @sendilkumarn
6. de-facto standard @sendilkumarn
7. de-facto standard isolated & independent @sendilkumarn
8. de-facto standard isolated & independent granular scalability @sendilkumarn
9. de-facto standard isolated & independent granular scalability fault tolerant @sendilkumarn
10. @sendilkumarn
11. Does one thing & do it well @sendilkumarn
12. Does one thing & do it well Should avoid Single Point of Failure @sendilkumarn
13. Why Kubernetes? @sendilkumarn
14. Each service own their data @sendilkumarn
15. Each service own their data @sendilkumarn
16. Contracts @sendilkumarn
17. Contracts @sendilkumarn
18. Contracts @sendilkumarn
19. @sendilkumarn
20. How to know whether the service is running? @sendilkumarn
21. How to know whether the service is running? How to scale the services? @sendilkumarn
22. How will we know whether the service is running or not? How to know whether the service is running? How to scale the services? @sendilkumarn
23. How will we know whether the service is running or not? How to know whether the service is running? How to scale the services? How to safely update a con fi g / password? @sendilkumarn
24. Kubernetes Build / Deploy / Scale containerised apps @sendilkumarn
25. @sendilkumarn
26. How to know whether the service is running? Load Balancing & Service Discovery @sendilkumarn
27. How to know whether the service is running? How to scale the services? Load Balancing & Service Discovery Automatic Scaling based on conditions @sendilkumarn
28. How will we know whether the service is running or not? How to know whether the service is running? How to scale the services? Load Balancing & Service Discovery Automatic Scaling based on conditions Automated monitoring to start & stop services @sendilkumarn
29. How will we know whether the service is running or not? How to know whether the service is running? How to scale the services? How to safely update a password? Load Balancing & Service Discovery Automatic Scaling based on conditions Automated monitoring to start & stop services Secret & Con fi g Management @sendilkumarn
30. @sendilkumarn
31. @sendilkumarn
32. You just replaced function calls into network calls!! @sendilkumarn
33. @sendilkumarn
34. @sendilkumarn
35. @sendilkumarn
36. 50ms @sendilkumarn
37. 50ms 100ms @sendilkumarn
38. 50ms 100ms 20ms @sendilkumarn
39. 50ms 100ms 20ms 170ms @sendilkumarn
40. @sendilkumarn
41. @sendilkumarn
42. 50ms 100ms 20ms @sendilkumarn
43. 50ms 100ms 20ms 100ms @sendilkumarn
44. Non-Blocking Async communication @sendilkumarn
45. @sendilkumarn
46. Why Reactive? @sendilkumarn
47. @sendilkumarn
48. Highly interactive & fast experience @sendilkumarn
49. Highly interactive & fast experience consistent & reliable experience @sendilkumarn
50. Highly interactive & fast experience consistent & reliable experience Scale dynamically @sendilkumarn
51. Highly interactive & fast experience consistent & reliable experience Scale dynamically Less resource utilisation @sendilkumarn
52. Reactive Manifesto @sendilkumarn
53. Reactive Manifesto • Responsive Always caller will receive response as fast as possible @sendilkumarn
54. Reactive Manifesto • Responsive • Resilient Recovers quickly @sendilkumarn
55. Reactive Manifesto • Responsive • Resilient • Elastic Delivers @ Scale @sendilkumarn
56. Reactive Manifesto • Responsive • Resilient • Elastic • Message Driven Msg In Msg Out @sendilkumarn
57. Reactive Manifesto • Responsive • Resilient • Elastic • Message Driven @sendilkumarn
58. Everything should be reactive to reap bene fi ts of reactive system @sendilkumarn
59. Not for everyone @sendilkumarn
60. @sendilkumarn
61. But how can we build services with RxJava? @sendilkumarn
62. @sendilkumarn
63. @sendilkumarn
64. @PostMapping("/users") public User createUser(@Valid @RequestBody User user) { // Handle errors User result = userRepository.save(user); // do something with the result return ResponseEntity .created(new URI("/api/users/" + result.getId())) .headers(HeaderUtil.createEntityCreationAlert(...)) .body(result); } @sendilkumarn
65. Spring Reactive @sendilkumarn
66. @sendilkumarn
67. Mono @sendilkumarn
68. Mono Flow @sendilkumarn
69. Mono Flow Emit 0 or 1 value @sendilkumarn
70. Mono Flow Emit 0 or 1 value Emits 0 or many values @sendilkumarn
71. @PostMapping(“/users") Mono<User> public User createUser(@Valid @RequestBody User user) { // Handle errors User result = userRepository.save(user); // do something with the result return ResponseEntity .created(new URI("/api/users/" + result.getId())) .headers(HeaderUtil.createEntityCreationAlert(...)) .body(result); } @sendilkumarn
72. @PostMapping(“/users") Mono<User> public User createUser(@Valid @RequestBody User user) { // Handle errors return User result = userRepository.save(user) .flatMap(// do something with the result) .map(return ResponseEntity .created(new URI("/api/users/" + result.getId())) .headers(HeaderUtil.createEntityCreationAlert(...)) .body(result)); } @sendilkumarn
73. @PostMapping("/users") public Mono<User> createUser(@Valid @RequestBody User user) { // Handle errors return userRepository.save(user) .flatMap( // Do something with the result/users ) .map( result -> return ResponseEntity .created(new URI("/api/users/" + result.getId())) .headers(HeaderUtil.createEntityCreationAlert(...)) .body(result); ) } @sendilkumarn
74. But Kotlin makes it even more sweeter… @sendilkumarn
75. @PostMapping("/users") fun createUser(@Valid @RequestBody user: User) = // Handle errors userRepository.save(user) .flatMap { // Do something with the users } .map { ResponseEntity .created(URI("/api/users/${it.id}”)) .headers(HeaderUtil.createEntityCreationAlert(…)) .body(it) } @sendilkumarn
76. Kotlin @sendilkumarn
77. Kotlin • Null Safety @sendilkumarn
78. Kotlin • Null Safety • Less verbose @sendilkumarn
79. Kotlin • Null Safety • Less verbose • Co-routines @sendilkumarn
80. Kotlin • Null Safety • Less verbose • Co-routines • Expressive & Concise @sendilkumarn
81. Kotlin • Null Safety • Less verbose • Co-routines • Expressive & Concise • “Hacky” & Fun @sendilkumarn
82. Kotlin • Null Safety • Less verbose • Co-routines • Expressive & Concise • “Hacky” & Fun Java Catching up… @sendilkumarn
83. Kotlin • Null Safety • Less verbose • Co-routines • Expressive & Concise • “Hacky” & Fun Java Project Loom @sendilkumarn
84. Kotlin • Null Safety • Less verbose • Co-routines • Expressive & Concise • “Hacky” & Fun Java @sendilkumarn
85. Kotlin • Null Safety • Less verbose • Co-routines • Expressive & Concise • “Hacky” & Fun @sendilkumarn
86. Kotlin • Null Safety • Less verbose • Co-routines • Expressive & Concise • “Hacky” & Fun Personal Preference @sendilkumarn
87. Why KHipster? @sendilkumarn
88. KHipster is a open source app. generator @sendilkumarn
89. open source app generator development platform KHipster is @sendilkumarn
90. open source app generator development platform generates all bells & whistles KHipster is @sendilkumarn
91. @sendilkumarn
92. npm i -g generator-jhipster-kotlin @sendilkumarn
93. npm i -g generator-jhipster-kotlin mkdir app & cd app @sendilkumarn
94. npm i -g generator-jhipster-kotlin mkdir app & cd app khipster @sendilkumarn
95. npm i -g generator-jhipster-kotlin mkdir app & cd app khipster @sendilkumarn
96. Various options • Monolithic / Microservices • Spring WebFlux / Boot • Authentication • Database • Maven / Gradle • Web Frameworks • CI & CD • Kubernetes & Istio @sendilkumarn
97. Demo Time @sendilkumarn
98. Recap @sendilkumarn
99. Recap • Microservices splitting your services enable you to scale faster @sendilkumarn
100. Recap • Microservices • Kubernetes splitting your services enable you to scale faster super power to manage & maintain your services @scale @sendilkumarn
101. Recap • Microservices • Kubernetes • Reactive splitting your services enable you to scale faster super power to manage & maintain your services @scale makes things fast & resilient @sendilkumarn
102. Recap • Microservices • Kubernetes • Reactive • KHipster splitting your services enable you to scale faster super power to manage & maintain your services @scale makes things fast & resilient makes it easier to develop & deploy @sendilkumarn
103. Recap • Microservices • Kubernetes • Reactive • KHipster • Demo splitting your services enable you to scale faster super power to manage & maintain your services @scale makes things fast & resilient makes it easier to develop & deploy @sendilkumarn
104. Thanks Questions/Thoughts - feel free to reach out. @sendilkumarn