From 74af9e15ca79de962d824636bc1d2f34deda5fbb Mon Sep 17 00:00:00 2001 From: Bruno Germano Date: Thu, 5 Nov 2026 18:55:28 -0300 Subject: [PATCH] docs(use-cases): link each Reference Architecture page from its use case (MM-16244) The 19 Reference Architecture pages are hidden rows in the Use Cases sidebar, so the use-case page is their only entry point inside the docs. Link each one from the use case the GTM catalog pairs it with, in en and pt-br: one sentence in the Reference architecture section of the 15 use cases that build the same design, and one in Build AI agents, which shares the third-party LLM page with the customer support use case. --- .../add-ai-features-to-existing-applications.mdx | 2 ++ .../use-cases/build-and-run-ai-workloads/build-ai-agents.mdx | 2 ++ .../build-and-run-customer-support-ai-assistants.mdx | 2 ++ .../build-and-run-marketing-websites.mdx | 2 ++ .../build-and-run-applications/build-rest-and-graphql-apis.mdx | 2 ++ .../deploy-full-stack-applications-globally.mdx | 2 ++ .../modernize-a-monolithic-application-without-a-rewrite.mdx | 2 ++ .../stream-live-events-to-large-audiences.mdx | 2 ++ .../accelerate-websites-and-apis-with-a-cdn.mdx | 2 ++ .../optimize-images-for-websites-and-mobile-apps.mdx | 2 ++ .../block-account-takeover-on-login-and-checkout-flows.mdx | 2 ++ .../block-attackers-automatically-from-siem-detections.mdx | 2 ++ .../prepare-regulated-web-applications-for-security-audits.mdx | 2 ++ .../protect-public-apis-from-abuse.mdx | 2 ++ ...-web-applications-from-owasp-top-10-and-zero-day-attacks.mdx | 2 ++ .../screen-file-uploads-for-malicious-content.mdx | 2 ++ .../criar-apis-rest-e-graphql.mdx | 2 ++ .../criar-e-operar-sites-de-marketing.mdx | 2 ++ .../implantar-aplicacoes-full-stack-globalmente.mdx | 2 ++ .../modernizar-uma-aplicacao-monolitica-sem-reescreve-la.mdx | 2 ++ .../adicionar-funcionalidades-de-ia-a-aplicacoes-existentes.mdx | 2 ++ .../criar-agentes-de-ia.mdx | 2 ++ ...iar-e-executar-assistentes-de-ia-para-suporte-ao-cliente.mdx | 2 ++ .../transmitir-eventos-ao-vivo-para-grandes-audiencias.mdx | 2 ++ .../acelerar-sites-e-apis-com-uma-cdn.mdx | 2 ++ .../otimizar-imagens-para-sites-e-aplicacoes-moveis.mdx | 2 ++ .../bloquear-account-takeover-em-fluxos-de-login-e-checkout.mdx | 2 ++ ...-atacantes-automaticamente-a-partir-de-deteccoes-do-siem.mdx | 2 ++ ...ionar-uploads-de-arquivos-em-busca-de-conteudo-malicioso.mdx | 2 ++ ...ar-aplicacoes-web-reguladas-para-auditorias-de-seguranca.mdx | 2 ++ .../proteger-apis-publicas-contra-abuso.mdx | 2 ++ ...aplicacoes-web-contra-ataques-do-owasp-top-10-e-zero-day.mdx | 2 ++ 32 files changed, 64 insertions(+) diff --git a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/add-ai-features-to-existing-applications.mdx b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/add-ai-features-to-existing-applications.mdx index f0597d261c..7a16029c0f 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/add-ai-features-to-existing-applications.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/add-ai-features-to-existing-applications.mdx @@ -37,6 +37,8 @@ This use case does not cover conversational assistants grounded in company conte This page builds the *Catalog-model inference API*: the model is used as AI Inference publishes it, behind a function your application calls. +For this design on its own, with its diagram, dataflow, and components, refer to [*Catalog-model inference API*](/en/documentation/use-cases/build-and-run-ai-workloads/ai-inference-architecture/). + Solid arrows carry the request, and dotted arrows carry the response. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-ai-agents.mdx b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-ai-agents.mdx index 0069a39a72..22c689d21e 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-ai-agents.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-ai-agents.mdx @@ -40,6 +40,8 @@ The model comes from the third-party provider. A team that runs the model on AI This page builds the *Tool-calling agent over third-party LLMs*: every step of the loop calls the provider's API, and the tools run in the function. +For a LangGraph agent on Azion that answers from documents through a third-party model, with the chat state in SQL Database, refer to [*Retrieval-augmented assistant over third-party LLMs*](/en/documentation/use-cases/build-and-run-ai-workloads/ai-agent-third-party-llm/). + Solid arrows carry the requests, and dotted arrows carry the responses. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-and-run-customer-support-ai-assistants.mdx b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-and-run-customer-support-ai-assistants.mdx index c8d66d2bd4..6cb6f28570 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-and-run-customer-support-ai-assistants.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-ai-workloads/build-and-run-customer-support-ai-assistants.mdx @@ -39,6 +39,8 @@ This use case does not cover AI features that are not conversational. For those, This page builds the *Retrieval-augmented assistant on platform-hosted models*: the documents, the vectors, the retrieval, and both models stay on Azion. +For this design on its own, with its diagram, dataflow, and components, refer to [*Retrieval-augmented assistant on platform-hosted models*](/en/documentation/use-cases/build-and-run-ai-workloads/ai-agent-copilot-assistant/). + The diagram carries two flows that meet at the database. Solid arrows carry a customer's question, dotted arrows carry its answer, and thick arrows carry the ingestion flow, which runs apart from any question. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-and-run-marketing-websites.mdx b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-and-run-marketing-websites.mdx index 80edf5f756..9ab2b97be7 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-and-run-marketing-websites.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-and-run-marketing-websites.mdx @@ -36,6 +36,8 @@ This use case does not cover e-commerce storefronts, which [Build e-commerce sto This page builds the *Git-driven static website*: every push to the repository builds the site, and an application serves the prebuilt files from Object Storage through Cache. +For this design on its own, with its diagram, dataflow, and components, refer to [*Git-driven static website*](/en/documentation/use-cases/build-and-run-applications/deploy-jamstack-applications/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the publish flow and the purge, which run apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-rest-and-graphql-apis.mdx b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-rest-and-graphql-apis.mdx index 2548dbb483..24782e573b 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-rest-and-graphql-apis.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/build-rest-and-graphql-apis.mdx @@ -36,6 +36,8 @@ This use case does not cover APIs that react to events instead of callers, which This page builds the *Single-service API on SQL Database*: one function implements every endpoint and reads and writes one database in SQL Database. +For this design on its own, with its diagram, dataflow, and components, refer to [*Single-service API on SQL Database*](/en/documentation/use-cases/build-and-run-applications/serverless-applications/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the replication and the metrics, which run apart from any request. Each label starts with the number of the dataflow step it belongs to. The application does nothing but run the API function on every request, so the diagram draws the two as one node. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/deploy-full-stack-applications-globally.mdx b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/deploy-full-stack-applications-globally.mdx index 53028896b8..6a2b345d8e 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/deploy-full-stack-applications-globally.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/deploy-full-stack-applications-globally.mdx @@ -37,6 +37,8 @@ This use case does not cover APIs without a user interface, which [Build REST an This page builds the *Server-rendered full-stack application on SQL Database*: a server-rendering framework whose build splits into static assets in Object Storage and server code in a function that reads Azion's stores. +For this design on its own, with its diagram, dataflow, and components, refer to [*Server-rendered full-stack application on SQL Database*](/en/documentation/use-cases/build-and-run-applications/edge-native-applications/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the publish flow, which runs apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/modernize-a-monolithic-application-without-a-rewrite.mdx b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/modernize-a-monolithic-application-without-a-rewrite.mdx index 49264c97fd..1d5cfd5df1 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/modernize-a-monolithic-application-without-a-rewrite.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/build-and-run-applications/modernize-a-monolithic-application-without-a-rewrite.mdx @@ -37,6 +37,8 @@ This use case does not cover moving the whole application to a new origin in one This page builds the *Strangler façade for legacy applications*: an application on Azion becomes the single entry point for the domain, and each migrated path goes to a function while every other path goes to the monolith. +For this design on its own, with its diagram, dataflow, and components, refer to [*Strangler façade for legacy applications*](/en/documentation/use-cases/build-and-run-applications/application-modernization/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the request records and the team's rule changes, which run apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/deliver-media-and-streaming/stream-live-events-to-large-audiences.mdx b/apps/docs/src/content/docs/en/pages/use-cases/deliver-media-and-streaming/stream-live-events-to-large-audiences.mdx index 6d189b48c5..bf968f5268 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/deliver-media-and-streaming/stream-live-events-to-large-audiences.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/deliver-media-and-streaming/stream-live-events-to-large-audiences.mdx @@ -38,6 +38,8 @@ This use case does not cover on-demand libraries, ad insertion, or DRM. For on-d This page builds the *Live stream ingested on Azion*: the encoder pushes the stream to Live Ingest, and an application delivers it, with no streaming origin of your own. +For this design on its own, with its diagram, dataflow, and components, refer to [*Live stream ingested on Azion*](/en/documentation/use-cases/deliver-media-and-streaming/live-streaming-delivery-with-hls/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the stream from the encoder and the audience reports, which run apart from any viewer's request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/accelerate-websites-and-apis-with-a-cdn.mdx b/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/accelerate-websites-and-apis-with-a-cdn.mdx index 2cdc864ed6..b27c65ae6a 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/accelerate-websites-and-apis-with-a-cdn.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/accelerate-websites-and-apis-with-a-cdn.mdx @@ -42,6 +42,8 @@ Pointing the domain at Azion is the same for every site, so it has no section on This page builds the *Caching reverse proxy in front of an origin*: an application that answers from cache whatever it can and reaches the origin only on a miss. +For this design on its own, with its diagram, dataflow, and components, refer to [*Caching reverse proxy in front of an origin*](/en/documentation/use-cases/improve-performance-and-reliability/content-delivery/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the purge, which runs apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/optimize-images-for-websites-and-mobile-apps.mdx b/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/optimize-images-for-websites-and-mobile-apps.mdx index fd0f341ddb..7c32547d3f 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/optimize-images-for-websites-and-mobile-apps.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/improve-performance-and-reliability/optimize-images-for-websites-and-mobile-apps.mdx @@ -38,6 +38,8 @@ This use case does not cover video or image editing workflows. This page builds the *Origin-backed image optimization proxy*: image routes on an application that transform the originals fetched from your origin and cache each variant. +For this design on its own, with its diagram, dataflow, and components, refer to [*Origin-backed image optimization proxy*](/en/documentation/use-cases/improve-performance-and-reliability/image-processing/). + Solid arrows carry the request, dotted arrows carry the response, and the thick arrow carries the metrics, which flow apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-account-takeover-on-login-and-checkout-flows.mdx b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-account-takeover-on-login-and-checkout-flows.mdx index b097e2ef19..dd6979ff91 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-account-takeover-on-login-and-checkout-flows.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-account-takeover-on-login-and-checkout-flows.mdx @@ -41,6 +41,8 @@ This use case does not cover general API abuse, which [Protect public APIs from This page builds the *Bot-scoring perimeter for authentication flows*: firewall rules that scope Bot Manager to the login, signup, and checkout paths, where the score decides whether a request passes, is challenged, or is denied. +For this design on its own, with its diagram, dataflow, and components, refer to [*Bot-scoring perimeter for authentication flows*](/en/documentation/use-cases/secure-applications-and-networks/online-fraud-prevention/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the report lines, which leave apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-attackers-automatically-from-siem-detections.mdx b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-attackers-automatically-from-siem-detections.mdx index a71c363909..2aa3d1381e 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-attackers-automatically-from-siem-detections.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/block-attackers-automatically-from-siem-detections.mdx @@ -38,6 +38,8 @@ This use case does not cover the detection logic itself, which stays in the team This page builds the *SIEM-driven firewall mitigation loop*: events leave the firewall for the SIEM, and a detection comes back as an entry in a network list that a firewall rule already enforces. +For this design on its own, with its diagram, dataflow, and components, refer to [*SIEM-driven firewall mitigation loop*](/en/documentation/use-cases/secure-applications-and-networks/security-automation-with-edge-computing/). + Solid arrows carry the attacker's requests and the deny rule's check of each one against the list. Dotted arrows carry the responses, and thick arrows carry the loop, which runs apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/prepare-regulated-web-applications-for-security-audits.mdx b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/prepare-regulated-web-applications-for-security-audits.mdx index 20bdf194e1..74aa956054 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/prepare-regulated-web-applications-for-security-audits.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/prepare-regulated-web-applications-for-security-audits.mdx @@ -42,6 +42,8 @@ DDoS Protection mitigates DoS and DDoS attacks on every workload, with nothing t This page builds the *Compliance perimeter with security event retention*: encryption, filtering, and access restrictions in front of the application, and an export of every security event to a destination the team keeps. +For this design on its own, with its diagram, dataflow, and components, refer to [*Compliance perimeter with security event retention*](/en/documentation/use-cases/secure-applications-and-networks/governance-risk-compliance/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the evidence, which leaves apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-public-apis-from-abuse.mdx b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-public-apis-from-abuse.mdx index 2416f0c340..10fe69f93f 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-public-apis-from-abuse.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-public-apis-from-abuse.mdx @@ -44,6 +44,8 @@ This use case does not cover API design or lifecycle management, or account take This page builds the *API security perimeter*: a firewall on the API's workload that filters each request by rules, tokens, bot scores, and rates before the connector forwards it to the API origin. +For this design on its own, with its diagram, dataflow, and components, refer to [*API security perimeter*](/en/documentation/use-cases/secure-applications-and-networks/implement-api-gateways-security/). + Solid arrows carry the request, and dotted arrows carry the response. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-web-applications-from-owasp-top-10-and-zero-day-attacks.mdx b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-web-applications-from-owasp-top-10-and-zero-day-attacks.mdx index 6c7971ecdf..e3c47bbd45 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-web-applications-from-owasp-top-10-and-zero-day-attacks.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/protect-web-applications-from-owasp-top-10-and-zero-day-attacks.mdx @@ -44,6 +44,8 @@ DDoS Protection mitigates DoS and DDoS attacks on every workload, before any fir This page builds the *Web application and API protection (WAAP) perimeter*: one firewall policy in front of the workload, with the origin closed to every other path. +For this design on its own, with its diagram, dataflow, and components, refer to [*Web application and API protection (WAAP) perimeter*](/en/documentation/use-cases/secure-applications-and-networks/web-application-and-api-protection-waap/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the WAF events, which leave apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/screen-file-uploads-for-malicious-content.mdx b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/screen-file-uploads-for-malicious-content.mdx index 134d31dcf3..5e35e28898 100644 --- a/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/screen-file-uploads-for-malicious-content.mdx +++ b/apps/docs/src/content/docs/en/pages/use-cases/secure-applications-and-networks/screen-file-uploads-for-malicious-content.mdx @@ -38,6 +38,8 @@ This use case does not cover antivirus scanning of stored files, or general WAF This page builds the *AI-assisted upload inspection pipeline*: the firewall sends each upload to a function that asks a model whether it is malicious, and applies the verdict in the same request. +For this design on its own, with its diagram, dataflow, and components, refer to [*AI-assisted upload inspection pipeline*](/en/documentation/use-cases/build-and-run-ai-workloads/autonomous-security-ai-agent/). + Solid arrows carry the request, dotted arrows carry the response, and thick arrows carry the verdict lines and the blocklist update, which run apart from any request. Each label starts with the number of the dataflow step it belongs to. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-apis-rest-e-graphql.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-apis-rest-e-graphql.mdx index 7eddac8abf..f12a342b0c 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-apis-rest-e-graphql.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-apis-rest-e-graphql.mdx @@ -36,6 +36,8 @@ Este caso de uso não cobre APIs que reagem a eventos em vez de chamadores, que Esta página constrói a *API de serviço único sobre o SQL Database*: uma function implementa todos os endpoints e lê e grava um banco de dados no SQL Database. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*API de serviço único sobre o SQL Database*](/pt-br/documentacao/casos-de-uso/construir-e-executar-aplicacoes/serverless-applications/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam a replicação e as métricas, que rodam separadas de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. A aplicação não faz nada além de executar a function da API em toda requisição, então o diagrama desenha as duas como um único nó. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-e-operar-sites-de-marketing.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-e-operar-sites-de-marketing.mdx index d2b2660369..364417ca9e 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-e-operar-sites-de-marketing.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/criar-e-operar-sites-de-marketing.mdx @@ -36,6 +36,8 @@ Este caso de uso não cobre vitrines de e-commerce, que [Criar vitrines de e-com Esta página constrói o *Site estático orientado por Git*: cada push no repositório constrói o site, e uma aplicação serve os arquivos pré-construídos do Object Storage pelo Cache. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Site estático orientado por Git*](/pt-br/documentacao/casos-de-uso/construir-e-executar-aplicacoes/implantacao-aplicacoes-jamstack/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam o fluxo de publicação e o purge, que rodam separados de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/implantar-aplicacoes-full-stack-globalmente.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/implantar-aplicacoes-full-stack-globalmente.mdx index 6c1b38c6bd..24fc89b12e 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/implantar-aplicacoes-full-stack-globalmente.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/implantar-aplicacoes-full-stack-globalmente.mdx @@ -37,6 +37,8 @@ Este caso de uso não cobre APIs sem interface de usuário, que [Criar APIs REST Esta página constrói a *Aplicação full-stack renderizada no servidor sobre o SQL Database*: um framework de renderização no servidor cujo build se divide em assets estáticos no Object Storage e código de servidor em uma function que lê os armazenamentos da Azion. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Aplicação full-stack renderizada no servidor sobre o SQL Database*](/pt-br/documentacao/casos-de-uso/construir-e-executar-aplicacoes/aplicacoes-edge-native/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam o fluxo de publicação, que roda separado de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/modernizar-uma-aplicacao-monolitica-sem-reescreve-la.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/modernizar-uma-aplicacao-monolitica-sem-reescreve-la.mdx index 848d5c456f..c087ed6eb3 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/modernizar-uma-aplicacao-monolitica-sem-reescreve-la.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-aplicacoes/modernizar-uma-aplicacao-monolitica-sem-reescreve-la.mdx @@ -37,6 +37,8 @@ Este caso de uso não cobre mover a aplicação inteira para uma nova origem em Esta página monta a *Fachada strangler para aplicações legadas*: uma aplicação na Azion se torna o ponto de entrada único do domínio, e cada caminho migrado vai para uma função, enquanto todos os outros caminhos vão para o monolito. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Fachada strangler para aplicações legadas*](/pt-br/documentacao/casos-de-uso/construir-e-executar-aplicacoes/modernizacao-de-aplicacoes/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam os registros das requisições e as mudanças de regra da equipe, que rodam separados de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/adicionar-funcionalidades-de-ia-a-aplicacoes-existentes.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/adicionar-funcionalidades-de-ia-a-aplicacoes-existentes.mdx index bc4304a239..f1f5287e75 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/adicionar-funcionalidades-de-ia-a-aplicacoes-existentes.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/adicionar-funcionalidades-de-ia-a-aplicacoes-existentes.mdx @@ -37,6 +37,8 @@ Este caso de uso não cobre assistentes conversacionais fundamentados em conteú Esta página constrói o *Catalog-model inference API*: o modelo é usado como o AI Inference o publica, atrás de uma function que a sua aplicação chama. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Catalog-model inference API*](/pt-br/documentacao/casos-de-uso/construir-e-executar-workloads-de-ai/ai-inference-architecture/). + As setas contínuas levam a requisição, e as setas pontilhadas levam a resposta. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-agentes-de-ia.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-agentes-de-ia.mdx index 28e43444b8..3fb6fc276d 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-agentes-de-ia.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-agentes-de-ia.mdx @@ -40,6 +40,8 @@ O modelo vem do provedor de terceiros. Uma equipe que executa o modelo no AI Inf Esta página constrói o *Tool-calling agent over third-party LLMs*: cada etapa do loop chama a API do provedor, e as ferramentas são executadas na function. +Para um agente LangGraph na Azion que responde a partir de documentos por meio de um modelo de terceiros, com o estado da conversa no SQL Database, consulte [*Retrieval-augmented assistant over third-party LLMs*](/pt-br/documentacao/casos-de-uso/construir-e-executar-workloads-de-ai/ai-agent-third-party-llm/). + As setas contínuas levam as requisições, e as setas pontilhadas levam as respostas. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-e-executar-assistentes-de-ia-para-suporte-ao-cliente.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-e-executar-assistentes-de-ia-para-suporte-ao-cliente.mdx index 1c88494f96..29b2cfba2e 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-e-executar-assistentes-de-ia-para-suporte-ao-cliente.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/construir-e-executar-workloads-de-ai/criar-e-executar-assistentes-de-ia-para-suporte-ao-cliente.mdx @@ -39,6 +39,8 @@ Este caso de uso não cobre funcionalidades de IA que não são conversacionais. Esta página constrói o *Retrieval-augmented assistant on platform-hosted models*: os documentos, os vetores, a recuperação e os dois modelos ficam na Azion. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Retrieval-augmented assistant on platform-hosted models*](/pt-br/documentacao/casos-de-uso/construir-e-executar-workloads-de-ai/agente-ai-assistente-copilot/). + O diagrama tem dois fluxos que se encontram no banco de dados. As setas contínuas levam a pergunta de um cliente, as setas pontilhadas levam a resposta dela, e as setas grossas levam o fluxo de ingestão, que roda separado de qualquer pergunta. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/entregar-midia-e-streaming/transmitir-eventos-ao-vivo-para-grandes-audiencias.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/entregar-midia-e-streaming/transmitir-eventos-ao-vivo-para-grandes-audiencias.mdx index be9238363c..78dc22249d 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/entregar-midia-e-streaming/transmitir-eventos-ao-vivo-para-grandes-audiencias.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/entregar-midia-e-streaming/transmitir-eventos-ao-vivo-para-grandes-audiencias.mdx @@ -38,6 +38,8 @@ Este caso de uso não cobre bibliotecas sob demanda, inserção de anúncios nem Esta página monta a *Transmissão ao vivo ingerida na Azion*: o encoder envia a transmissão ao Live Ingest, e uma aplicação a entrega, sem nenhuma origem de streaming sua. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Transmissão ao vivo ingerida na Azion*](/pt-br/documentacao/casos-de-uso/entregar-midia-e-streaming/live-streaming-delivery-com-hls/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam a transmissão do encoder e os relatórios de audiência, que rodam separados da requisição de qualquer espectador. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/acelerar-sites-e-apis-com-uma-cdn.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/acelerar-sites-e-apis-com-uma-cdn.mdx index 89bb2e7330..313b3f1965 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/acelerar-sites-e-apis-com-uma-cdn.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/acelerar-sites-e-apis-com-uma-cdn.mdx @@ -42,6 +42,8 @@ Apontar o domínio para a Azion é igual para todos os sites, então não tem se Esta página constrói o *Proxy reverso com cache na frente de uma origem*: uma aplicação que responde do cache tudo o que pode e só chega à origem em um miss. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Proxy reverso com cache na frente de uma origem*](/pt-br/documentacao/casos-de-uso/melhorar-performance-e-confiabilidade/content-delivery/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam o purge, que roda separado de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/otimizar-imagens-para-sites-e-aplicacoes-moveis.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/otimizar-imagens-para-sites-e-aplicacoes-moveis.mdx index c9e2cb72de..0cd7f47fc5 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/otimizar-imagens-para-sites-e-aplicacoes-moveis.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/melhorar-performance-e-confiabilidade/otimizar-imagens-para-sites-e-aplicacoes-moveis.mdx @@ -38,6 +38,8 @@ Este caso de uso não cobre vídeo nem fluxos de edição de imagem. Esta página constrói o *Proxy de otimização de imagens apoiado na origem*: rotas de imagem em uma aplicação que transformam os originais buscados da sua origem e cacheiam cada variação. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Proxy de otimização de imagens apoiado na origem*](/pt-br/documentacao/casos-de-uso/melhorar-performance-e-confiabilidade/processamento-de-imagens/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e a seta grossa leva as métricas, que fluem separadas de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-account-takeover-em-fluxos-de-login-e-checkout.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-account-takeover-em-fluxos-de-login-e-checkout.mdx index b1646c3af0..cd181241d1 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-account-takeover-em-fluxos-de-login-e-checkout.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-account-takeover-em-fluxos-de-login-e-checkout.mdx @@ -41,6 +41,8 @@ Este caso de uso não cobre o abuso geral de APIs, que [Proteger APIs públicas Esta página constrói o *perímetro de pontuação de bots para fluxos de autenticação*: regras de firewall que restringem o Bot Manager aos caminhos de login, cadastro e checkout, onde o score decide se uma requisição passa, é desafiada ou é negada. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Perímetro de pontuação de bots para fluxos de autenticação*](/pt-br/documentacao/casos-de-uso/proteger-aplicacoes-e-redes/prevencao-fraudes-online/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam as linhas de report, que saem separadas de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-atacantes-automaticamente-a-partir-de-deteccoes-do-siem.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-atacantes-automaticamente-a-partir-de-deteccoes-do-siem.mdx index b20b44b765..314f7175a4 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-atacantes-automaticamente-a-partir-de-deteccoes-do-siem.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/bloquear-atacantes-automaticamente-a-partir-de-deteccoes-do-siem.mdx @@ -38,6 +38,8 @@ Este caso de uso não cobre a lógica de detecção em si, que fica no SIEM da e Esta página constrói o *loop de mitigação no firewall orientado pelo SIEM*: os eventos saem do firewall para o SIEM, e uma detecção volta como um item em uma network list que uma regra de firewall já aplica. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Loop de mitigação no firewall orientado pelo SIEM*](/pt-br/documentacao/casos-de-uso/proteger-aplicacoes-e-redes/automacao-da-seguranca-com-edge-computing/). + As setas contínuas levam as requisições do atacante e a verificação de cada uma na lista pela regra de negação. As setas pontilhadas levam as respostas, e as setas grossas levam o loop, que roda separado de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/inspecionar-uploads-de-arquivos-em-busca-de-conteudo-malicioso.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/inspecionar-uploads-de-arquivos-em-busca-de-conteudo-malicioso.mdx index fdce329e5a..cf6bce5fdd 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/inspecionar-uploads-de-arquivos-em-busca-de-conteudo-malicioso.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/inspecionar-uploads-de-arquivos-em-busca-de-conteudo-malicioso.mdx @@ -39,6 +39,8 @@ Este caso de uso não cobre a varredura antivírus de arquivos armazenados nem a Esta página constrói o *pipeline de inspeção de uploads assistida por AI*: o firewall envia cada upload a uma função que pergunta a um modelo se ele é malicioso e aplica o veredito na mesma requisição. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Pipeline de inspeção de uploads assistida por AI*](/pt-br/documentacao/casos-de-uso/construir-e-executar-workloads-de-ai/ai-agent-seguranca-autonoma/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam as linhas de veredito e a atualização da blocklist, que rodam separadas de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/preparar-aplicacoes-web-reguladas-para-auditorias-de-seguranca.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/preparar-aplicacoes-web-reguladas-para-auditorias-de-seguranca.mdx index efd5c36484..a09d84a8a4 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/preparar-aplicacoes-web-reguladas-para-auditorias-de-seguranca.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/preparar-aplicacoes-web-reguladas-para-auditorias-de-seguranca.mdx @@ -42,6 +42,8 @@ DDoS Protection mitiga ataques DoS e DDoS em todo workload, sem nada para config Esta página constrói o *perímetro de compliance com retenção de eventos de segurança*: criptografia, filtragem e restrições de acesso na frente da aplicação, e uma exportação de cada evento de segurança a um destino que a equipe mantém. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Perímetro de compliance com retenção de eventos de segurança*](/pt-br/documentacao/casos-de-uso/proteger-aplicacoes-e-redes/governanca-risco-conformidade/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam a evidência, que sai separada de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-apis-publicas-contra-abuso.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-apis-publicas-contra-abuso.mdx index e39e4c101a..1f15f77ab8 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-apis-publicas-contra-abuso.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-apis-publicas-contra-abuso.mdx @@ -44,6 +44,8 @@ Este caso de uso não cobre o design nem a gestão do ciclo de vida de APIs, nem Esta página constrói o *perímetro de segurança de APIs*: um firewall no workload da API que filtra cada requisição por regras, tokens, scores de bot e taxas antes que o connector a encaminhe à origem da API. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Perímetro de segurança de APIs*](/pt-br/documentacao/casos-de-uso/proteger-aplicacoes-e-redes/implementar-seguranca-api-gateways/). + As setas contínuas levam a requisição, e as setas pontilhadas levam a resposta. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid diff --git a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-aplicacoes-web-contra-ataques-do-owasp-top-10-e-zero-day.mdx b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-aplicacoes-web-contra-ataques-do-owasp-top-10-e-zero-day.mdx index 6c0ccdc35f..f6482917c3 100644 --- a/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-aplicacoes-web-contra-ataques-do-owasp-top-10-e-zero-day.mdx +++ b/apps/docs/src/content/docs/pt-br/pages/casos-de-uso/proteger-aplicacoes-e-redes/proteger-aplicacoes-web-contra-ataques-do-owasp-top-10-e-zero-day.mdx @@ -44,6 +44,8 @@ DDoS Protection mitiga ataques DoS e DDoS em todo workload, antes de qualquer re Esta página constrói o *perímetro de proteção de aplicações web e APIs (WAAP)*: uma política de firewall na frente do workload, com a origem fechada a qualquer outro caminho. +Para ver este design isoladamente, com o diagrama, o fluxo de dados e os componentes, consulte [*Perímetro de proteção de aplicações web e APIs (WAAP)*](/pt-br/documentacao/casos-de-uso/proteger-aplicacoes-e-redes/web-application-and-api-protection-waap/). + As setas contínuas levam a requisição, as setas pontilhadas levam a resposta, e as setas grossas levam os eventos do WAF, que saem separados de qualquer requisição. Cada rótulo começa pelo número da etapa do fluxo de dados a que pertence. ```mermaid