Thread by @akadapa

I woke up to a great twitter thread from @QuinnyPig. As always, @QuinnyPig has a good twitter thread on mechanics and some technical details on what it means when @awscloud says it is will boot Parler off of #AWS

2 points: WHAT and HOW you build on #Cloud

Two points are most important for any business that builds on Cloud: (1) WHAT is built on Cloud and (2) HOW it is built on it?

There are some great points here and wanted to start a twitter thread on my own quoting @QuinnyPig.

Quoting @QuinnyPig (emphasis added)...
"Making WHAT you built on AWS's systems work elsewhere is super challenging."

This making it "elsewhere" whether another cloud or on-premise servers requires how the original technical architecture and solution(s) are built.

It is not a binary choice and requires a cross-teams organization, design, planning and execution. Requiring highly technical skillsets. As @QuinnyPig mentioned the Web and the mobile Apps use different sets of application stack, programming languages, tools and services.

As much as one wants to think that solutions are built in a modular way that may not always be the case. As Products and solutions are built, teams take a lot of #TechnicalDebt and focus on delivering on Products rather than building an ideal/right solution.

Another great item from @QuinnyPig

"These services aren't really directly compatible with other companies' offerings. Making what you built on AWS's systems work elsewhere is super challenging."

This is a super important point.

AWS, like any other businesses, has been building a #moat around its business to discourage companies that hosts services on its cloud services to not even thing about going anywhere.

Even if you want to think about that "somewhere" (such as Microsoft @Azure or Google @googlecloud ) as @QuinnyPig mentioned it is "super challenging". In other words consumes a lot of super technical effort, time, and money.

And, most importantly making them all work (after full or partial transition) for your Product or Service work the same way requires a lot of non-technical activity as well. Things are bound to fail and causing downtimes and negative #userexperience

Quoting part of @QuinnyPig "The way AWS's services work--how you create them, how long that creation process takes, how you get data onto them? They behave differently in AWS's world than elsewhere."

This relates to that "HOW" part of the solution.

At the heart of all these services is the DATA and how you operate and use the data for your users and products. It is not difficult to get the data out and load into load into another place. But...

how you get that Data out and load Data and how you build up new services to use that Data becomes gnarly at best. Not let your services get affected when you do this is super challenging for the facts that was mentioned above on how AWS built its moat.

At this point, every Cloud provider not only providing simple hosting services. They are building a lot of #PaaS (platform as a service) and this Platform is everyone's MOAT!

Finally, If you are in IT space or tangentially related to any IT work, then please follow .@QuinnyPig. Besides tech, his tweets are super funny to read!

DM me or contact me if you have any questions or want to simply discuss on some of these topics.

try @threadreaderapp to unroll this thread.