Skip to content

Commit

Permalink
update 01_solution_architecture.md
Browse files Browse the repository at this point in the history
  • Loading branch information
jonathan-vella committed Oct 16, 2023
1 parent 3d96cbb commit 9d05796
Showing 1 changed file with 8 additions and 8 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -29,14 +29,14 @@ Your team will now practice as if you were delivering a pitch to the customer. T

Being a Solutions Architect means being responsible for the design and implementation of technical solutions that meet the requirements of a business goal or project. Your solution should be based on the customer's needs and priorities. You should also consider the customer's budget and timeline.

Use the **observation chart** with all the required notes that were created during the workshop to design one more solution architectures.
Use a **storytelling strategy** to present the solution to your customer. Remember that in real life, the customer might not understand technical vocabulary. Clients may not know how a technical solution looks or how it should be presented.
Identify the **architecture style**: The first step is to identify the architecture style that suits your requirements. It could be a microservices architecture, a more traditional N-tier application, or a big data solution.
Choose the **main technology pieces**: Once you have identified the architecture style, you can start choosing the main technology pieces for the architecture. For example, if you are building a microservices architecture, you might choose to use Azure Kubernetes Service (AKS) for hosting the microservices, Azure Cosmos DB for the database, and Azure Active Directory (Azure AD) for authentication and authorization.
Design for **scalability and resilience**: Applications should be designed to scale horizontally, adding new instances as demand requires. They should also be resilient when failures occur. For example, if a microservice fails, the application should be able to continue to function without that microservice.
**Automate deployments**: Deployments must be automated and predictable. This is especially important for cloud applications, where you might need to deploy to multiple environments, such as development, test, and production.
**Monitor and gain insights**: Monitoring and telemetry are critical for gaining insight into the system. You should be able to monitor the health of the system and individual components, and you should be able to gain insights into how the system is being used.
**Refer to Azure Architecture Center**: Microsoft provides an Azure Architecture Center that offers architecture diagrams and technology descriptions for reference architectures, real-world examples of cloud architectures, and solution ideas for common workloads on Azure ³. The center also provides a guide for Azure Application Architecture that covers architecture styles for cloud applications, technology choices, design principles, the five pillars of software quality, and cloud design patterns.
* Use the **observation chart** with all the required notes that were created during the workshop to design one more solution architectures.
* Use a **storytelling strategy** to present the solution to your customer. Remember that in real life, the customer might not understand technical vocabulary. Clients may not know how a technical solution looks or how it should be presented.
* Identify the **architecture style**: The first step is to identify the architecture style that suits your requirements. It could be a microservices architecture, a more traditional N-tier application, or a big data solution.
* Choose the **main technology pieces**: Once you have identified the architecture style, you can start choosing the main technology pieces for the architecture. For example, if you are building a microservices architecture, you might choose to use Azure Kubernetes Service (AKS) for hosting the microservices, Azure Cosmos DB for the database, and Azure Active Directory (Azure AD) for authentication and authorization.
* Design for **scalability and resilience**: Applications should be designed to scale horizontally, adding new instances as demand requires. They should also be resilient when failures occur. For example, if a microservice fails, the application should be able to continue to function without that microservice.
* **Automate deployments**: Deployments must be automated and predictable. This is especially important for cloud applications, where you might need to deploy to multiple environments, such as development, test, and production.
* **Monitor and gain insights**: Monitoring and telemetry are critical for gaining insight into the system. You should be able to monitor the health of the system and individual components, and you should be able to gain insights into how the system is being used.
* **Refer to Azure Architecture Center**: Microsoft provides an Azure Architecture Center that offers architecture diagrams and technology descriptions for reference architectures, real-world examples of cloud architectures, and solution ideas for common workloads on Azure ³. The center also provides a guide for Azure Application Architecture that covers architecture styles for cloud applications, technology choices, design principles, the five pillars of software quality, and cloud design patterns.

**Participant steps**

Expand Down

0 comments on commit 9d05796

Please sign in to comment.