Magnolia vs. VMware vCenter

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.

The VMware vCenter server is very useful in maintaining the CPU/RAM/datastore resources are balanced when there are multiple ESX/ESXi host servers. It is clear what resources are being used, and it is easy to migrate VMs to different ESX/ESXi hosts. Being able to remotely connect to the VM servers in vCenter when you cannot have other remote connections helps in maintenance and troubleshooting.

Incentivized

• 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.

• VSAN storage management and redundancy - high performance IO with built in fault tolerance across the cluster, not reliant on a single hardware item
• VM fault tolerance. The ability to relocate a running VM and restart VMs from failed or isolated nodes
• Resource management and alerting. Tracking load across physical systems and allowing us to rebalance for better utilisation

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

• Currently, the HTML 5-based vSphere Client lets you manage the essential functions of vSphere from any browser, however, it would be nice if they would port all management functions over to the HTML 5-based Client.
• Performing updates and upgrades to the infrastructure is a bit challenging for someone that may not be as intimate with vSphere. I think the updates/upgrades should be more integrated into the UI and provide the ability to push to the hosts, etc...
• It would also be nice to have a more robust snapshot management tool to prevent snapshot overgrowth. It would be nice to be able to set a lifespan for the snapshot(s)

Incentivized

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

We are very dependent on this software, it has become a much needed tool to perform the daily tasks that are required to maintain the virtual server environment. VMware has become very pricey over the years, so we are looking for alternatives for cost savings strategy, but nothing has been found to be on par to what we are currently using

Incentivized

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

I work with vCenter for 10+ years and i love it. I can find my way around and can help building and expanding the platform. It is easy to use and there are a lot good communities for the extra support when needed. Even the Homelab community is of great value.

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

VMware support has always been fantastic and they have been invaluable in solving tougher issues that have been run into. Most of the time, any oddities encountered are fixed by available updates. This can be deduced by support quickly with logs within vCenter. We have not run into something yet that support was unable to help with. They either have a solution already, or they are able to find one quickly.

Incentivized

Since moving away from the Windows Server hosting the vCenter application and instead using a virtual appliance, it has become much easier to implement and deploy the new versions. We can easily create a snapshot or clone of the vCenter vApp to ensure any problems encountered during the upgrade can be mitigated with a fall back to the old version to prevent unscheduled downtime.

Incentivized

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

Citrix Xen Server.... Great Hypervisor but very limited in terms of functionality

MS Hyper-V... [VMware vCenter Server] is better for almost everything and appliance form makes a clear winner for security and ease of deployment

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

• The positive impact of vcenter is definitely felt in larger organisations in terms of being able to manage multiple servers all in one environment
• It will decrease the amount of time your server engineers will have to spend in the server room or datacenter.

Incentivized