There are bunch of them, really. But for general structure, using your end-user's user experience path (from start to end) as a guide and avoiding buzzwords as

There are bunch of them, really. But for general structure, using your end-user's user experience path (from start to end) as a guide and avoiding buzzwords as much as you can usually help. Think of Stripe's documentation, you want something as easily digestible as that. - Software Design Patterns: https://en.wikipedia.org/wiki/Software_design_pattern https://en.wikipedia.org/wiki/Software_design_pattern - Azure Application Architecture Guide: https://docs.microsoft.com/en-us/azure/architecture/guide/ https://docs.microsoft.com/en-us/azure/architecture/guide/ - Azure Cloud Design Patterns: https://docs.microsoft.com/en-us/azure/architecture/patterns/ https://docs.microsoft.com/en-us/azure/architecture/patterns... - Azure Architecture Framework: https://docs.microsoft.com/en-us/azure/architecture/framework/ https://docs.microsoft.com/en-us/azure/architecture/framewor... - Azure Cloud Adoption Framework: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ https://docs.microsoft.com/en-us/azure/cloud-adoption-framew... - Cloud Computing Patterns: https://www.cloudcomputingpatterns.org/ https://www.cloudcomputingpatterns.org/ - Microservice Architecture Patterns: https://microservices.io/patterns/index.html https://microservices.io/patterns/index.html - Amazon's Builders Library: https://aws.amazon.com/builders-library/ https://aws.amazon.com/builders-library/