Why Cloud Architecture Matters: The Multi-Instance Advantage over Multi-Tenant


Posted May 4, 2016 by Spee123

CloudFlare is a cloud services company founded in San Francisco in 2009. Their various services protect, speed up, and improve availability for websites and applications.

 
Not all clouds are created equal – and the key difference for The Enterprise Cloud is a superior architecture. Nearly all clouds today are built on a legacy construct called a multi-tenant architecture. The cloud is built on an advanced architecture called multi-instance.
When the first cloud services went live in the late 1990s, the architecture was built on database systems originally designed for making airline reservations, tracking customer service requests and running financial systems. These database systems were built on centralized compute, storage and networking that served all customers. These cloud services scaled their hardware to accommodate customer growth while companies like Oracle, IBM, EMC and Cisco thrived in this ecosystem.
In these multi-tenant clouds, many of which are still using this same architecture today, customers share the same software and infrastructure. While the cloud provider gains the advantage of building and maintaining a centralized system, there are three major drawbacks of the multi-tenant model for their customers:
1) Your data is commingled. You rely on the cloud provider to logically isolate your data from everyone else’s data. The data of your direct competitor could be commingled with yours in the single database. Commingling doesn’t mean you can see another company’s data; access to the multi-tenant environment is controlled. But all the same, your data is not physically separate and relies on software for separation and isolation. This has major implications for government, healthcare and financial regulations. Further, a security breach to the cloud provider could expose your data along with everyone else commingled on the same multi-tenant environment.
2) Multi-tenant architectures rely on large and complex databases that require hardware and software maintenance on a regular basis, resulting in availability issues for customers. Departmental applications in use by a single group, such as the sales or marketing teams, can tolerate weekly downtime after normal business hours or on the weekend.
3) Any action that affects the multi-tenant database affects all shared customers. When software or hardware issues are found on a multi-tenant database, it causes an outage for all customers, and an upgrade of the multi-tenant database upgrades all customers. Your availability and upgrades are tied to all other customers that share your multi-tenancy. The big problem arises when this model is applied to run enterprise–wide business services. Entire organizations do not tolerate this shared approach on applications that are critical to their success. They need software and hardware issues to be isolated and resolved quickly and to upgrade on their own schedule for planning and compliance reasons.
With its inherent data isolation and multiple availability issues, multi-tenancy is a legacy cloud computing architecture that will not stand the test of time.
Enter the Multi-Instance Cloud

Each customer instance is a unique software stack and this means that, unlike some competing platforms, there is no 70-page document of restrictions and limitations. Your instances in our cloud are for your enterprise and your business needs. With this architecture and deployment model comes a wealth of benefits; true data isolation, advanced high availability and customer-driven upgrade schedules. Let’s look at these areas more closely.
• True data isolation: This makes hardware and software maintenance on these unique customer instances far easier to perform and issues can be resolved on a customer-by-customer basis. Unlike a multi-tenant architecture, customers are not grouped together in a shared database.
• Customer-driven upgrades: As we described above, the multi-instance architecture allows us to perform actions on individual customer instances, such as performing an upgrade. Each individual instance can be upgraded on a schedule that fits the compliance requirements and needs of the enterprise.
In short, the multi-instance architecture puts our customers in control of their cloud. This is how the enterprise runs their mission-critical applications – with data isolated, a fully replicated environment that provides extremely high availability and upgrades on their schedule. This is why we’ve invested heavily in advancing our cloud architecture and know that the multi-instance architecture gives our customers many advantages over antiquated multi-tenant clouds.
get more details: Digital ocean review
-- END ---
Share Facebook Twitter
Print Friendly and PDF DisclaimerReport Abuse
Contact Email [email protected]
Issued By annie
Country Virgin Islands (U.S.)
Categories Internet , Services , Web Development
Last Updated May 4, 2016