🧵Spent an hour this week with a squad building new #Serverless API on #AWS.
My main advises were-
- Break-down the #domain & think of set-piece #microservices
- Identify sync & async parts
- Think #events & event-driven
- Do event storming & develop event-driven thinking
1/3
- Identify core & support #microservices
- Perform data modelling for each microservice - queries, indexes...
- Follow #API guidelines
- Remember you're building an intelligent service. Not a proxy to 3rd party
- Make your service's contract with its clients as simple & easy
2/3
- Don't build a #monolith microservice
- #Observability - structure logs, metrics, monitoring
- API usage plan for each client & monitor
- Native #serverless service integration
- Reach out to experts for help
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/
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/