Posts

TitleDateExcerpt
AEM and Apache Arrow for High-Performance Data ExchangeAdobe Experience Manager is often the content and experience layer in a broader digital platform. It manages pages, assets, fragments, forms, and delivery…
AEM and PostgreSQL for external data source integrationAdobe Experience Manager is designed to manage content, assets, configurations, and publishing workflows through its repository. PostgreSQL serves a different…
Monitoring AEM Publisher Health with PrometheusAn Adobe Experience Manager publisher can appear available while still failing the work that matters. HTTP requests may return successfully even as replication…
AEM and Spring Boot for Microservice Backend IntegrationAdobe Experience Manager (AEM) is often the presentation and content management layer in an enterprise platform, while Spring Boot is well suited to business…
AEM Custom Login Modules With Two-Factor AuthenticationAdobe Experience Manager applications often begin with a simple username-and-password flow and gradually acquire more demanding security requirements. As…
Using AEM transient workflows for non-persistent operationsAdobe Experience Manager workflows are often associated with durable business processes: content approval, asset processing, translation, and publishing. Those…
AEM and MariaDB for Custom Persistence Beyond the JCRAdobe Experience Manager is built around a content repository, and that repository remains the right home for pages, assets, components, tags, permissions, and…
Building a Modern AEM Front-End Workflow with Webpack and BabelAdobe Experience Manager projects often begin with a clear component model and a well-organized content structure. Yet the front end can become difficult to…
AEM and Apache Camel for system integration workflowsAdobe Experience Manager (AEM) is often the presentation and content hub in a larger digital estate. Product information may live in a commerce platform,…
AEM and Terraform for Infrastructure as Code DeploymentsAdobe Experience Manager projects depend on more than Java code, component dialogs, and content structures. They also rely on cloud resources, network rules,…