Path to Cloud-native Application Development: 8 steps
summary
Eight concrete steps for cloud-native migration with examples: move monolith to containers (OpenShift on Kubernetes), adopt CI/CD and rolling / blue‑green / canary deployments, build self‑service on‑demand infrastructure, and prefer use non‑blocking reactive runtimes where appropriate. Demo shows a gateway calling eight inventory services with 100 ms artificial delay: a blocking Spring Boot path stacks to ~850 ms and 90% success under load, while a Vert.x reactive path drops to ~150 ms, 100% success and ~36 tps. Tracing uses Jaeger; API management example: 3scale.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:46EVOLUTION OF CLOUD APPS/SVCS/FMWKS
- 3:18DIGITAL LEADER PAYOFF
- 4:34SPEEDING UP DEVELOPMENT & DELIVERY
- 5:43DEVELOPMENT AND OPERATIONAL CONCERNS
- 6:26WHAT IS CLOUD-NATIVE APP DEVELOPMENT
- 7:16TRADITIONAL VS. CLOUD-NATIVE APP DEV
- 8:27EVOLVE A DEVOPS CULTURE & PRACTICES
- 9:28SPEED UP EXISTING APPLICATIONS
- 11:14USE APPLICATION SERVICES
- 12:20CHOOSE RIGHT TOOL FOR RIGHT TASK
- 14:05COOLSTORE SERVICES
- 14:23CHAINING OF SERVICE
- 25:265: SELF-SERVICE ON-DEMAND INFRA
- 26:55AUTOMATE IT TO ACCELERATE DELIVERY
- 28:26IMPLEMENT CI/CD & ADV DEPLOY TECH
- 30:55EVOLVE A MORE MODULAR ARCH
- 33:48BUILD MODERN APPS
- 34:26FREE e-BOOK Building Microservices with Enterprise Java
related talks
51mSingle Entry Point or Single Point of Failure: The Path to a Non-blocking API Gateway
40mReactive programming: lessons learned
48mReactive Microservices with Spring Boot and JHipster
52mTesting Reactive Apps
42mReacting to the Future of Application Architecture
43mMigrating from Imperative to Reactive
58mReactive Spring
45mShould I migrate to Reactive and how?