Thread by @sheenbrisals

Great thoughts & opinions in 👇 and in Jeremy's bit.ly/3prk4OA

To me, @awscloud should focus on providing a #Serverless adoption & application experience (AX) than simply improving DX by mixing a bit of UX and getting nowhere. 🧵
1/

https://twitter.com/loujaybee/status/1473946267713777668

As a cloud prvoider and with the scale of services and adoption, for #AWS, it's difficult to play the balancing act.

Too few service cause frustration and too many services lead to confusion. Adding more new services is not always a healthy situation.
2/

As Jeremy mentioned, the maturity of the existing services is crucial. He also beautifully described what a DX is in the cloud world. It's not about adding some UX and calling it DX.
3/

AWS can add a tonne of DX/UX to DynamoDB, for example. The matter of the fact is, in a high volume production environment with 10s or 100s of tables and millions or billions of items, the console is not the answer nor is that opinionated PartiQL thing.
4/

The focus for #AWS should be to fill the gaps that already exists. Take Cognito. If you use it as the oauth provider, then it's the one standing between having a DR setup for #Serverless application in another region. us-east-1 can happen anywhere. It's just a matter of time.
5/

Add intelligence into the services so that they don't require more DX to work on them.

#EventBridge has grown to be a pivotal service. Make it stronger faster add features to promote adoption further.

Bring open standards to the services to mute the 'vendor lock-in' debates
6/

We of course need intelligent frameworks, and there are several now and more coming out everyday. However, the abstractions can only go so far.
Enterprise scale adoption is not just about abstracted frameworks. Visibility and control play major roles in the adoption process.
7/

Enterprises have preferences as to which type of data store to use, which region/country/continent to keep the data.

This is true when it comes to many other service choices and influence the tools and framework selection.
8/

It's healthy to have these conversations & opinions from our experiences. Taking stock of these & coming out with the best is what needed from #AWS.

I would be rather happy if AWS brought services that we can deploy in prod to serve customers than some opinionated IDE.
/end