From d9ab8e77aca1aaefc36ff8166bcadd67597a58ed Mon Sep 17 00:00:00 2001 From: Luke Murray <24467442+lukemurraynz@users.noreply.github.com> Date: Fri, 29 Mar 2024 18:54:56 +1300 Subject: [PATCH 1/5] Update services.md Minor readability enhancements. --- docs/aws-professional/services.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/aws-professional/services.md b/docs/aws-professional/services.md index d0fdb85240..1b9a07de5c 100644 --- a/docs/aws-professional/services.md +++ b/docs/aws-professional/services.md @@ -39,7 +39,7 @@ products: # AWS to Azure services comparison -This article helps you understand how Microsoft Azure services compare to Amazon Web Services (AWS). Whether you are planning a multicloud solution with Azure and AWS, or migrating to Azure, you can compare the IT capabilities of Azure and AWS services in all categories. +This article helps you understand how Microsoft Azure services compare to Amazon Web Services (AWS). Whether you are planning a multi-cloud solution with Azure and AWS or migrating to Azure, you can compare the IT capabilities of Azure and AWS services in all categories. This article compares services that are roughly comparable. Not every AWS service or Azure service is listed, and not every matched service has exact feature-for-feature parity. @@ -149,7 +149,7 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | [QuickSight](https://aws.amazon.com/quicksight) | [Power BI](https://powerbi.microsoft.com/) | Business intelligence tools that build visualizations, perform ad hoc analysis, and develop business insights from data. | [CloudSearch](https://aws.amazon.com/cloudsearch) | [Cognitive Search](https://azure.microsoft.com/services/search/) | Delivers full-text search and related search analytics and capabilities. | | [Athena](https://aws.amazon.com/athena) | [Data Lake Analytics](https://azure.microsoft.com/services/data-lake-analytics)

[Azure Synapse Analytics](/azure/synapse-analytics/overview-what-is)| Provides a serverless interactive query service that uses standard SQL for analyzing databases.

Azure Synapse Analytics is a limitless analytics service that brings together data integration, enterprise data warehousing, and big data analytics. It gives you the freedom to query data on your terms, using either serverless or dedicated resources at scale.| -| [Elasticsearch Service](https://aws.amazon.com/elasticsearch-service/the-elk-stack) | [Elastic on Azure](https://azuremarketplace.microsoft.com/marketplace/apps/elastic.ec-azure-pp) | Use the Elastic Stack (Elastic, Logstash, and Kibana) to search, analyze, and visualize in real time. | +| [Elasticsearch Service](https://aws.amazon.com/elasticsearch-service/the-elk-stack) | [Elastic on Azure](https://azuremarketplace.microsoft.com/marketplace/apps/elastic.ec-azure-pp) | Use the Elastic Stack (Elastic, Logstash, and Kibana) to search, analyze, and visualize in real-time. | ### Analytics architectures @@ -258,10 +258,10 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | [Identity and Access Management (IAM)](https://aws.amazon.com/iam) | [Microsoft Entra ID](https://azure.microsoft.com/services/active-directory) | Allows users to securely control access to services and resources while offering data security and protection. Create and manage users and groups, and use permissions to allow and deny access to resources. | | [Identity and Access Management (IAM)](https://aws.amazon.com/iam) | [Azure role-based access control (RBAC)](/azure/role-based-access-control/overview) | Azure role-based access control (Azure RBAC) helps you manage who has access to Azure resources, what they can do with those resources, and what areas they have access to. | | [Organizations](https://aws.amazon.com/organizations) | [Subscription Management + Azure RBAC](/azure/azure-subscription-service-limits) | Security policy and role management for working with multiple accounts. | -| [Multi-Factor Authentication](https://aws.amazon.com/iam/features/mfa) | [Microsoft Entra ID](https://azure.microsoft.com/services/active-directory) | Safeguard access to data and applications, while meeting user demand for a simple sign-in process. | +| [Multi-Factor Authentication](https://aws.amazon.com/iam/features/mfa) | [Microsoft Entra ID](https://azure.microsoft.com/services/active-directory) | Safeguard access to data and applications while meeting user demand for a simple sign-in process. | | [Directory Service](https://aws.amazon.com/directoryservice) | [Microsoft Entra Domain Services](https://azure.microsoft.com/services/active-directory-ds) | Provides managed domain services, such as domain join, group policy, LDAP, and Kerberos/NTLM authentication, which are fully compatible with Windows Server Active Directory. | -| [Cognito](https://aws.amazon.com/cognito) | [Microsoft Entra External ID](https://azure.microsoft.com/products/active-directory/external-identities/) | A highly available, global, identity management service for consumer-facing applications that scales to hundreds of millions of identities. | -| [AWS Config](https://aws.amazon.com/config/) | [Policy](https://azure.microsoft.com/services/azure-policy/) | Azure Policy is a service in Azure that you use to create, assign, and manage policies. These policies enforce different rules and effects over your resources, so those resources stay compliant with your corporate standards and service-level agreements. | +| [Cognito](https://aws.amazon.com/cognito) | [Microsoft Entra External ID](https://azure.microsoft.com/products/active-directory/external-identities/) | A highly available, global identity management service for consumer-facing applications that scales to hundreds of millions of identities. | +| [AWS Config](https://aws.amazon.com/config/) | [Policy](https://azure.microsoft.com/services/azure-policy/) | Azure Policy is a service in Azure that you use to create, assign, and manage policies. These policies enforce different rules and effects over your resources so those resources stay compliant with your corporate standards and service-level agreements. | | [Organizations](https://aws.amazon.com/organizations) | [Management Groups](/azure/governance/management-groups/) | Azure management groups provide a level of scope above subscriptions. You organize subscriptions into containers called "management groups" and apply your governance conditions to the management groups. All subscriptions within a management group automatically inherit the conditions applied to the management group. Management groups give you enterprise-grade management at a large scale, no matter what type of subscriptions you have. | ### Encryption @@ -308,10 +308,10 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | AWS service | Azure service | Description | |------|-------------|---------------| -| [Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk) | [App Service](https://azure.microsoft.com/services/app-service) | Managed hosting platform providing easy to use services for deploying and scaling web applications and services. | +| [Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk) | [App Service](https://azure.microsoft.com/services/app-service) | Managed hosting platform providing easy-to-use services for deploying and scaling web applications and services. | | [API Gateway](https://aws.amazon.com/api-gateway) | [API Management](https://azure.microsoft.com/services/api-management) | A turnkey solution for publishing APIs to external and internal consumers. | | [CloudFront](https://aws.amazon.com/cloudfront) | [Azure Front Door](https://azure.microsoft.com/services/frontdoor) | Azure Front Door is a modern cloud content delivery network (CDN) service that delivers high performance, scalability, and secure user experiences for your content and applications. | -| [Global Accelerator](https://aws.amazon.com/global-accelerator) | [Azure Front Door](https://azure.microsoft.com/services/frontdoor) | Easily join your distributed microservices architectures into a single global application using HTTP load balancing and path-based routing rules. Automate turning up new regions and scale-out with API-driven global actions, and independent fault-tolerance to your back end microservices in Azure-or anywhere. | +| [Global Accelerator](https://aws.amazon.com/global-accelerator) | [Azure Front Door](https://azure.microsoft.com/services/frontdoor) | Easily join your distributed microservices architectures into a single global application using HTTP load balancing and path-based routing rules. Automate turning up new regions and scale-out with API-driven global actions and independent fault-tolerance to your back-end microservices in Azure or anywhere. | | [Global Accelerator](https://aws.amazon.com/global-accelerator) | [Cross-regional load balancer](/azure/load-balancer/cross-region-overview) | Distribute and load balance traffic across multiple Azure regions via a single, static, global anycast public IP address. | | [Lightsail](https://aws.amazon.com/lightsail) | [App Service](https://azure.microsoft.com/services/app-service) | Build, deploy, and scale web apps on a fully managed platform. | | [App Runner](https://aws.amazon.com/apprunner) | [Web App for Containers](https://azure.microsoft.com/services/app-service/containers) | Easily deploy and run containerized web apps on Windows and Linux. | @@ -334,7 +334,7 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | AWS service | Azure service | Description | |------|-------------|---------------| | [WorkSpaces](https://aws.amazon.com/workspaces), [AppStream 2.0](https://aws.amazon.com/appstream2) | [Azure Virtual Desktop](/azure/virtual-desktop) | Manage virtual desktops and applications to enable corporate network and data access to users, anytime, anywhere, from supported devices. Amazon WorkSpaces support Windows and Linux virtual desktops. Azure Virtual Desktop supports multi-session Windows 10 virtual desktops.| -| [WorkLink](https://aws.amazon.com/worklink) | [Application Proxy](/azure/active-directory/app-proxy/application-proxy) | Provides access to intranet applications, without requiring VPN connectivity. Amazon WorkLink is limited to iOS and Android devices.| +| [WorkLink](https://aws.amazon.com/worklink) | [Application Proxy](/azure/active-directory/app-proxy/application-proxy) | Provides access to intranet applications without requiring VPN connectivity. Amazon WorkLink is limited to iOS and Android devices.| ## Miscellaneous From 8bcd6b03997d7d01db2d9ed5fa965fe19a7c6791 Mon Sep 17 00:00:00 2001 From: Luke Murray <24467442+lukemurraynz@users.noreply.github.com> Date: Fri, 29 Mar 2024 18:58:38 +1300 Subject: [PATCH 2/5] Update self-healing.md Minor readability enhancements. --- docs/guide/design-principles/self-healing.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/guide/design-principles/self-healing.md b/docs/guide/design-principles/self-healing.md index 8d8d63faaf..0cc4d75146 100644 --- a/docs/guide/design-principles/self-healing.md +++ b/docs/guide/design-principles/self-healing.md @@ -19,15 +19,15 @@ categories: ## Design your application to be self healing when failures occur -In a distributed system, failures can happen. Hardware can fail. The network can have transient failures. Rarely, an entire service, data center, or even Azure region may experience a disruption, but even those must be planned for. +In a distributed system, failures can happen. Hardware can fail. The network can have transient failures. Rarely will an entire service, data center, or even Azure region experience a disruption, however, even those must be planned for. -Therefore, design an application to be self healing when failures occur. This requires a three-pronged approach: +Therefore, design an application that is self-healing when failures occur. This requires a three-pronged approach: - Detect failures. - Respond to failures gracefully. -- Log and monitor failures, to give operational insight. +- Log and monitor failures to give operational insight. -How you respond to a particular type of failure may depend on your application's availability requirements. For example, if you require high availability, you might deploy to multiple availability zones in a region. To avoid outages even in the unlikely event of an entire Azure region experiencing disruption, you can automatically fail over to a secondary region during a regional outage. However, that will incur a higher cost and potentially lower performance than a single-region deployment. +How you respond to a particular type of failure may depend on your application's availability requirements. For example, if you require high availability, you might deploy to multiple availability zones in a region. To avoid outages, even in the unlikely event of an entire Azure region experiencing disruption, you can automatically fail over to a secondary region during a regional outage. However, that will incur a higher cost and potentially lower performance than a single-region deployment. Also, don't just consider big events like regional outages, which are generally rare. You should focus as much, if not more, on handling local, short-lived failures, such as network connectivity failures or failed database connections. @@ -35,19 +35,19 @@ Also, don't just consider big events like regional outages, which are generally **Retry failed operations**. Transient failures may occur due to momentary loss of network connectivity, a dropped database connection, or a timeout when a service is busy. Build retry logic into your application to handle transient failures. For many Azure services, the client SDK implements automatic retries. For more information, see [Transient fault handling][transient-fault-handling] and the [Retry pattern][retry]. -**Protect failing remote services (Circuit Breaker)**. It's good to retry after a transient failure, but if the failure persists, you can end up with too many callers hammering a failing service. This can lead to cascading failures, as requests back up. Use the [Circuit Breaker pattern][circuit-breaker] to fail fast (without making the remote call) when an operation is likely to fail. +**Protect failing remote services (Circuit Breaker)**. It's good to retry after a transient failure, but if the failure persists, you can end up with too many callers hammering a failing service. This can lead to cascading failures as requests back up. Use the [Circuit Breaker pattern][circuit-breaker] to fail fast (without making the remote call) when an operation is likely to fail. -**Isolate critical resources (Bulkhead)**. Failures in one subsystem can sometimes cascade. This can happen if a failure causes some resources, such as threads or sockets, not to get freed in a timely manner, leading to resource exhaustion. To avoid this, use the [Bulkhead pattern][bulkhead] to partition a system into isolated groups, so that a failure in one partition does not bring down the entire system. +**Isolate critical resources (Bulkhead)**. Failures in one subsystem can sometimes cascade. This can happen if a failure causes some resources, such as threads or sockets, not to be freed in a timely manner, leading to resource exhaustion. To avoid this, use the [Bulkhead pattern][bulkhead] to partition a system into isolated groups so that a failure in one partition does not bring down the entire system. **Perform load leveling**. Applications may experience sudden spikes in traffic that can overwhelm services on the backend. To avoid this, use the [Queue-Based Load Leveling pattern][load-level] to queue work items to run asynchronously. The queue acts as a buffer that smooths out peaks in the load. -**Fail over**. If an instance can't be reached, fail over to another instance. For things that are stateless, like a web server, put several instances behind a load balancer or traffic manager. For things that store state, like a database, use replicas and fail over. Depending on the data store and how it replicates, this may require the application to deal with eventual consistency. +**Fail over**. If an instance can't be reached, failover to another instance. For things that are stateless, like a web server, put several instances behind a load balancer or traffic manager. For things that store state, like a database, use replicas and fail over. Depending on the data store and how it replicates, the application may have to deal with eventual consistency. **Compensate failed transactions**. In general, avoid distributed transactions, as they require coordination across services and resources. Instead, compose an operation from smaller individual transactions. If the operation fails midway through, use [Compensating Transactions][compensating-transactions] to undo any step that already completed. **Checkpoint long-running transactions**. Checkpoints can provide resiliency if a long-running operation fails. When the operation restarts (for example, it is picked up by another VM), it can be resumed from the last checkpoint. Consider implementing a mechanism that records state information about the task at regular intervals, and save this state in durable storage that can be accessed by any instance of the process running the task. In this way, if the process is shut down, the work that it was performing can be resumed from the last checkpoint by using another instance. There are libraries that provide this functionality, such as [NServiceBus](https://docs.particular.net/nservicebus/sagas) and [MassTransit](https://masstransit-project.com/usage/sagas). They transparently persist state, where the intervals are aligned with the processing of messages from queues in Azure Service Bus. -**Degrade gracefully**. Sometimes you can't work around a problem, but you can provide reduced functionality that is still useful. Consider an application that shows a catalog of books. If the application can't retrieve the thumbnail image for the cover, it might show a placeholder image. Entire subsystems might be noncritical for the application. For example, in an e-commerce site, showing product recommendations is probably less critical than processing orders. +**Degrade gracefully**. Sometimes you can't work around a problem, but you can provide reduced functionality that is still useful. Consider an application that shows a catalog of books. If the application can't retrieve the thumbnail image for the cover, it might show a placeholder image. Entire subsystems might be noncritical for the application. For example, on an e-commerce site, showing product recommendations is probably less critical than processing orders. **Throttle clients**. Sometimes a small number of users create excessive load, which can reduce your application's availability for other users. In this situation, throttle the client for a certain period of time. See the [Throttling pattern][throttle]. @@ -57,9 +57,9 @@ Also, don't just consider big events like regional outages, which are generally **Test with fault injection**. All too often, the success path is well tested but not the failure path. A system could run in production for a long time before a failure path is exercised. Use fault injection to test the resiliency of the system to failures, either by triggering actual failures or by simulating them. -**Embrace chaos engineering**. Chaos engineering extends the notion of fault injection, by randomly injecting failures or abnormal conditions into production instances. +**Embrace chaos engineering**. Chaos engineering extends the notion of fault injection by randomly injecting failures or abnormal conditions into production instances. -**Consider using availability zones**. Many Azure regions provide [availability zones](/azure/reliability/availability-zones-overview), which are isolated sets of data centers within the region. Some Azure services can be deployed *zonally*, which ensures they are placed in a specific zone, and can help to reduce latency in communicating between components in the same workload. Alternatively, some services can be deployed with *zone redundancy*, which means that Azure automatically replicates the resource across zones for high availability. Consider which approach makes provides the best set of tradeoffs for your solution. To learn more about how to design your solution to use availability zones and regions, see [Recommendations for using availability zones and regions](/azure/well-architected/resiliency/regions-availability-zones). +**Consider using availability zones**. Many Azure regions provide [availability zones](/azure/reliability/availability-zones-overview), which are isolated sets of data centers within the region. Some Azure services can be deployed *zonally*, which ensures they are placed in a specific zone and can help reduce latency in communicating between components in the same workload. Alternatively, some services can be deployed with *zone redundancy*, which means that Azure automatically replicates the resource across zones for high availability. Consider which approach provides the best set of tradeoffs for your solution. To learn more about how to design your solution to use availability zones and regions, see [Recommendations for using availability zones and regions](/azure/well-architected/resiliency/regions-availability-zones). For a structured approach to making your applications self healing, see [Design reliable applications for Azure][resiliency-overview]. From 6544b1a297262721ac153570f8c02c9e50dda7dd Mon Sep 17 00:00:00 2001 From: Luke Murray <24467442+lukemurraynz@users.noreply.github.com> Date: Fri, 29 Mar 2024 19:46:49 +1300 Subject: [PATCH 3/5] Update automate-document-classification-durable-functions-content.md Updated Azure Cognitive Search to: Azure AI Search, as per product rename. --- ...ent-classification-durable-functions-content.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/ai-ml/architecture/automate-document-classification-durable-functions-content.md b/docs/ai-ml/architecture/automate-document-classification-durable-functions-content.md index edb6593a6b..d222dcb748 100644 --- a/docs/ai-ml/architecture/automate-document-classification-durable-functions-content.md +++ b/docs/ai-ml/architecture/automate-document-classification-durable-functions-content.md @@ -20,7 +20,7 @@ This article describes an architecture for processing document files that contai > Azure doesn’t offer a service that can classify multiple document types in a single file. This solution uses a non-Azure service that's hosted in AKS. 1. The Metadata Store activity function saves the document type and page range information in an Azure Cosmos DB store. -1. The Indexing activity function creates a new search document in the Cognitive Search service for each identified document type and uses the [Azure Cognitive Search libraries for .NET](/dotnet/api/overview/azure/search?view=azure-dotnet) to include in the search document the full OCR results and document information. A correlation ID is also added to the search document so that the search results can be matched with the corresponding document metadata from Azure Cosmos DB. +1. The Indexing activity function creates a new search document in the Cognitive Search service for each identified document type and uses the [Azure AI Search libraries for .NET](/dotnet/api/overview/azure/search?view=azure-dotnet) to include in the search document the full OCR results and document information. A correlation ID is also added to the search document so that the search results can be matched with the corresponding document metadata from Azure Cosmos DB. 1. End users can search for documents by contents and metadata. Correlation IDs in the search result set can be used to look up document records that are in Azure Cosmos DB. The records include links to the original document file in Blob Storage. ### Components @@ -30,7 +30,7 @@ This article describes an architecture for processing document files that contai - [Azure Storage](https://azure.microsoft.com/product-categories/storage) is a set of massively scalable and secure cloud services for data, apps, and workloads. It includes [Blob Storage](https://azure.microsoft.com/products/storage/blobs), [Azure Files](https://azure.microsoft.com/products/storage/files), [Azure Table Storage](https://azure.microsoft.com/products/storage/tables), and [Azure Queue Storage](https://azure.microsoft.com/products/storage/queues). - [Azure App Service](https://azure.microsoft.com/products/app-service) provides a framework for building, deploying, and scaling web apps. The Web Apps feature is an HTTP-based service for hosting web applications, REST APIs, and mobile back ends. With Web Apps, you can develop in .NET, .NET Core, Java, Ruby, Node.js, PHP, or Python. Applications easily run and scale in Windows and Linux-based environments. - [Azure Cognitive Services](https://azure.microsoft.com/products/cognitive-services) provides intelligent algorithms to see, hear, speak, understand, and interpret your user needs by using natural methods of communication. -- [Azure Cognitive Search](https://azure.microsoft.com/products/search) provides a rich search experience over private, heterogeneous content in web, mobile, and enterprise applications. +- [Azure AI Search](https://azure.microsoft.com/products/search) provides a rich search experience over private, heterogeneous content in web, mobile, and enterprise applications. - [AKS](https://azure.microsoft.com/products/kubernetes-service) is a highly available, secure, and fully managed Kubernetes service. AKS makes it easy to deploy and manage containerized applications. ### Alternatives @@ -72,7 +72,7 @@ A reliable workload is one that's both resilient and available. Resiliency is th For reliability information about solution components, see the following resources: -- [SLA for Azure Cognitive Search](https://azure.microsoft.com/support/legal/sla/search/v1_0) +- [SLA for Azure AI Search](https://azure.microsoft.com/support/legal/sla/search/v1_0) - [SLA for Azure Applied AI Services](https://azure.microsoft.com/support/legal/sla/azure-applied-ai-services/v1_0) - [SLA for Azure Functions](https://azure.microsoft.com/support/legal/sla/functions/v1_2) - [SLA for App Service](https://azure.microsoft.com/support/legal/sla/app-service/v1_5) @@ -84,9 +84,9 @@ For reliability information about solution components, see the following resourc Cost optimization is about reducing unnecessary expenses and improving operational efficiencies. For more information, see [Overview of the cost optimization pillar](/azure/architecture/framework/cost/overview). -The most significant costs for this architecture will potentially come from the storage of image files in the storage account, Cognitive Services image processing, and index capacity requirements in the Azure Cognitive Search service. +The most significant costs for this architecture will potentially come from the storage of image files in the storage account, Cognitive Services image processing, and index capacity requirements in the Azure AI Search service. -Costs can be optimized by [right sizing](/azure/architecture/framework/services/storage/storage-accounts/cost-optimization) the storage account by using reserved capacity and lifecycle policies, proper [Azure Cognitive Search planning](/azure/search/search-sku-manage-costs) for regional deployments and operational scale up scheduling, and using [commitment tier pricing](/azure/cognitive-services/commitment-tier) that's available for the Computer Vision – OCR service to manage [predictable costs](/azure/cognitive-services/plan-manage-costs). +Costs can be optimized by [right sizing](/azure/architecture/framework/services/storage/storage-accounts/cost-optimization) the storage account by using reserved capacity and lifecycle policies, proper [Azure AI Search planning](/azure/search/search-sku-manage-costs) for regional deployments and operational scale up scheduling, and using [commitment tier pricing](/azure/cognitive-services/commitment-tier) that's available for the Computer Vision – OCR service to manage [predictable costs](/azure/cognitive-services/plan-manage-costs). Here are some guidelines for optimizing costs: @@ -118,7 +118,7 @@ Introductory articles: - [Introduction to Azure Storage](/azure/storage/common/storage-introduction) - [What are Durable Functions?](/azure/azure-functions/durable/durable-functions-overview?tabs=csharp) - [What are Azure Cognitive Services?](/azure/cognitive-services/what-are-cognitive-services) -- [What’s Azure Cognitive Search?](/azure/search/search-what-is-azure-search) +- [What’s Azure AI Search?](/azure/search/search-what-is-azure-search) - [App Service overview](/azure/app-service/overview) - [Introduction to Azure Cosmos DB](/azure/cosmos-db/introduction) - [Azure Kubernetes Service](/azure/aks/intro-kubernetes) @@ -129,7 +129,7 @@ Product documentation: - [Azure documentation (all products)](/azure?product=all) - [Durable Functions documentation](/azure/azure-functions/durable) - [Azure Cognitive Services documentation](/azure/cognitive-services) -- [Azure Cognitive Search documentation](/azure/search) +- [Azure AI Search documentation](/azure/search) ## Related resources From f35e8d7c9df331c5ef8fbbb1eb1dc18a558b9bc2 Mon Sep 17 00:00:00 2001 From: Chad Kittel Date: Fri, 29 Mar 2024 08:53:33 -0500 Subject: [PATCH 4/5] Apply suggestions from code review --- docs/aws-professional/services.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/aws-professional/services.md b/docs/aws-professional/services.md index 1b9a07de5c..16f10fceed 100644 --- a/docs/aws-professional/services.md +++ b/docs/aws-professional/services.md @@ -39,7 +39,7 @@ products: # AWS to Azure services comparison -This article helps you understand how Microsoft Azure services compare to Amazon Web Services (AWS). Whether you are planning a multi-cloud solution with Azure and AWS or migrating to Azure, you can compare the IT capabilities of Azure and AWS services in all categories. +This article helps you understand how Microsoft Azure services compare to Amazon Web Services (AWS). Whether you are planning a multicloud solution with Azure and AWS or migrating to Azure, you can compare the IT capabilities of Azure and AWS services in all categories. This article compares services that are roughly comparable. Not every AWS service or Azure service is listed, and not every matched service has exact feature-for-feature parity. @@ -149,7 +149,7 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | [QuickSight](https://aws.amazon.com/quicksight) | [Power BI](https://powerbi.microsoft.com/) | Business intelligence tools that build visualizations, perform ad hoc analysis, and develop business insights from data. | [CloudSearch](https://aws.amazon.com/cloudsearch) | [Cognitive Search](https://azure.microsoft.com/services/search/) | Delivers full-text search and related search analytics and capabilities. | | [Athena](https://aws.amazon.com/athena) | [Data Lake Analytics](https://azure.microsoft.com/services/data-lake-analytics)

[Azure Synapse Analytics](/azure/synapse-analytics/overview-what-is)| Provides a serverless interactive query service that uses standard SQL for analyzing databases.

Azure Synapse Analytics is a limitless analytics service that brings together data integration, enterprise data warehousing, and big data analytics. It gives you the freedom to query data on your terms, using either serverless or dedicated resources at scale.| -| [Elasticsearch Service](https://aws.amazon.com/elasticsearch-service/the-elk-stack) | [Elastic on Azure](https://azuremarketplace.microsoft.com/marketplace/apps/elastic.ec-azure-pp) | Use the Elastic Stack (Elastic, Logstash, and Kibana) to search, analyze, and visualize in real-time. | +| [Elasticsearch Service](https://aws.amazon.com/elasticsearch-service/the-elk-stack) | [Elastic on Azure](https://azuremarketplace.microsoft.com/marketplace/apps/elastic.ec-azure-pp) | Use the Elastic Stack (Elastic, Logstash, and Kibana) to search, analyze, and visualize in real time. | ### Analytics architectures @@ -308,7 +308,7 @@ For an overview of Azure for AWS users, see [Introduction to Azure for AWS profe | AWS service | Azure service | Description | |------|-------------|---------------| -| [Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk) | [App Service](https://azure.microsoft.com/services/app-service) | Managed hosting platform providing easy-to-use services for deploying and scaling web applications and services. | +| [Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk) | [App Service](https://azure.microsoft.com/services/app-service) | Managed hosting platform providing easy to use services for deploying and scaling web applications and services. | | [API Gateway](https://aws.amazon.com/api-gateway) | [API Management](https://azure.microsoft.com/services/api-management) | A turnkey solution for publishing APIs to external and internal consumers. | | [CloudFront](https://aws.amazon.com/cloudfront) | [Azure Front Door](https://azure.microsoft.com/services/frontdoor) | Azure Front Door is a modern cloud content delivery network (CDN) service that delivers high performance, scalability, and secure user experiences for your content and applications. | | [Global Accelerator](https://aws.amazon.com/global-accelerator) | [Azure Front Door](https://azure.microsoft.com/services/frontdoor) | Easily join your distributed microservices architectures into a single global application using HTTP load balancing and path-based routing rules. Automate turning up new regions and scale-out with API-driven global actions and independent fault-tolerance to your back-end microservices in Azure or anywhere. | From 1ce2c02a022dbee60c52ba85a55b72263ad1b8b2 Mon Sep 17 00:00:00 2001 From: Chad Kittel Date: Fri, 29 Mar 2024 09:15:30 -0500 Subject: [PATCH 5/5] Update docs/guide/design-principles/self-healing.md --- docs/guide/design-principles/self-healing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/design-principles/self-healing.md b/docs/guide/design-principles/self-healing.md index 0cc4d75146..578e995b8d 100644 --- a/docs/guide/design-principles/self-healing.md +++ b/docs/guide/design-principles/self-healing.md @@ -41,7 +41,7 @@ Also, don't just consider big events like regional outages, which are generally **Perform load leveling**. Applications may experience sudden spikes in traffic that can overwhelm services on the backend. To avoid this, use the [Queue-Based Load Leveling pattern][load-level] to queue work items to run asynchronously. The queue acts as a buffer that smooths out peaks in the load. -**Fail over**. If an instance can't be reached, failover to another instance. For things that are stateless, like a web server, put several instances behind a load balancer or traffic manager. For things that store state, like a database, use replicas and fail over. Depending on the data store and how it replicates, the application may have to deal with eventual consistency. +**Fail over**. If an instance can't be reached, fail over to another instance. For things that are stateless, like a web server, put several instances behind a load balancer or traffic manager. For things that store state, like a database, use replicas and fail over. Depending on the data store and how it replicates, the application might have to deal with eventual consistency. **Compensate failed transactions**. In general, avoid distributed transactions, as they require coordination across services and resources. Instead, compose an operation from smaller individual transactions. If the operation fails midway through, use [Compensating Transactions][compensating-transactions] to undo any step that already completed.