Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
DigitalOcean App Platform
Score 8.0 out of 10
N/A
The DigitalOcean App Platform enables developers to build, deploy, and scale apps on what they describe as a simple, fully managed PaaS.
Users of the former Nanobox, acquired by DigitalOcean in 2019, have been migrated to the App Platform upon Nanobox's end of life in March 2021.
$5
per month
Netlify Platform
Score 10.0 out of 10
N/A
Netlify is a platform for developers from the company of the same name in San Francisco, used to build performant and dynamic web sites, e-commerce stores and applications. By uniting an ecosystem of technologies, services and APIs into one workflow.
I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
I would only get into it if I where willing to pay for the support plan and getting some assurances from the team as to where they are headed. The platform itself is great and can save you a ton of hard work and money. but it's hard to be confidant in it's sustainability.
Netlify is a static website host, so it obviously wouldn't work for hosting dynamic websites built in PHP, such as WordPress or Drupal. It works very well with static sites with a git codebase on something like GitHub. It has automatic deployments, which include preview websites. It works very well with this workflow. There are solutions for allowing content authoring on static websites on Netlify, but I would probably reach for something like WordPress or Drupal for that.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
I can connect Github/Gitlab repos or drag and drop code folders directly to host them onto the platform, and can customize build and publish details. It handles all granular details itself, so I don't have to worry about configuring everything like I would have to do on an IaaS like AWS
Netlify Platform has inbuilt scalability support - meaning automatic upgrading of servers to handle traffic, without us needing to do anything at all, again, unlike IaaS, where we'd have to manually configure scaling
It has a built in CDN, meaning static applications can be served blazing fast over the web without worrying about traffic or latency
There are some glitches in permissions inheritance that require us to toggle a save on permissions in groups that inherit from a group that was recently updated.
Large packages require stopping the workflow launcher OSGi components or many workflows will slow down the server.
Locked pages are hard to find unless I use /siteadmin... I often hear that the CQ tools will go away, but if we lose that, some small things might be harder to do, like finding locked pages.
The company has not been very communicative as of lately. Not much news, no apparent work on missing features.
Some components are incomplete as far as some critical features. For example, I use RethinkDB as my database and it's missing critical features like backup and clustering, so It is unusable and they should have made that clear from the get go.
The pricing on the support plan is vague. I do have the feeling it is actually well worth the money, but it's hard to form a decisions based without more predictable specific.
Seems to me like the platform's future is unclear.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
Adobe Experience Manager overall is fairly easy to use and caters to a wide range of users when it comes to their technical abilities. It has the flexibility to enable UI/UX designers to pop in and easily design new content with drop in components. It also has sufficient capabilities for those who are more technically inclined and want to dig more into custom code or solutions
We interact with the CLI via our CI/CD pipeline. It was very straightforward to get set up, and their documentation is thorough. There are a ton of examples online of various setups. We needed to deploy a React SPA, so we required redirects, which was straightforward with Netlify.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
It can help you to host your virtual appliance or serverless application at very low cost. DigitalOcean marketplace also helps you to deploy the serverless app or virtual appliance effortlessly. It is suitable for small scale deployment and the process to setup an account and roll out your app via marketplace is easy and cheap.
Netlify Platform is the first choice that we are using in this organization continuously and it's been a very promising platform to use. It also maintains the things very well. it also giving a very good updates. It is very easy to use and very easy to learn. overall it is good.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
too soon to tell on increased conversion rates based on external marketing factors in play but having increased visibility into customer engagement trends will most likely lead to improvement of our conversion rates.
There have been productivity gains from the perspective of actually migrating all of our externally managed sites to the same in-house Adobe Experience Manager platform and then being able to utilize those universal components.
