How could we support the ever-increasing stream of content headed our way? Great forward-thinking in 2015 by our engineers resulted in the internal creation of the first generation of a storage proxy that would be able to support a multitude of backend storage solutions (both on-premises and in AWS) without requiring our internal users and services to change their access patterns. We certainly had a conundrum on our hands. Drivers of this growth, such as the availability of an increasingly more capable selection of media gear (including cameras, drones, and even phones), created an exciting wave of new content the world had never seen. Our analytics leading up to 2014 forecasted exponential growth ahead. ![]() In early 2015, our storage was based on an open-source object store and a collection of high disk capacity servers. Data Center to cloud via Strangler Fig Pattern Join us as we examine how we shifted our primary focus from hardware to software and how Amazon Simple Storage Service (Amazon S3) assisted with this transformation. In this blog, written from the perspective of the Shutterstock Cloud Storage Services Team, we explore the AWS cloud journey our team embarked on in 2015 and the discoveries along the way. Maintaining our own storage infrastructure for over a decade has given us valuable insight into the logistics of on-premises hardware maintenance, expansion, and refreshes. One of the challenges of a fast-growing library of content like ours is ensuring that ample storage is available well ahead of demand. To add to this scale, our catalog increases by approximately 200,000 images each day. Headquartered in New York City, we serve a global customer base spread across 150 countries and cater our platform to 21 unique languages. Working with a community of over 2 million contributors, our catalog has grown to more than 405 million images and over 25 million videos. ![]() Shutterstock, founded in 2003, is a leading global creative platform for transformative brands and media companies.
0 Comments
Leave a Reply. |