Cloudinary Blog

Keep.com, releasing the image processing bottleneck

Keep.com, releasing the image processing bottleneck

Cloudinary is passionate about its users. We built our cloud-based image management features around real-world pain points, and it's gratifying to see our customers use those features to solve major business challenges.

One example is Keep.com, an innovative online commerce startup, which the Huffington Post has called "the only fashion app worth getting". We wanted to share the story of how Keep used Cloudinary to remove a major bottleneck in the development of their website and business.

The customer

Keep provides users a place to go when they want to discover and buy the latest trends in fashion, decor, accessories and design.

Keep's community aggregates products from across the Internet into a showcase of emerging trends. Unlike Commerce 2.0, where an online retailer simply sells products online, or Commerce 3.0, where online shopping is enhanced by social sharing, Keep gives shoppers a way to discover and buy trends as they happen — on Instagram, TV and from other popular trendsetters. They call this Commerce 4.0, where goods from across the Web are collected and curated by people with a passion for products. Keep's philosophy is that these passionate consumers will be better merchandisers than traditional retailers, whose merchandising decisions are dictated by business restrictions.

Keep site

The challenge

Keep's application displays hundreds of thousands of product and brand images, user profile pictures, and user uploaded images. Keep found it was spending a large and increasing portion of developer time on managing image transformations, every time they went through a design iteration of their website and mobile app.

Each time a redesign took place, Keep needed new image sizes, and would require reprocessing of all the images. This was not only time consuming from a server perspective, but also caused delays in the development process, due to long waiting times as all the images were being transformed.

Engineering resources were wasted trying to set up new image transformations and getting jobs running efficiently, and even so image processing remained a bottleneck.

“When planning how quickly we could change or iterate on a design, the time it took to retroactively process all existing images still needed to be considered. This meant we had to wait to download, process and then re-upload hundreds of thousands of images, before pushing a new design to the site or mobile app,” said Steve Heinz, Senior Developer at Keep.  “This was significantly slowing down our ability to get new releases up and running. We felt the key to success as a startup was being able to push out a new version very quickly, and image processing was getting in the way. We also had to keep track of which images had been processed, which were complex and which created multiple points of failure.”

The solution

We asked Keep to give us the results on how Cloudinary solved the problems they were facing.

”Initially, we were handling our own processing in-house and sought a solution that would reduce the percentage of resources we spend on image transformations, said Steve. “We found Cloudinary, which was cost-effective and allowed for fast image processing and automatic caching. In addition, we wanted to integrate with Rackspace's cloud space, and Cloudinary provided a 'fetch' interface that allowed us to grab images directly off Rackspace, making integration very easy.”

Keep site details

The results

“Keep has been using Cloudinary for over a year now. When we just started, the integration was immediate,” Steve said. “Cloudinary allows Keep to quickly process images on-demand, allowing us to quickly push a new version of our design to production."

“Keep has saved significant developer time, including nearly 50% of one full-time developer, just on managing image transformations and writing code to retroactively go back and process images to newly-needed sizes. This number dropped further, to nearly zero, because now any employee can manage Cloudinary via its Web interface."

“By implementing Cloudinary, Keep significantly reduced the time required to release new image sizes – we went from a process that required overnight image processing, to one that takes only 10 minutes. It also freed up developer resources to work on other projects, further increasing Keep's velocity of innovation.”

Final Words

We were pleased by the dramatic change Keep's development went through – from heavy overnight image processing requiring complex code, to an off-loaded cloud-managed process that enables agile development with almost no delays.

We're happy to have Keep using Cloudinary, and wanted to thank Steve for taking the time and sharing his experience.

Cloudinary users - let us know if you'd like to share your own unique experiences with the Cloudinary community. Stay tuned for more creative ways our customers are using Cloudinary.

Recent Blog Posts

Hipcamp Optimizes Images and Improves Page Load Times With Cloudinary

When creating a website that allows campers to discover great destinations, Hipcamp put a strong emphasis on featuring high-quality images that showcased the list of beautiful locations, regardless of whether users accessed the site on a desktop, tablet, or phone. Since 2015, Hipcamp has relied on Cloudinary’s image management solution to automate cropping and image optimization, enabling instant public delivery of photos, automatic tagging based on content recognition, and faster loading of webpages. In addition, Hipcamp was able to maintain the high standards it holds for the look and feel of its website.

Read more
New Image File Format: FUIF: Why Do We Need a New Image Format

In my last post, I introduced FUIF, a new, free, and universal image format I’ve created. In this post and other follow-up pieces, I will explain the why, what, and how of FUIF.

Even though JPEG is still the most widely-used image file format on the web, it has limitations, especially the subset of the format that has been implemented in browsers and that has, therefore, become the de facto standard. Because JPEG has a relatively verbose header, it cannot be used (at least not as is) for low-quality image placeholders (LQIP), for which you need a budget of a few hundred bytes. JPEG cannot encode alpha channels (transparency); it is restricted to 8 bits per channel; and its entropy coding is no longer state of the art. Also, JPEG is not fully “responsive by design.” There is no easy way to find a file’s truncation offsets and it is limited to a 1:8 downscale (the DC coefficients). If you want to use the same file for an 8K UHD display (7,680 pixels wide) and for a smart watch (320 pixels wide), 1:8 is not enough. And finally, JPEG does not work well with nonphotographic images and cannot do fully lossless compression.

Read more
 New Image File Format: FUIF:Lossy, Lossless, and Free

I've been working to create a new image format, which I'm calling FUIF, or Free Universal Image Format. That’s a rather pretentious name, I know. But I couldn’t call it the Free Lossy Image Format (FLIF) because that acronym is not available any more (see below) and FUIF can do lossless, too, so it wouldn’t be accurate either.

Read more