AEM Explained in Simple Terms | 30 Concepts Every Adobe Experience Manager Professional Must Know

Workflow State Machines

A workflow state machine is the part of a system that keeps track of where a multi-step process is, what already happened, what should happen next, and what to do if something fails. In this episode, Satish uses a simple real-life example first, then turns the idea into a practical technical mental model for engineers and curious builders. In Simple Terms with Satish: daily tech trends explained simply, with enough technical depth for builders. Production note: This episode uses authorized synthetic narration based on Satish's own voice. The topic, script, and final editorial approval are by Satish. Engineer notes: Exact technical references: - OpenAI documents background mode for long-running asynchronous tasks. - The OpenAI Agents SDK exposes resumable run state after interruptions through `to_state()`. - Temporal says workflows can continue after crashes by replaying event history and can keep running for years. - Temporal retries activities declaratively instead of requiring custom retry code everywhere. - Azure Durable Task uses event sourcing and append-only orchestration history to rebuild state on replay. - AWS Step Functions exposes retry controls like interval, backoff, max delay, and jitter inside workflow definitions. Sources: - https://developers.openai.com/api/docs/guides/background - https://openai.github.io/openai-agents-python/results/ - https://docs.temporal.io/workflows - https://docs.temporal.io/encyclopedia/retry-policies - https://learn.microsoft.com/en-us/azure/durable-task/common/durable-task-orchestrations - https://docs.aws.amazon.com/step-functions/latest/dg/concepts-error-handling.html

Semantic Reranking

Semantic reranking is the step where an AI system takes a shortlist of search results and reorders them based on which result best matches the meaning of your question. In this episode, Satish uses a simple real-life example first, then turns the idea into a practical technical mental model for engineers and curious builders. In Simple Terms with Satish: daily tech trends explained simply, with enough technical depth for builders. Production note: This episode uses authorized synthetic narration based on Satish's own voice. The topic, script, and final editorial approval are by Satish. Engineer notes: Exact technical references: - Azure AI Search semantic ranker reranks an initial BM25-ranked or RRF-ranked result set and is built into agentic retrieval. - Azure semantic ranking applies to a bounded result window rather than searching the full corpus again. - Pinecone exposes reranking as part of a two-stage retrieval process and also as a standalone operation. - Cohere documents reranking for semi-structured and tabular data in addition to plain text. - OpenSearch documents rerank as a search response processor using a cross-encoder model. Sources: - https://learn.microsoft.com/en-us/azure/search/semantic-search-overview - https://docs.pinecone.io/guides/search/rerank-results - https://docs.cohere.com/docs/reranking-with-cohere - https://docs.opensearch.org/latest/search-plugins/search-pipelines/search-processors/

Hybrid RAG Pipelines

That is the pattern where an AI system looks up outside information before it answers. In this episode, Satish uses a simple real-life example first, then turns the idea into a practical technical mental model for engineers and curious builders. In Simple Terms with Satish: daily tech trends explained simply, with enough technical depth for builders. Production note: This episode uses authorized synthetic narration based on Satish's own voice. The topic, script, and final editorial approval are by Satish. Engineer notes: Exact technical references: - OpenAI file search uses both semantic and keyword search. - Azure AI Search hybrid search runs full-text and vector queries in parallel and merges them with Reciprocal Rank Fusion. - Azure query guidance recommends starting with balanced hybrid patterns instead of maxing out every retrieval parameter. - Pinecone documents reranking as a second-stage quality improvement after merged retrieval. - Cohere documents reranking as a semantic boost for keyword or vector retrieval systems. Sources: - https://platform.openai.com/docs/guides/tools-file-search/ - https://learn.microsoft.com/en-us/azure/search/hybrid-search-overview - https://learn.microsoft.com/en-us/azure/search/hybrid-search-how-to-query - https://docs.pinecone.io/guides/search/hybrid-search - https://docs.pinecone.io/guides/search/rerank-results - https://docs.cohere.com/docs/reranking-quickstart

How AI Tools Tell Agents Where Login Lives

Before an AI client can log in to a protected tool, it has to know where the right login system is. In this episode, Satish uses a simple real-life example first, then turns the idea into a practical technical mental model for engineers and curious builders. In Simple Terms with Satish: daily tech trends explained simply, with enough technical depth for builders. Production note: This episode uses authorized synthetic narration based on Satish's own voice. The topic, script, and final editorial approval are by Satish. Engineer notes: Exact technical references: - Latest MCP authorization specification: `2025-11-25`. - RFC 9728 defines OAuth 2.0 protected resource metadata. - MCP servers use protected resource metadata for authorization server discovery. - Discovery can happen through a `WWW-Authenticate` challenge or a standard well-known metadata endpoint. - Client credentials for unattended services still depend on the same discovery layer before token acquisition. Sources: - https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization - https://modelcontextprotocol.io/extensions/auth/oauth-client-credentials - https://www.rfc-editor.org/rfc/rfc9728 - https://datatracker.ietf.org/doc/html/rfc7523 - https://arxiv.org/abs/2605.22333

How Background AI Agents Get Permission

This matters because not every AI agent is a person sitting in front of a chat window. In this episode, Satish uses a simple real-life example first, then turns the idea into a practical technical mental model for engineers and curious builders. In Simple Terms with Satish: daily tech trends explained simply, with enough technical depth for builders. Production note: This episode uses authorized synthetic narration based on Satish's own voice. The topic, script, and final editorial approval are by Satish. Engineer notes: Exact technical references: - Official MCP extension: `io.modelcontextprotocol/oauth-client-credentials`. - The extension is intended for background services, CI/CD jobs, server-to-server integrations, and daemon processes. - Supported auth patterns include standard client credentials with `client_id` and `client_secret`, and JWT bearer assertions from RFC 7523. - Remote MCP servers still act as protected resources and should validate issuer, audience or resource binding, expiry, and scope. - Related implementation surfaces include protected resource metadata, auth provider support in MCP SDKs, and extension capability negotiation during initialize. Sources: - https://modelcontextprotocol.io/extensions/auth/oauth-client-credentials - https://modelcontextprotocol.io/specification/draft/basic/authorization - https://modelcontextprotocol.io/extensions/auth/overview - https://py.sdk.modelcontextprotocol.io/authorization/ - https://www.rfc-editor.org/rfc/rfc7523