Over the course of the last five years I’ve experienced various AEM implementations.
They differ in every aspect, as the needs of our clients are very different too - from the business domain to IT considerations such as security or scalability. It is also not uncommon for other unexpected things to impact the solution - things like legacy systems that that need to be integrated. That said, things are not as chaotic as it would seem at a glance - a clear trend is emerging.
That trend is the growing digital maturity of marketers and their end users. As it stands today, the end users are the driving force for change - their expectations only rising, never declining!
There are many facets of the emerging trend, but most of them have a similar effect on the resulting platform - they add integration points, add bespoke features - often both at the same time - thereby adding more complexity to an already inherently complex system.
Adobe AEM is a platform that not only provides many integrations points out of the box, but also is relatively easy to integrate completely new systems as well. In the end we get a nice, homogenous environment that scales horizontally. Scaling is just a matter of adding another mirror of the same environment and load balancing traffic to it, a few key checks, and we’re done.
However, over time we noticed that this is not enough. Scaling by providing mirrors of the same AEM machine is okay if the services provided by it are similar. But as diversity in different parts of the system grows we have noticed that clients rarely want traffic on their community portal to affect the business critical parts of the system (assuming the community portal IS NOT the business critical part). This lead us to embracing the increasingly popular idea of microservices that you can read about on Maciej’s blog post.
When talking about scalability and performance you can never forget about the most important aspect - dispatcher caching. This is a very broad topic with some really interesting better practices. Let me refer you to Jakub’s blog post for a comprehensive write up on that.
Looking at the growing content consumption expectations of end users, you should also keep in mind all the internal system users responsible for creating the content. When building a modern experience management platform you should care about authors as well, because a poor author experience invariably leads to a poor customer experience.
An advanced, well designed and slick interface will not only make authors happy but also reduce the time-to-market for content changes that is one of many critical business KPIs. One of the aspects of building a modern authoring interface you can read about in the upcoming blog from Mateusz Chromiński.
These, and many more experience management feature at this year’s AEMHub cover design and delivery aspects ranging from platform architecture to tweaking the sling rewriter, from cloud deployments to building social Intranets. Join us at AEMHub to learn from the practitioners and share your expertise in the break out sessions.
If you can’t make it, continue the conversation on our Adobe Community portal
We're always looking for new faces to join the Cognifide family. Take a look at our available jobs.