I'm working on a project for a major insurance company that wants to migrate their on-premise IBM servers to AWS. We were sold on it being an easy transition, but what we didn't realize is the massive amount of training, and analysis paralysis involved in the migration. We had to learn Terraform, all of the AWS services etc, and then hope the firewalls were configured correctly to allow traffic in and out. The entire project is pretty chaotic, and going slowly, so don't assume serverless and cloud migrations means less work and planning.

Great breakdown of the serverless space!

Great video, keep up the good content

Dude, I enjoy the way you break things down :0

Very well put together video 👌🏼

My man held the strawberry throughout the video. Love the music btw 💙

great video, great strawberry

On top of breaking things down I also really like the product recommendations

Good video. Have an algorithm boost

what do you think about people who build their application on serverless and try to make the transition to cloud native? (please whisper me on twitter though!!! (giving you those algo juices))

If you are working on solving the problem and bringing the best of both world, let's name that strawberry 🍓

It took me 7 minutes to notice the strawberry. Great breakdown tho

What to do you think? Which one is the ultimate stack for serverless apps

Nice video, you are missing a new one on the block: winglang

Do you have a link for serverless & architect frameworks - since they're pretty common terms identifying the specific framework is not straightforward?

Bro your channel is great all you need to do is buy a better microphone. Other than that your content is great and you explain things very nicely.

Great video, thank you so much! Could you please share the twitter thread from 5:04 🙏

Thats a fine point. But can your serverless solution do this? **drops database*

Very informative! I learned a lot from this video. However, I think there is a fundamental problem that will continue to lead to specialization and/or lock-in, which is the incentive to monetize. It's not a coincidence that tons of options popped up with specific apis that lock you in to their products, or that big cloud providers are trying to provide "alternatives" to fragmentation that still lock you into their ecosystem. Lock in is something every profit driven organization is going to be incentivized into and specialization helps smaller organizations compete with larger organizations that try to offer more generalized solutions (that lock you in to their ecosystem). It is simply more difficult and/or expensive to work towards generic solutions, and leaving lock-in off the table makes it harder to ensure your org gets paid. I don't think it's impossible, just very unlikely.

First 🍓

Lol did you eat the strawberry at the start, just so that you holding the mike up wouldn't look wierd? xP

💯🍓

Might be naive, but why don't we just abstract out the cloud to be localhost

Bro is way farther than u think, he hacked his brain by making it learn that he must work (record the video) and only THEN get the reward which is the strawberry xD