The Acquia Digital Experience Platform is an "Open DXP" with its two core pillars being content and data. Built on top of one of the largest open-source content management systems, Drupal, it aims to provide the flexibility and interoperability a modern organization needs. With its customer data platform, it allows organizations to understand who their customers are and deliver personalized experiences. Acquia's DXP offers variety of other tools including digital asset management,…
N/A
Drupal
Score 8.2 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
Acquia Cloud is more of a hands-off approach to Drupal hosting - get the code on the server and that's basically it. AWS on the other hand requires more specialized server and networking knowledge to support a site. Our company wants to focus on content deliver and not on being …
Acquia coupled with their easier interface and 24 x 7 customer service can outweigh its competitors anytime. Acquia provides a full end to end solution for Drupal websites.
The flexibility aspect of Acquia Site Studio is unmatched and WordPress does not provide it on a large scale. The ability to perform bulk operations and security are also the factors in favour of Acquia Digital Experience Platform as compared to WordPress. They also offer …
If you're project requires a multisite architecture with scalable site deployment, and your budget allows, I would recommend Acquia. Acquia pricing sits more on an Enterprise level, so it is overwhelming if you're hosting a smaller site. Pantheon is much more suited for …
I have used Pantheon for almost as long as I have used Acquia. Many colleges and universities will use sub-sites in Drupal either as a separator for each department, or possibly for targeted marketing campaigns. One of the biggest reason we tend to use Acquia over Pantheon for …
Acquia offers a more robust product suite than Pantheon. Acquia also offers professional services for another level beyond what Pantheon offers. Acquia pricing is typically more expensive than Pantheon, but the extra cost tends to be worth it, given all the support you receive …
Cost - Acquia provides more granular control of the costs. Interface - Acquia interface is a bit cleaner, although Patheon may have a few more features.
Acquia provides much more for the investment. The support and services they provide make them the best choice in choosing a platform to host your Drupal sites. Services like Pantheon may have some new tools or cool features. But Acquia always seems to come out with those …
Acquia has a much easier path for procurement through the GSA contract. Pantheon didn't have an avenue to purchase through the GSA, which severely limited our ability to procure their product. Pantheon has a few extra features which Acquia has yet to develop like true …
I still feel WordPress is easier for a simple 4 page website. Anything more complicated than that, and Drupal is your answer. Drupal 8 may change this dynamic though.
Acquia Cloud is provides some excellent dev to prod staging that I haven't seen anywhere else.
Drupal is head-and-shoulders above WordPress in terms of extensibility and community support, in great part because it is completely open-source. I would recommend it in almost every case over WordPress. (WP is only better if you already know that system well, and your end …
It made it super easy to upgrade 300+ Drupal sites to the latest major version in 12 weeks, end to end. It is easy to deploy legal changes and updates to components at scale. Turnkey service to deploy new environments and to clone sites. There are no ecosystem lock-in principles for Customer service/success services and professional services for new approaches.
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
Exceptionally good support. When there's a problem, you reach out to your account manager who either fixes the issue or gets you to the right person. We've had no downtime.
Platform is very accessible to those who know how to manage the back end software.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
Support responds pretty quickly to critical tickets, but they can be slow to respond on non-urgent items. Some of what we experienced may have been related to a newer ticketing system recently implemented.
Standard support covers business days/hours but only critical support is available outside those times. We typically schedule our website updates for the weekend or "off" hours when only critical support is available.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
We're moving away from Drupal as a platform. Drupal 8 and 9 were simply too overburdened and difficult to maintain compared to other offerings. PHP seems like a dying language so we are currently in the process of migrating all of our Drupal 7 functionality and custom modules to a Python/Django/Wagtail platform. This doesn't mean Acquia isn't a great service, they are professional and top-knotch, but the only way we'd say with them is if I didn't complete the migration.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
Every time we have had an issue, Acquia support has responded promptly and worked with us as a team to solve the problem. The Acquia support team is global and we have literally had interactions with all of their support offices, yet the experience has been the same - top notch
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
We chose Acquia for a much better UI that gave non-analytical marketers and easy to use tool where they could create their own reports. The campaign side of things also had an easier to use UI as well, that made the targeting of audiences much easier.
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
The DXP tools can handle millions of requests and can scale automatically to fit your needs. We have clients that use only part of the DXP tools and have a small usage, but even in these cases they see great value in using tools like personalization and CDP.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Acquia has helped us to stabilize and optimize our website performance, lowering page load times and dramatically decreasing the frequency of issues experienced by end-users.
Acquia SOLR search provided a much-improved search experience on our website.
Acquia's PCI-compliant hosting has helped us to remain compliant and cyber-secure.
We are working to implement Acquia Site Studio and Acquia Personalization now and expect those to improve our operation agility and ability to drive more relevant experiences to our various website visitors.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.