An app modernization story with Cloud Run
summary
App starts as an ASP.NET 4.6 monolith on IIS then moves to Compute Engine VMs, App Engine Flex, and finally Cloud Run; containers built with Docker, deployed via Google Cloud Build, logs to Stackdriver, storage in Cloud Storage, messaging with Pub/Sub, data in Cloud Firestore. The migration reduces cost to near zero (Cloud Run billing per-request), cuts deployments from minutes to seconds, and breaks the monolith into three services with reader → Cloud Storage, converter triggered by Pub/Sub → Firestore, web API serving clients, all working with functional tests.
AI-written summary · about
chapters (20)
- 0:00Intro
- 3:52Stage O: Prototype (Late 2015 / Early 2016) Goal: Get something up and running
- 6:53Prototype: Pros & Cons
- 9:58Prototype: Lessons Learned
- 14:02Lift & Shift (Late 2016 / Early 2017) Goal: Improve resiliency and redundancy
- 16:36Lift & Shift: Pros & Cons
- 19:09Lift & Shift: Lessons Learned
- 19:45The app served us well until 2019...
- 22:03Containarization (Early 2019) Goal: Remove Windows dependency and cost
- 24:42Containarization: Pros & Cons
- 28:14Containarization: Lessons Learned
- 31:19Around mid 2019...
- 32:34HTTPS Endpoint
- 33:01Billable time
- 37:16Serverless: Pros & Cons
- 38:47Monolith issues
- 40:46Monolith decomposition questions
- 42:49Monolith to microservices (Early 2020)
- 46:42Monolith to microservices: Pros & Cons
- 49:06Grand Lessons Learned
related talks
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
25mAutobahn in the cloud
58mJourney to the Cloud - a Rearchitecting Story
27mMicro-transformation
11mAbstracting infrastructure away from developers
43mSolving Scalability by Converting a Monolith into Microservices
33mChopping the monolith
30mPragmatic App Migration to the Cloud