Cloudinary Blog

Why we moved from an in-house image management system to Cloudinary

By Adam Cox
Build VS. Buy
At Build.com, where I’m a software architect, we manage hundreds of millions of images. Our site offers more than 1 million home improvement products, such as tubs, toilets, cabinets, fireplaces – really any thing homeowners need for their improvement projects. And for each item, there are multiple images – product and gallery images, action shots, close-ups and thumbnails – that our visitors view from a variety of devices, including mobile phones, tablets, their desktop computers and our native app. In addition, these images are used in many view templates – on the landing page, via search, by category and in the cart.
 
Since our inception, we were using a homegrown system to manage and manipulate our images. We relied on Apache rules and proxies to a Java resizer app. But we ran into several problems with the system as our site grew, including:
  • Speed – It was slow and we were unable to do image transformations on-the-fly.
  • Limited features – We could only resize the height and width, proportionately, and crop for thumbnails.
  • Data consistency – We would upload new images to the site, but they wouldn’t be visible to customers.
  • Storage – With capacity problems and back-up issues, our IT operations staff was always having to help us deal with the images in our system.
  • Scaling – Uploading thousands of images caused a cascading set of issues, resulting in the system crashing and maxing out CPOs.
  • Image management – All images were managed through FTP, without any user interface (UI).
As our company evolved and expanded, we knew we had to find a better way to manage and deliver the best possible images to our buyers. We were spending too much time and too many resources maintaining the legacy system. That led us to a crossroads: Do we build a new system in-house, or should we look for a solution from a third-party vendor?
 
To aid in the decision-making process, we created a matrix that enabled us to evaluate the pros vs. cons of in-house vs. third-party, and identify the requirements any new system must meet:
  • Performance – Time to transform and the ability to create multiple variants, on-the-fly, from the original.
  • Optimization – Ability to reduce image weight by stripping metadata, set JPEG levels and use progressive JPEGs, leverage WebP for Chrome and other actions that speed page-load time.
  • Rich Feature Set – Multiple transformation options, including cropping capabilities, face detection, applying watermarks and delivering higher resolution images for retina display.
  • Accuracy – Proper cache purges to resolve data consistency issues and deliver new images to customers immediately.
  • Ease of Use – Should be easy to implement, integrate and migrate the large existing media library from the legacy system in order to minimize impact on operations.
As we narrowed down our decision to build or buy, we also debated key points, including cost, both in terms of dollars and man hours. These costs included: 
  • Common costs that would be incurred with either option (managing files, integration/migration to a new system, storage, back-up costs and training for the new system).
  • Opportunity costs (particularly in terms of the roadmap and functionality that may be required in the future).
  • Man hours required (for either building and maintaining the system or integrating and managing a third-party solution). 
Other considerations included:
  • Number of files we would need to manage
  • Total storage
  • Bandwidth usage 
  • Growth expectations
  • Potential scalability and reliability of each model to support a global audience or unexpected traffic spikes.
Ultimately, we realized that buying was our best option. We have a talented group of developers, but felt their time would be better spent working on new features for Build.com, rather than the tasks that an outsourced image management service should easily be able to handle.
 
We looked for a vendor that had experience serving companies that were larger than Build.com, which showed that it was capable of scaling, was considered reliable and offered high availability. If these companies were using a vendor and satisfied with its performance, we knew it would be a good fit for us. In addition, we wanted to ensure that the vendor’s performance was faster than our legacy system. Before making our decision, we ran side-by-side WebPageTest comparisons, which enabled us to test whether the vendor’s system offered significant speed increases and performance improvements. 
 
After considering a number of third-party vendors, we selected Cloudinary because it met – or exceeded – all our requirements. Since our move to Cloudinary in May 2016, we’ve seen a number of benefits:
  • Easy implementation – Available code libraries, upload widgets and ability to fetch images from remote locations made our start-up and transition a snap.
  • Greater productivity – Because we didn’t have to maintain and troubleshoot problems, like in our legacy system, our development team became more productive, saving use an average of 10 to 20 hours a month to re-focus on other important aspects.
  • Instant access to new features – As Cloudinary introduced new features, such as art-directed cropping and optimal format selection based on the browser, we could immediately take advantage of them.
  • Better utilization – There was less CPU usage on our servers, better CDN purging when files changed and improvements in back ups.
  • Improved performance – All web pages loaded on Chrome now use WebP for optimal performance, and we generally lowered the page size and reduced loading time.
The decision to build vs. buy a new image management system was not one we took lightly, since the success of our site – and our business – relies so heavily on images. Every company needs to take careful stock of its current challenges, what it wishes to accomplish, expectations for the future, and the risks and rewards of each option, before taking that next step.
 
Here I’ve shared our decision-making process, and the overall benefits from moving to Cloudinary. In my next blog, I’ll go into more detail about how we’re using Cloudinary and the results we have achieved.
 

Recent Blog Posts

Analyze and auto tag images with Amazon Rekognition

Knowledge is power. And if you allow your users to upload images, you also probably want to better understand what their images contain. Whether a photo is of a building, people, animals, celebrities, or a product, image processing and analysis can assist in further comprehension. The benefits of this knowledge can go beyond "merely" categorizing your content and making your image library searchable: drawing insights from user generated content can be very useful! What better way to learn more about your users than to analyze the images they upload and find out what they care about and then have the ability to display relevant content to them according to their interests or even match them with other users that share similar interests.

Read more
Automatically moderate your user uploaded images

Allowing your users to upload their own images to your website can increase user engagement, retention and monetization. However, allowing your users to upload any image they want to, may lead to some of your users uploading inappropriate images to your application. These images may offend other users or even cause your site to violate standards or regulations.

Read more
Cloudinary Uses Scale API to Focus on Image Compression

Here at Cloudinary, we provide a cloud-based tool that enables our users to compress images and video for their websites and apps. Our goal is to preserve the visual integrity of the content, but deliver the smallest file size to any device or browser to ultimately optimize website performance and end user satisfaction.

Read more
CloudinaryAndroid SDK

Developing applications for mobile consumption requires facing, and overcoming, some difficult challenges. Apps need to limit their RAM, CPU and battery usage while still performing the required tasks in a reasonable time frame. If too many background tasks are running, the mobile device can become sluggish, with the battery running out very quickly. Coordination with other apps is crucial to keep the device responsive and make the battery last longer.

Read more
forLoop: Nigeria Event on Building for The Next Billion Users

TL;DR

Since Google shared their intent for the next billion internet users, some African developers thought this was pointing right at them and they needed to act fast. The mission to bring the next billion users from Africa to the internet kicked off a storm of enthusiasm. This community event turned into a success story and this is a summary of what happened.

Read more