Feb 14 · 4 min read · Chapter 1 of AEM Learning Series — Understanding the core architecture used in every production AEM setup. 🌍 The Big Picture Every production AEM setup runs on a 3-tier architecture. These 3 layers work together to deliver fast, secure, and scalab...
Join discussionFeb 14 · 4 min read · Chapter 2 of AEM Learning Series — Understanding the engine that runs AEM. 🚀 What is OSGi? OSGi = The engine that runs AEM AEM is not a single huge Java application.It is made of hundreds of small modules called Bundles. OSGi is the framework that...
Join discussionFeb 14 · 4 min read · Chapter 1 of AEM Learning Series — Understanding the core architecture used in every production AEM setup. These 3 layers work together to deliver fast, secure, and scalable websites. ✍️ 1. AUTHOR Instance AspectDetail UsersAuthors, marketer...
Join discussionFeb 12 · 9 min read · Introducción En los últimos años, el ecosistema de Adobe Experience Manager (AEM) ha evolucionado hacia modelos de entrega cada vez más gestionados: desde instancias On-premise tradicionales, pasando por Adobe Managed Service (AMS), hasta llegar a Ad...
Join discussionFeb 12 · 6 min read · Introducción Adobe Experience Manager (AEM) no es solo un gestor de contenidos tradicional: es una plataforma altamente extensible que integra gestión, entrega, personalización y optimización de contenido en proyectos empresariales complejos. En esce...
Join discussionJan 15 · 3 min read · OSGi is extremely powerful. But with that power comes complexity, operational overhead, and architectural responsibility. Understanding what OSGi enables is only half the story. The other half is knowing when not to use it. What OSGi Services Are Re...
Join discussionJan 10 · 2 min read · This post serves as a central index for my complete OSGi Deep Dive series. OSGi is often described as complex or hard to understand, mainly because its concepts are deeply interconnected — containers, bundles, classloading, services, IoC, DI, and dec...
Join discussionJan 10 · 6 min read · The Final Post in Our OSGi Series! In our previous post, we explored the IoC, and Dependency Injection (DI) - the foundation that makes OSGi modular, dynamic, and flexible. Understanding these concepts is essential before diving into Components and S...
Join discussionJan 10 · 5 min read · In the previous post, we explored bundle lifecycle, bundle activators, and the Service Registry. Now that we understand how services are registered and made available, it’s time to explore how bundles actually consume these services in a flexible and...
Join discussionJan 10 · 3 min read · In OSGi, a bundle does not interact with the framework directly. Instead, all communication between a bundle and the OSGi container happens through a single, powerful object: BundleContext. You can think of BundleContext as a bundle’s window into the...
Join discussion