Published a new episode of AWS Bites podcast
37. How do you migrate a monolith to AWS without the drama?
https://www.youtube.com/watch?v=GYa2RkYDfBQ
Migrating monoliths to the cloud can be a scary, expensive and time consuming and time consuming activity. Many companies try to avoid it even if it could be beneficial for them, just because they think it would require too much work and be too risky. But there are interesting compromises and incremental approaches that can be used to simplify and de-risk this kind of migration. The idea is that you don’t necessarily have to dramatically re-engineer your application to move it to the cloud (and start to take advantage of it).
In this episode, based on an InfoQ article that we recently published, we discuss a fictional use case where a company with a monolithic application managed to move to the cloud with a minimum amount of change. The move to the cloud has brought more scalability and resilience for the company to move forward and expand. But it also brings new challenges and opportunities. We will discuss all of this in more detail and by the end of this episode you should have a checklist for migrating monoliths to the cloud with minimal effort.
⏱ timestamps:
00:00 Intro
01:12 Case study: a fictitious legal startup
02:50 What is the problem we are trying to solve with moving to the cloud?
05:40 What kind of tradeoffs can we suggest?
06:50 The new architecture: ALB + EC2 instances + S3 + RDS + ElastiCache
10:10 First steps: learning Infrastructure as Code and AWS Networking
13:18 Next step: data migration (files, database and session storage)
19:02 Next step: deploying the application code (AMIs and operational mindset shift)
22:37 Going live: HTTPS and DNS
25:25 Knowledge gap and other things the team needs to learn
27:50 What's next: opportunities and challenges
31:38 Wrapping up
In this episode, we mentioned the following resources:
- InfoQ article “A Recipe to Migrate and Scale Monoliths in the Cloud”: https://www.infoq.com/articles/cloud-...
- Our previous episode about other cloud migration strategies: https://www.youtube.com/watch?v=IDh4e...
- Our previous episode about the difference between CloudFormation and Terraform for infrastructure as code: https://www.youtube.com/watch?v=mLkOH...
- Our previous episode about the pros and cons of CDK for infrastructure as code: https://www.youtube.com/watch?v=jjyNT...
This episode is also available on YouTube: https://www.youtube.com/AWSBites
You can listen to AWS Bites wherever you get your podcasts:
- Apple Podcasts: https://podcasts.apple.com/us/podcast...
- Spotify: https://open.spotify.com/show/3Lh7Pzq...
- Google: https://podcasts.google.com/feed/aHR0...
- Breaker: https://www.breaker.audio/aws-bites
- RSS: https://anchor.fm/s/6a3312a0/podcast/rss
Do you have any AWS questions you would like us to address?
Leave a comment here or connect with us on Twitter:
- https://twitter.com/eoins
- https://twitter.com/loige
#aws #monolith #migration
Migrating monoliths to the cloud can be a scary, expensive and time consuming and time consuming activity. Many companies try to avoid it even if it could be beneficial for them, just because they think it would require too much work and be too risky. But there are interesting compromises and incremental approaches that can be used to simplify and de-risk this kind of migration. The idea is that you don’t necessarily have to dramatically re-engineer your application to move it to the cloud (and start to take advantage of it).
In this episode, based on an InfoQ article that we recently published, we discuss a fictional use case where a company with a monolithic application managed to move to the cloud with a minimum amount of change. The move to the cloud has brought more scalability and resilience for the company to move forward and expand. But it also brings new challenges and opportunities. We will discuss all of this in more detail and by the end of this episode you should have a checklist for migrating monoliths to the cloud with minimal effort.
⏱ timestamps:
00:00 Intro
01:12 Case study: a fictitious legal startup
02:50 What is the problem we are trying to solve with moving to the cloud?
05:40 What kind of tradeoffs can we suggest?
06:50 The new architecture: ALB + EC2 instances + S3 + RDS + ElastiCache
10:10 First steps: learning Infrastructure as Code and AWS Networking
13:18 Next step: data migration (files, database and session storage)
19:02 Next step: deploying the application code (AMIs and operational mindset shift)
22:37 Going live: HTTPS and DNS
25:25 Knowledge gap and other things the team needs to learn
27:50 What's next: opportunities and challenges
31:38 Wrapping up
In this episode, we mentioned the following resources:
- InfoQ article “A Recipe to Migrate and Scale Monoliths in the Cloud”: https://www.infoq.com/articles/cloud-...
- Our previous episode about other cloud migration strategies: https://www.youtube.com/watch?v=IDh4e...
- Our previous episode about the difference between CloudFormation and Terraform for infrastructure as code: https://www.youtube.com/watch?v=mLkOH...
- Our previous episode about the pros and cons of CDK for infrastructure as code: https://www.youtube.com/watch?v=jjyNT...
This episode is also available on YouTube: https://www.youtube.com/AWSBites
You can listen to AWS Bites wherever you get your podcasts:
- Apple Podcasts: https://podcasts.apple.com/us/podcast...
- Spotify: https://open.spotify.com/show/3Lh7Pzq...
- Google: https://podcasts.google.com/feed/aHR0...
- Breaker: https://www.breaker.audio/aws-bites
- RSS: https://anchor.fm/s/6a3312a0/podcast/rss
Do you have any AWS questions you would like us to address?
Leave a comment here or connect with us on Twitter:
- https://twitter.com/eoins
- https://twitter.com/loige
#aws #monolith #migration