InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Designing a Cloud-oriented Enterprise Datacenter

Posted by Boris Lublinsky on Aug 25, 2010

Sections
Architecture & Design,
Enterprise Architecture,
Operations & Infrastructure
Topics
SOA ,
Cloud Computing ,
Operations ,
Virtualization

 

According to Gartner one of the top strategic technologies for the 2010 is cloud computing. Based on this a commonly asked question is how to approach the implementation of demand-driven cloud-oriented data centers. In his new article,. Tony Bishop outlines proven design principles that can enable an enterprise to create a cloud-oriented datacenter.

Dynamic provisioning - an application provisioning approach that provides the capability to deploy an application (including configuration of its runtime resources) in minutes, rather than hours or days.

Dynamic execution management - a facility monitoring server’s workload and adjusting allocation of applications and services (starting and/or stopping them as desired) based on their required SLAs

Virtualized - the ability to dynamically provision not only applications and services but also resources required by these application services. This is typically required to support an unanticipated demand without a significant amount of over provisioning.

Abstracted - the infrastructure component and layer design needs to have sufficient abstraction so that the operational details are hidden from all other collaborating components and layers. This allows different implementation of any component which in turn maximizes the opportunity to create a virtualized infrastructure.

Service-oriented infrastructure - an enterprise infrastructure (middleware, connectivity, hardware, and network) has to be designed as a set of cooperating services (subject to service level agreements that can be enforced through policies in real time). These services can be measured, reported on, and reallocated based on the business demands.

Demand-based infrastructure footprints - it is necessary to be able to assemble infrastructure components to fit required operational demands in terms of operational qualities.

Simplified engineering - the infrastructure component is successful only if it is easy to use and deploy. Bishop thinks that

Applying the principles stated above will simplify engineering and meet the objectives that will make the utility a success. Simplified engineering will promote greater efficiency, enable the datacenter to migrate to a "green" status, enable greater agility in the deployment of new services, all while reducing cost, waste, and deployment time, and providing a better quality service.

Principles, described by Bishop, come very close to the Panduit's Vineeth Ram advice on designing of data centers:

... a truly smart datacenter that meets the business performance requirements with a unified, integrated, efficient, sustainable and automated infrastructure across all core systems,.. Infrastructure management software would provide visibility into both the physical and logical systems and enables optimization... in a production environment. Software automation will enable integrated services management capabilities across all systems and the underlying physical infrastructure. Lastly, it would also ensure that planned growth and changes are accommodated efficiently, with the lowest risk and highest agility.

Although these design principles seem to be common sense, failure to follow them typically leads to failure in creating a useful, fully functional cloud-based datacenter.

  • This article is part of a featured topic series on SOA
Security by Chris Czarnecki Posted
  1. Back to top

    Security

    by Chris Czarnecki

    Really interesting article. I think you have all the major considerations here except for security. In my experience, security is a primary concern for organisations considering any cloud oriented solutions. It would have been great to hear your views on security here.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.