Slide 1

Slide 1 text

Shaping Tomorrow’s Technology: Navigating Cloud-Native, Serverless with Java Shaaf Syed Principal Architect, Red Hat ORGANIZERS:

Slide 2

Slide 2 text

Shaping Tomorrow’s Technology: Navigation Cloud-Native, Serverless with Java fosstodon.org/@shaaf @syshaaf sshaaf https://www.linkedin.com/in/shaaf/ shaaf.dev Java developer, architect, advocate @RedHat, 🐧 β˜• , open source enthusiast, Technical editor at @InfoQ , 🏏 coach 🧒 πŸ”­ I’m currently working @Red Hat β˜• Mostly backend Java development, and maybe some node sometimes.. 🌱 Java Technical editor @Infoq 🀝 I’m a cricket coach @ Glostrup Cricket πŸ“ I regularly write articles on https://shaaf.dev πŸ’¬ Ask me about Java, backends and architecture

Slide 3

Slide 3 text

Too many tech words in the title talk cloud native Serverless Java

Slide 4

Slide 4 text

Knative is more than Serverless

Slide 5

Slide 5 text

Monolith Microservice Function f( ) Architecture Evolution ❖ Self-contained software ❖ Fewer cross-cutting concerns ❖ Lack of flexibility ❖ Difficult to Scale ❖ Difficult to maintain, update, and deploy ❖ Multiple, loosely coupled, independent services ❖ More scalable ❖ More flexible ❖ More Complex Development ❖ Easier to maintain, update, and deploy services individually ❖ Single purpose, event driven ❖ Easy development ❖ Highly scalable ❖ Highly flexible ❖ More Complex Deployment ❖ Cold start latency

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

Our Monolith’s Architecture & Challenges βž” Scaling challenges e.g. individual components or app βž” Lifecycle is prolonged due to dependencies βž” Everything runs in the same process βž” Technical debt, hard to innovate βž” CI/CD

Slide 8

Slide 8 text

Breaking down components into services βž” Scaling is more independent to the component (hypothetically speaking..) βž” Life cycles are shorter depending on the teams βž” Everything is no longer in one big process βž” Distributed, can introduce other challenges like latency, compatibility, single point of failures etc. βž” Capacity, not all services are used all the time…. wait what???

Slide 9

Slide 9 text

Our evolved architecture- mix and match! βž” Lets try this on one service βž” Scale to Zero? βž” Only use it when a component needs it.? βž” Mix and match which ones? βž” Cost, efficiency maybe more sustainable? βž” Is it really beneficial in production?

Slide 10

Slide 10 text

Demo time!

Slide 11

Slide 11 text

Show me Event Driven Pattern- Eventing βž” Operates on a Knative Service βž” Publish an event without creating a consumer. βž” Consume an event without creating a publisher. βž” Push based approach βž” Manages data delivery (Eventing) βž” Knative Autoscaler - Demand-based autoscaling (HTTP)

Slide 12

Slide 12 text

Show me the wild scaling! - Pattern

Slide 13

Slide 13 text

Show me scaling of Events - with KEDA βž” Automatically scale Kubernetes Deployments, Jobs & Custom Resources βž” Provides 61+ built-in scalers, but users can build own external scalers βž” Kafka, Prometheus, RabbitMQ, AWS services, Azure Services,... βž” Scale resources based on events in the target scalers, eg. messages in Kafka topic βž” KEDA does not manipulate the data, just scales the workload βž” Installation through OLM Operator or Helm

Slide 14

Slide 14 text

Show me the wild scaling! - Efficiency Over provisioning Time in capacity planning IT cost of idle resources Under provisioning Lost business revenue Poor quality of service More applications Direct line between IT costs & business revenue NOT Serverless with Serverless

Slide 15

Slide 15 text

● KEDA - Kubernetes event driven autoscaling dead simple ● KEDA - pull model vs. Knative - push model ● KEDA - Standard Kubernetes resources vs. Knative Service ● KEDA can autoscale Knative Eventing Infrastructure β—‹ knative-sandbox/eventing-autoscaler-keda Takeaways - Leveraging architecture strength scale to zero scale on events

Slide 16

Slide 16 text

Show me where to find the demo source https://github.com/sshaaf/coolstore-knative

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

Thank you for watching Remember to rate the presentation and leave your questions in the section below. www.yavaconf.com ORGANIZERS: