Skip to content

Commit

Permalink
add cross links
Browse files Browse the repository at this point in the history
  • Loading branch information
jstruve-catalysis authored Oct 25, 2024
1 parent f932f93 commit 479e191
Show file tree
Hide file tree
Showing 5 changed files with 7 additions and 7 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -108,4 +108,4 @@ The back end is responsible for managing product-related data, such as customer

In this blog post, we showcased the power of integrating multiple services and Azure technologies to create a straightforward user experience for AI-based content generation. From secure user sign-in to generating AI-driven content and retrieving relevant product data, the app efficiently uses Azure API Management, Azure Key Vault, and Azure OpenAI Service to meet the needs of modern applications.

In the next post, we’ll dive deeper into how the application works, covering technical details, code, and data flow diagrams.
In the [next post](https://azure.github.io/Cloud-Native/30-days-of-ia-2024/how-it-works-behind-the-scenes-of-our-ai-based-content-generation-app), we’ll dive deeper into how the application works, covering technical details, code, and data flow diagrams.
Original file line number Diff line number Diff line change
Expand Up @@ -187,4 +187,4 @@ Learn more on Technical leaders’ [guide to building intelligent apps](https://

In this post, we provided a comprehensive guide on monitoring, scaling, and optimizing applications on Azure App Service and AKS. We discussed using monitoring tools, configuring scaling strategies, and setting up alerts. Additionally, we covered best practices for continuous optimization to ensure your applications remain reliable, scalable, and cost-effective.

In the next blog, we will demonstrate a live application setup, showcasing how all these components work together in real-world use cases.
In the [next blog](https://azure.github.io/Cloud-Native/30-days-of-ia-2024/demo-our-ai-based-content-generation-app), we will demonstrate a live application setup, showcasing how all these components work together in real-world use cases.
Original file line number Diff line number Diff line change
Expand Up @@ -257,4 +257,4 @@ In this blog, we explored how to set up a CI/CD pipeline for Java and ReactJS ap

## Next

In the next blog, we’ll cover advanced topics such as monitoring and scaling these deployments.
In the [next blog](https://azure.github.io/Cloud-Native/30-days-of-ia-2024/setting-up-ci-cd-pipelines-for-azure-app-servicea-and-aks-using-azure-devops-2), we’ll cover advanced topics such as monitoring and scaling these deployments.
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ tags: [Build-Intelligent-Apps, 30-days-of-IA-2024, learn-live, demo-bytes, commu
<!-- End METADATA -->
## Part 2: Setting Up CI/CD Pipelines for Azure Kubernetes Service (AKS) Using Azure DevOps

In the previous blog, we discussed the fundamentals of setting up CI/CD pipelines for **Azure App Service**. In this blog, we will focus on how to configure a CI/CD pipeline specifically for **Azure Kubernetes Service (AKS)** using Azure DevOps. We’ll cover prerequisites, detailed YAML configurations, and how to manage deployments based on a variable group setting.
In the [previous blog](https://azure.github.io/Cloud-Native/30-days-of-ia-2024/setting-up-ci-cd-pipelines-for-azure-app-servicea-and-aks-using-azure-devops-1), we discussed the fundamentals of setting up CI/CD pipelines for **Azure App Service**. In this blog, we will focus on how to configure a CI/CD pipeline specifically for **Azure Kubernetes Service (AKS)** using Azure DevOps. We’ll cover prerequisites, detailed YAML configurations, and how to manage deployments based on a variable group setting.

## Prerequisites

Expand Down Expand Up @@ -379,4 +379,4 @@ Similar to **Blog 1.6a**, manually trigger the pipeline to ensure that the deplo

In this blog, we extended our CI/CD pipelines to deploy Java Spring Boot and ReactJS applications to Azure Kubernetes Service. This approach allows for greater scalability and flexibility.

In our next blog, we will cover advanced topics such as monitoring and scaling these deployments to ensure optimal performance and reliability.
In our [next blog](https://azure.github.io/Cloud-Native/30-days-of-ia-2024/post-production-monitoring-scaling-and-optimization), we will cover advanced topics such as monitoring and scaling these deployments to ensure optimal performance and reliability.
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Dive in to learn more about how our example application works at a technical lev

## Introduction

In the previous blog post, we gave you a high-level overview of our example AI-based content generation app, covering its user experience and how it integrated various services. Now we’d like to dive a little deeper into the technical side, explaining the app's architecture, key components, and code snippets and offering an overview of the app’s data flow.  
In the [previous blog post](https://azure.github.io/Cloud-Native/30-days-of-ia-2024/demo-our-ai-based-content-generation-app), we gave you a high-level overview of our example AI-based content generation app, covering its user experience and how it integrated various services. Now we’d like to dive a little deeper into the technical side, explaining the app's architecture, key components, and code snippets and offering an overview of the app’s data flow.  

Today’s post breaks down how the **front-end**, **middleware**, and **back-end** services work together. We also discuss how the app uses Azure services, like [Azure API Management](https://learn.microsoft.com/azure/api-management/api-management-key-concepts?ocid=biafy25h1_30daysofia_webpage_azuremktg), [Azure Key Vault](https://learn.microsoft.com/azure/key-vault/general/overview?ocid=biafy25h1_30daysofia_webpage_azuremktg), [Azure Cosmos DB](https://learn.microsoft.com/azure/cosmos-db/introduction?ocid=biafy25h1_30daysofia_webpage_azuremktg), [Azure Blob Storage](https://learn.microsoft.com/azure/storage/blobs/storage-blobs-introduction?ocid=biafy25h1_30daysofia_webpage_azuremktg), and [Azure OpenAI Service](https://learn.microsoft.com/azure/ai-services/openai/overview?ocid=biafy25h1_30daysofia_webpage_azuremktg), and how **managed identity** is used to securely connect these components. 

Expand Down Expand Up @@ -140,4 +140,4 @@ The data flow diagram shows how the user query flows from the **front-end** app

In today’s blog post, we discussed the inner workings of our example AI-based content generation app, detailing the interactions between the **front-end**, **middleware**, and **back-end** app tiers. We learned how our app uses various Azure services, like Azure API Management, Azure Key Vault, Azure Cosmos DB, Azure Blob Storage, and Azure OpenAI Service to build a secure and scalable solution.  

In the next post—the last in this series—we'll explore the **outcomes** of building this application, highlighting its scalability and performance, the overall impact of the architecture and technologies used, and the key learnings to take away from the project. 
In the [next post](https://azure.github.io/Cloud-Native/30-days-of-ia-2024/closing-summary)—the last in this series—we'll explore the **outcomes** of building this application, highlighting its scalability and performance, the overall impact of the architecture and technologies used, and the key learnings to take away from the project. 

0 comments on commit 479e191

Please sign in to comment.