“The main reason we wanted to move was because we expected the number of users would scale in the future, and as a result, so would the number of audio samples that users would upload and that we’d have to transcode. “We made the decision in early 2017 that any audio-related stuff-transcoding, mixing, you name it-would be done on AWS,” says den Engelsman. The rationale for migrating was to enable scaling for growth and to establish a complete solution in which all functions could be done in one place. At BandLab, he found that engineers were already experimenting using AWS and understood the benefits of migrating to AWS. “But as our user base grew, the previous solution was struggling with the amount of new audio being uploaded.”ĭen Engelsman was familiar with Amazon Web Services (AWS) and had been involved in AWS migrations for several years before he joined BandLab. “Before, the app was running on another cloud storage provider,” says Nick den Engelsman, senior cloud systems engineer and architect for BandLab. Faced with this sustained growth, BandLab needed to find a place for the nearly 4 PB of data it had accrued and for its future storage needs. A digital audio workshop hailed as a “recording studio in your pocket,” the full-featured BandLab app sees upward of 40,000 new users every day. BandLab promotes music creation in the cloud, enabling individuals to compose, mix, revise, sync, and collaborate through smartphones, tablets, and computers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |