Cloudinary vs. Perforce P4

Cloudinary handles pretty much anything you have related to images. From serving them up efficiently to adding transformations on the fly, there's really little this service doesn't do. Their pricing plans allow you to grow into the right levels and their website dashboards are very helpful. I would easily recommend this for all but the simplest of use cases.

Incentivized

For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.

Incentivized

• Cloudinary is the best in the market for photo and video transformations.
• Cloudinary takes customer's requests for special features and implements them very quickly.

Incentivized

• Merge algorithm is smart and utilizing the visual interface to do merges makes them easier to digest.
• Easy to set up on multiple platforms and architectures and is well supported on all of them.
• Visual interface has many tools and customization options that help to optimize and personalize workflow.

Incentivized

• Currently, they don't have an officially supported Drupal module -so it's quite painful to implement.
• If you have a site that has a lot of visitors then it's possible to get quite large bills out of the blue if you get a massive spike e.g. black Friday.
• The UI for the backend and documentation could do with a lot of improvements.

Incentivized

• I was having a hard time learning it. Even if you are an experienced developer, there is some learning curve.
• Can be slow when working with large data sets at once.
• When working on multiple workspaces on the same machine, Perforce can make it difficult not to mess up the code.

We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.

Incentivized

Cloudinary is very easy to use and offers fast way to upload your images, files and videos to their servers. Then they give you quick ways t implement those files or images onto your website using their API or just a normal URL. They also give you very fast ways to make edits to those files and include them in the url.

Incentivized

With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!

Incentivized

In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.

Incentivized

We rarely use their support. But when we need it they are always there. They provide great consultation and suggestions to help us manage our costs and resources better. In the last 8 years perhaps we have contacted them 3 or 4 times - which is really really great

Incentivized

I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.

Incentivized

This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.

Incentivized

My experience with AEM has been limited to interacting with it through others, and so this information should be taken with that in mind, but my impressions from talking with the service engineers managing this system in our enterprise (in a previous role) was that it could be challenging to integrate effectively into a large-scale organization with demands on security. The biggest reason I selected Cloudinary was price-based; their free plan serves my needs as a freelancer quite well.

Incentivized

New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.

Incentivized

• Images are essential to our product and using Cloudinary has allowed us to serve them up in a cost-effective and efficient way. Not having to worry about your images frees you up to tackle the real challenges for your product.

Incentivized

• Locking assets make us have no merge problems which are harder to manage on other versions control without locking
• Almost no need to give support to artists or non-tech folks because the operations are very straightforward
• There's no way to do interim checkins without going to the process of creating a stream

Incentivized