Magnolia vs. Microsoft Azure

Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.

Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.

• Speed of development - time to delivery from zero to MVP was excellent
• Ease of use - the authoring experience is very easy to build and train
• PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.

• Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
• You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
• The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
• The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.

Incentivized

• The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
• The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
• Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
• Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.

Incentivized

• The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
• The documentation needs to be improved, and some advanced configuration options require research and experimentation.
• Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.

We have invested a lot of time and energy into tailoring a solution that works for the company.

We think the new features in v6.2 will help us get to the next level

We also don't have the resources to rebuild a website platform from scratch even if we wanted to

Incentivized

Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.

We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.

Incentivized

As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.

Incentivized

It has proven to be unreliable in our production environment and services become unavailable without proper notification to system administrators

Incentivized

I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.

You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases

We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!

Incentivized

As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.

I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.

Incentivized

As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.

Incentivized

• Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
• The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
• The templates makes the whole process easy

Incentivized

• For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
• DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
• Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.

Incentivized