Olympusat is a large, independent media company specializing in ownership, corporate distribution, production, and technical services. The company has established itself as a leader in the Hispanic television and media space with more than 100 English-language and Spanish-language television networks. The company provides an over-the-top content-delivery offering called VEMOX, which enables Olympusat to distribute live channels and extensive on-demand video to smart televisions and other smart devices via the cloud. Olympusat was founded in 1999 and engages more than eight million viewers each day.
- Olympusat was running a traditional PHP application, but wanted to use one language to run its backend.
- The company’s server-based architecture required a server administrator to handle upgrades and launch new instances.
- The company wanted to move to a microservices architecture to support both a layer of primitive functions to perform common tasks, as well as another layer of application services such as video-format translation.
- Olympusat realized it could develop application services more quickly by switching from a PHP application to a NodeJS implementation using Amazon API Gateway and AWS Lambda.
- The company built a microservices architecture by creating a low-level set of primitive microservices running in an asynchronous workflow, which let the company add new delivery vehicles and data sources without adding code. Amazon API Gateway fronts an asynchronous workflow layer that is implemented using AWS Lambda, which validates incoming requests against a schema stored in Amazon Simple Storage Service (Amazon S3).
- Once validated, the message is put in a queue in Amazon Simple Queue Service (Amazon SQS) and is added to Amazon DynamoDB.
- The workflow function uses Amazon Simple Notification Service to communicate with the microservices, signaling to either call more services or return results.
- Olympusat saves about $25,000 monthly by eliminating the use of similar, more expensive services.
- Using one backend language managed by AWS Lambda, the company can put code into production without the need to provision infrastructure or disrupt other departments.
- AWS Lambda eliminated the need for server administration, so more time is spent focusing on innovation and problem-solving rather than managing servers.
To learn more about how AWS Lambda can help reduce time to market and development and operational costs, visit our AWS Lambda details page.
Why Not Mix It Up? Link
Rather than build an app entirely with native or HTML5 technology, why not mix and match the technologies? With a hybrid application, building a mobile experience that leverages both native and HTML5 code for the user interface is quite possible. This enables the developer to use the most appropriate tool for the job when developing the user interface.
Clearly, developing portions of the user experience in two or more different technologies has some downsides. Chiefly, you would need developers who can handle both native development and HTML5. The portion of the user interface in native code couldn’t be readily used on other platforms and would need to be redeveloped. Given the broader scope of knowledge required by this technique and the difficulties outlined above, why would anyone want to embark on an endeavor that mixes user-interface technologies?
|Standard Storage||Standard – Infrequent Access Storage †||Glacier Storage|
|First 50 TB / month||$0.023 per GB||$0.0125 per GB||$0.004 per GB|
|Next 450 TB / month||$0.022 per GB||$0.0125 per GB||$0.004 per GB|
|Over 500 TB / month||$0.021 per GB||$0.0125 per GB||$0.004 per GB|
|For Requests Not Otherwise Specified Below|
|PUT, COPY, POST, or LIST Requests||$0.005 per 1,000 requests|
|GET and all other Requests||$0.004 per 10,000 requests|
|Delete Requests||Free †|
|For Standard – Infrequent Access Requests|
|PUT, COPY, or POST Requests||$0.01 per 1,000 requests|
|GET and all other Requests||$0.01 per 10,000 requests|
|Lifecycle Transition Requests into Standard – Infrequent Access||$0.01 per 1,000 requests|
|Data Retrievals||$0.01 per GB|
|For Glacier Requests|
|Lifecycle Transition Requests into Glacier||$0.05 per 1,000 requests|
|Glacier Retrieval Fees||See Glacier Pricing Page|
|Data Transfer OUT From Amazon S3 To|
|Amazon EC2 in the same region||$0.000 per GB|
|US East (N. Virginia)||$0.010 per GB|
|Another AWS Region||$0.020 per GB|
|Amazon CloudFront||$0.000 per GB|
|Data Transfer OUT From Amazon S3 To Internet|
|First 1 GB / month||$0.000 per GB|
|Up to 10 TB / month||$0.090 per GB|
|Next 40 TB / month||$0.085 per GB|
|Next 100 TB / month||$0.070 per GB|
|Next 350 TB / month||$0.050 per GB|
|Next 524 TB / month||Contact Us|
|Next 4 PB / month||Contact Us|
|Greater than 5 PB / month||Contact Us|
|Data Transfer IN To Amazon S3|
|All data transfer in||$0.000 per GB|
- Bike/ strider