The most important change in the 3D Gallery was the transition to a pure cloud-based environment based on the state-of-the-art Amazon Web Services (AWS). With the anticipated growing demand for high-quality 3D content, we wanted to have a robust and efficient system for users to reliably store their personal photos and to easily access them with low latency. It was also important to offer a good user experience for the 3D Gallery Connect Smart 3D TV applications.

Scalability & Quality-of-Service

To support all this new demand, the 3D Gallery utilizes the  Elastic Compute Cloud (EC2) for handling all image access and processing operations, as well as the user interface of the 3D Gallery.  One key item of this new environment is the Elastic Load Balancing capability, which automatically distributes incoming traffic between multiple servers running the 3D Gallery to decrease latency and to allow our services to easily scale-up with demand. Elastic Cloud computing provides us the ability to easily add computing/storage resources to meet activity spikes while maintaining quality of service and availability for our products and services.

In addition, we moved the User Forum, the 3D Gallery, and the Content Management databases to a Relational Database Service to simplify administrative tasks typically associated with databases. This capability allows us to execute difficult procedures, such as replication and scaling, fast and reliably thus minimizing downtime.

Worldwide Access

This new environment will also help with the global presence of our products and services by deploying servers in multiple zones and multiple regions. This cloud-based computing environment creates a primary Instance of the 3D Gallery operations on a server and synchronously replicates the 3D images to standby servers in different Time Zones. This enables us to ensure worldwide quality of service and efficient access to your images whether you are accessing them from your PC or the 3D Gallery Connect Smart 3D HDTV application. Each Availability Zone runs on its own independent infrastructure, and is engineered to be highly reliable.

Image Safety

Multi-AZ deployments utilize synchronous physical replication, keeping data on the standby up-to-date with the primary. This safeguards your images in the event of a server failure or loss of an Availability Zone. For example, if a storage volume on your primary server fails, the 3D Gallery automatically changes to the most up-to-date standby server.

Increased Availability

The new environment provides increased availability for the 3D Gallery. If a server failure occurs in one of the Zones, the availability impact of your images is limited to very little time (typically three to six minutes). The availability benefits also extend in cases of planned maintenance and backups. Although you may experience elevated latencies for a few minutes during backups or system upgrades, those latencies are very small.

Secure Transactions

All transactions between the 3D Gallery and yourself whether you are using Internet, or the Trimago smartphone application, or the 3D Gallery Connect Smart TV app are handled using Secure Socket Layer (SSL) over the secure HTTPS protocol to ensure proper protection of user data.

Image Storage, Backups, Reliability

One of our immediate goals is to use Amazon Simple Storage Service (S3) to house the storage of photos in the 3D Gallery as well as backups and other files. S3 is a cloud-based storage system that can be used to store and retrieve any amount of data, at any time, from anywhere on the web. It provides us with a highly-scalable, reliable, secure, and fast infrastructure to store and protect your images.

When fully configured, S3 will allow you to store your data at the closest server to your geographic location to minimize latency and increase availability.

S3 provides a highly durable storage infrastructure to prevent loss of your image data. The service redundantly stores data in multiple facilities and on multiple devices within each facility. Finally, S3 is designed to sustain the concurrent loss of data in two facilities.

Memory usage: real: 25690112, emalloc: 25367024
Code ProfilerTimeCntEmallocRealMem