Date: May 2023 Speaker: DaShaun Carter, Spring Developer Advocate, VMware

1. 15-Factors Spring with k8s
DaShaun Carter

2. DaShaun Carter
505 days as Spring Developer Advocate, VMware
Tanzu
411 days as Sr. Partner Solution Architect, Redis
845 days as Sr. Platform Architect,
Pivotal/VMware
985 days as VP of Engineering, Mobile Capital
Group/MedZero
1995 days as Tech Lead Engineer, Garmin Connect

3. @dashaun on (Twitter|GitHub|GitLab|LinkedIn)
https://dashaun.com
https://youtube.com/@dashaun

4. SpringOfficeHours.io

5. Session Purpose
- 15-Factors overview
- Cloud native features of kubernetes
- 15-Factor-Cloud-Native-with-k8s

6. 12-factors
Heroku
2012
12factor.net

8. 12-factor goals
Declarative Formats
Clean contracts
Dynamically scalable

10. "Platforms"
From the 12-Factor Introduction:
...Are suitable for deployment on modern cloud platforms...

11. For tech to be a real driver of innovation and growth,
IT needs to reorganize itself around
flexible and independent PLATFORMS.
- McKinsey 2019

13. Kubernetes is an open-source system for
automating deployment,
scaling,
and management of containerized applications.
https://kubernetes.io

14. Kind
Kind is a tool for running local
Kubernetes clusters
using Docker container “nodes”.
Kind

15. 12 Factor, but for the rest of us

16. Beyond the Twelve-Factor App
Title: Beyond the Twelve-Factor App
Author: Kevin Hoffman
Release date: April 2016
Publisher: O'Reilly Media, Inc.
ISBN: 9781491944035
https://www.oreilly.com/library/view/beyond-the-
twelve-factor/9781492042631/

17. More
Less
19-Factors
3-Factors

18. 15-Factors
1. One codebase, one application
2. API first
3. Dependency management
4. Design, build, release, and run
5. Configuration, credentials, and code
6. Logs
7. Disposability
8. Backing services
9. Environment parity
10. Administrative processes
11. Port binding
12. Stateless processes
13. Concurrency
14. Telemetry
15. Authentication and authorization

20. 1. One Codebase, One Application
Codebase != Repository
Version Control
"Big-A" Application
"Little-A" application

21. 2. API First
Contract
Contract Driven Development
Avoid waterfall / bottlenecks
API Catalog

23. Spring Cloud Contract

24. Spring RESTDocs

25. Dynamic API Registration

26. 3. Dependency Management
Apps need to bring their dependencies with them
Containers
Maven, Gradle, NuGet, Bundler, Godeps, PyPi

28. Buildpacks
Friends don't let friends use Dockerfiles
use buildpacks

29. Release Train

30. 4. Design, Build, Release and Run

31. Design
Design small features

32. Build
Convert code into a versioned binary artifact
Jar, tgz, Open Container Image (OCI)

33. Release
Unique
Identifiable
Auditable

34. Run
Developer Ability to run locally
Multiple Cloud Platforms
Platform provides "ilities"

35. YAML

36. Everything as Code
Infrastructure
"*ilities"
Features

37. 5. Configuration, credentials and code
Treat configuration, credentials, and code
as volatile substances that explode when combined.

38. TREAT YOUR APPS LIKE OPEN SOURCE
A litmus test
to see if you have properly externalized
your credentials and configuration
is to imagine the consequences
of your application’s source code
being pushed to GitHub.

39. Brute Force Method
1. Remove all configuration files from your artifact
2. Externalize configurations as needed until resolved

40. Code

41. Spring Cloud Configuration Server

42. Spring Cloud Kubernetes

43. Spring Cloud Vault

44. 6. Logs
Logs should be treated as event streams.

45. stdout
stderr
A truly cloud-native application
never concerns itself with routing
or storage of its output stream

46. 7. Disposability
Then Now
Assume reliable
infrastructure
Assume fragile
infrastructure
Minutes to get to steady
state
Scale up and down in
seconds

47. Startup and Shutdown

48. Healthy vs Ready

49. 8. Backing Services
data stores
messaging systems
caching systems
security
A backing service is any service
on which your application relies
for its functionality.

50. In the cloud
There is no filesystem

51. Small Print 1
An application should declare
its need for a given backing service
but allow the cloud environment
to perform the actual resource binding.

52. Small Print 2
The binding of an application
to its backing services
should be done via
external configuration.

53. Small Print 3
It should be possible to attach
and detach backing services
from an application at will,
without re-deploying the application.

54. Spring Cloud Bindings

55. Runner UI - Client Interface

56. 9. Environment Parity
It works on my machine

57. Moar Clowd
Time
People
Resources

58. Let's make 2023
the year of
Kubernetes on the laptop

59. Knative Serving

60. 10. Admin Processes
Database Migrations
Scheduled/Cron Jobs
Any "task" that is executed once

61. 11. Port Binding
Avoiding Container Determined Ports
Avoiding Micromanaging Port Assignments
Applications are backing services

62. 12. Stateless Processes
The Share Nothing Pattern
Data Caching

63. 13. Concurrency
Scale out using the process model
Horizontally not vertically

64. 14. Telemetry
Treat Apps Like Space Probes
I like to think of pushing applications
to the cloud as
launching a scientific instrument into space.

65. Application performance monitoring (APM)
Domain-specific telemetry
Health and system logs

66. Actuator

67. Micrometer

68. Prometheus RSocket Proxy

69. 15. Authentication and Authorization
Secure Endpoints
RBAC
Before production

70. Spring Security

71. Spring Authorization Server

72. Embrace continuous integration,
continuous delivery,
and the production of applications
designed to thrive in the cloud,
and you will reap rewards far and above
just what you get from a cloud-native world.
- Kevin Hoffman

73. Demo ?

74. Questions?
Thanks
@dashaun on (Twitter|GitHub|GitLab|LinkedIn)
https://dashaun.com
https://youtube.com/@dashaun