Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/Azure/Solution-Architecture-Questions
For you to share with your customers
https://github.com/Azure/Solution-Architecture-Questions
Last synced: 2 months ago
JSON representation
For you to share with your customers
- Host: GitHub
- URL: https://github.com/Azure/Solution-Architecture-Questions
- Owner: Azure
- License: cc-by-4.0
- Created: 2020-04-22T15:51:58.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2021-07-26T18:03:07.000Z (over 3 years ago)
- Last Synced: 2024-10-29T19:40:00.563Z (3 months ago)
- Homepage:
- Size: 104 KB
- Stars: 37
- Watchers: 8
- Forks: 19
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
- awesome-azure-architecture - Solution Architecture Questions
README
# Solution Architecture Questions
This repository is a checklist of questions to ask yourself and your customer when designing a new cloud solution architecture or migrating an existing archtiecture to the cloud.
## Intent
As a Cloud Solution Architect, we need to be able to quickly vet and understand a wide range of solutions before starting the discussing implementation. These pages are designed to help cover all bases during the investigation stage of a project.
## How to use
Each top-level Domain is broken up into a separate page which covers that domain and its relevant subdomains.
To start, it's recommended to investigate each of the domains at a high level and then dig deeper as the conversation warrants.
* [Architecture](docs/architecture.md) - Software Architecture of the solution
* [Business Context](docs/business-context.md) - Customer type, Industry, Licensing, etc.
* [Partnership](docs/partnership.md) - Goals, Marketplace
* [Project](docs/project.md) - Design/Operations Team, Success Criteria
* [Software Development Life Cycle (SDLC)](docs/sdlc.md) - DevOps, Environments
* [Technical Requirements](docs/technical-requirements.md) - Resiliency, HA/BC/DR, Observability, Scaling# Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [[email protected]](mailto:[email protected]) with any additional questions or comments.# Legal Notices
Microsoft and any contributors grant you a license to the Microsoft documentation and other content
in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode),
see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the
[LICENSE-CODE](LICENSE-CODE) file.Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.Privacy information can be found at https://privacy.microsoft.com/en-us/
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents,
or trademarks, whether by implication, estoppel or otherwise.