Developer Experience with Spring Boot on Kubernetes

As a developer, working with Kubernetes too often leads to too much cognitive load, inefficient inner development loop, and friction in the path to production. This session is structured as a series of iterations on the developer experience to improve those three aspects and boost productivity.

In the cloud-native world, being a developer might be challenging. The number of technologies and patterns to know can be overwhelming. This session presents an approach based on open-source technologies and focuses on improving the inner development loop and continuous delivery on Kubernetes. The end goal is to deliver value continuously, quickly, and reliably.

First, I’ll present several techniques for working locally effectively and productively. Should you run Kubernetes in your development environment? I’ll cover a few different options. Using Spring Boot, we’ll build a cloud-native application following the principles of test-driven development. The inner development loop will be enhanced with Cloud Native Buildpacks, Tilt, Knative, and Telepresence.

Continuous integration is a crucial practice for continuous delivery. We’ll check in code regularly, triggering an automated process to build, test, and package the application. Do you use pull requests? Relying on ArgoCD and the GitOps principles, I’ll show you how to work with temporary environments created dynamically when a new pull request is opened.

Finally, we’ll use Cartographer to glue together all these different tools and design a golden path to production on Kubernetes, providing a clear separation of concerns and letting developers focus on delivering value.

Transcript

1. Thomas Vitale Spring I/O May 19th, 2023 Developer Experience With Spring Boot on Kubernetes @vitalethomas
2. Systematic • Software Engineer and Cloud Architect. • Author of “Cloud Native Spring in Action” (Manning). • OSS contributor (Java, Spring, Cloud Native Technologies) Thomas Vitale thomasvitale.com @vitalethomas
3. Problem @vitalethomas
4. Value @vitalethomas
5. Delivering Value From idea to production Developer Production Idea @vitalethomas ?
6. Developer Experience @vitalethomas
7. Developer Experience “…developer experience could be defined as a means for capturing how developers think and feel about their activities within their working environments, with the assumption that an improvement of the developer experience has positive impacts on characteristics such as sustained team and project performance.” (F. Fagerholm, J. Münch) Developer Experience: Concept and De fi nition (F. Fagerholm, J. Münch) @vitalethomas
8. Developer Experience: Concept and De fi nition (F. Fagerholm, J. Münch) Developer Experience Conceptual Framework @vitalethomas
9. Value @vitalethomas
10. Developer Experience Tools are not enough ORGANIZATION PROCESSES TECHNOLOGY CULTURE @vitalethomas
11. Technologies Developer experience with Java on Kubernetes @vitalethomas
12. Team Topologies Organisational design for software @vitalethomas
13. Continuous Delivery Better software faster @vitalethomas
14. Goals 2 Reduced cognitive load 3 Clear and safe path to production 1 Rapid and continuous feedback loop @vitalethomas
15. Development Workflow @vitalethomas
16. Cloud Native @vitalethomas
17. From Traditional to Cloud Native Application Server, Embedded Server Runtime (JVM) Middleware (Application Server) Application (WAR/EAR) Runtime (JVM) Application (JAR) @vitalethomas
18. Containers @vitalethomas
19. Moving to Containers Application Server, Embedded Server, Container Runtime (OCI) Application (Container) Runtime (JVM) Middleware (Application Server) Application (WAR/EAR) Runtime (JVM) Application (JAR) @vitalethomas
20. Dockerfiles “Dockerfiles are easy to write, but the current development guidelines do not produce containers that are repeatable and hardened.” CNCF Software Supply Chain Security Paper https://github.com/cncf/tag-security/tree/main/supply-chain-security @vitalethomas
21. Cloud Native Buildpacks @vitalethomas
22. Image pack build Cloud Native Buildpacks From source code to container image @vitalethomas
23. Kubernetes @vitalethomas
24. Moving to Kubernetes Application Server, Embedded Server, Container, Kubernetes Runtime (OCI) Middleware (Kubernetes) Application (Container) Runtime (JVM) Middleware (Application Server) Application (WAR/EAR) Runtime (JVM) Application (JAR) Runtime (OCI) Application (Container) @vitalethomas
25. Working with Kubernetes Manifests for application deployment Deployment Deploy the application and con fi gure replication Service Expose the application from within the cluster @vitalethomas Ingress Expose the application from outside the cluster
26. Tilt @vitalethomas
27. Tilt Continuous development on Kubernetes @vitalethomas CODE BUILD RUN TEST Inner Development Loop
28. Development Workflow Inner Loop and Outer Loop Inner Loop ‣Code ‣Build ‣Run ‣Test Outer Loop ‣CI/CD ‣Compliance, security ‣Con fi guration, monitoring ‣Production deployment git push @vitalethomas
29. Inner Development Loop Code, build, test E ffi cient Inner Development Loops for Cloud Native Applications https://www.getambassador.io/resources/inner-dev-loop/ @vitalethomas
30. Skaffold @vitalethomas
31. Skaffold Continuous development on Kubernetes @vitalethomas CODE BUILD RUN TEST Inner Development Loop
32. Argo CD @vitalethomas
33. Argo CD Continuous Deployment with GitOps @vitalethomas Developer App Repo Pull Request Sync changes Temporary Environment
34. Knative @vitalethomas
35. Knative Serverless experience on Kubernetes @vitalethomas
36. Serverless Architectures Developers focus on code Focus on business logic Developer Platform Infrastructure Provisioning Workload Management Dynamic Scaling @vitalethomas
37. Knative Serving Serverless Experience on Kubernetes Developer-friendly abstractions From image to URL Autoscaling Scaling to zero Progressive Rollouts Request-driven Event-driven Cloud agnostic @vitalethomas
38. “Something a bit different than what today’s world is trying to offer - LESS tools!” @vitalethomas What does Developer Experience mean to you?
39. Capabilities over responsibilities @vitalethomas
40. Developer @vitalethomas
41. Developer Platform @vitalethomas
42. Developer Platform @vitalethomas
43. Cartographer @vitalethomas
44. Delivering Value From code to production Developer Production Application Operator Security Expert Platform Engineer @vitalethomas
45. “Something a bit different than what today’s world is trying to offer - LESS tools!” @vitalethomas “Let developers be professionals and do what they do best. Let them be proud of their work!” What does Developer Experience mean to you?
46. Kubernetes Native Choreographer Framework to build paved paths to production @vitalethomas
47. Workload API Developer-friendly interface @vitalethomas apiVersion: carto.run/v1alpha1 kind: Workload metadata: name: band-service labels: apps.kadras.io/workload-type: web spec: source: git: url: https://github.com/ThomasVitale/band-service ref: branch: main
48. Watch Source Code Testing Build Con fi guration Deployment @vitalethomas
49. cartographer.sh
50. Goals 2 Reduced cognitive load 3 Clear and safe path to production 1 Rapid and continuous feedback loop @vitalethomas
51. Backstage @vitalethomas
52. backstage.io
53. DevPod @vitalethomas
54. devpod.sh
55. Resources @vitalethomas
56. Resources • Presentation source code • Kadras: Cloud Native Platforms Toolkit • Cloud Native Buildpacks for ARM64 • Software Supply Chain Choreography • Cartographer • Cartographer CLI • Knative and Spring: Bringing back the func • Tanzu Application Platform @vitalethomas
57. https://github.com/ThomasVitale/awesome-spring
58. Thomas Vitale Spring I/O May 19th, 2023 Developer Experience With Spring Boot on Kubernetes @vitalethomas