A Load Balancing, Monitoring and AutoScaling Solution for Private Clouds Using AWS APIs
2011-03-06 10:30
573 查看
The Cloud today is a bit like SOA in the early days. In Enterprise IT, everyone talks about it, but few companies venture moving their core systems from their datacenters to public Clouds. Actually a lot of companies are rather deploying Private Clouds in their own datacenters as an extension of successful virtualization deployments even though Amazon Web Services have been around for more than four years now.
Yesterday, MomemtumSI announced "Tough Software Solutions", a set of services which provide an elastic layer to IaaS platforms like VMWare vCloud Director or Eucalyptus. The services include Load Balancing, which distributes incoming application traffic accross multiple machines, Cloud Monitoring which monitor the health of cloud services accross thousands of machines in multiple data centers or cloud providers, and Auto Scaling which give the ability to acquire and release machines based on activity levels.
These three services are accessible via APIs that are strictly compatible with Amazon Web Services APIs: Amazon Elastic Load Balancer, Amazon CloudWatch™ and Amazon Auto Scaling.
InfoQ spoke briefly with Jeff Schneider, CEO of MomentumSI who explained:
He added:
The platform side of Cloud Computing seems to be at cross roads for the enterprise. IaaS or even PaaS have not changed much the way IT deploys and operates solutions. Will the Private Cloud be a stepping stone towards the vision of Enterprise Cloud Computing? Will most large companies still run datacenters in 2020? What's your take on it?
Yesterday, MomemtumSI announced "Tough Software Solutions", a set of services which provide an elastic layer to IaaS platforms like VMWare vCloud Director or Eucalyptus. The services include Load Balancing, which distributes incoming application traffic accross multiple machines, Cloud Monitoring which monitor the health of cloud services accross thousands of machines in multiple data centers or cloud providers, and Auto Scaling which give the ability to acquire and release machines based on activity levels.
These three services are accessible via APIs that are strictly compatible with Amazon Web Services APIs: Amazon Elastic Load Balancer, Amazon CloudWatch™ and Amazon Auto Scaling.
InfoQ spoke briefly with Jeff Schneider, CEO of MomentumSI who explained:
Our enterprise customers have shown significant interest in the private cloud. They’ve seen all the cool stuff you can do in Amazon and they want it for themselves. However, they have a web of interconnected legacy applications and heterogeneous environments including mainframe, AIX, etc. that prevent them from making a wholesale jump to a cloud provider. This means that they have two choices. First, they can move a some of their Greenfield apps to the public cloud. This is great – but represents a minority of their systems. Second, they can make their own data centers work more like the cloud. The enterprise wants to enable their developers and testers to provision servers, load balancers, etc. in seconds. Currently, it often takes months to get these work orders pushed through. Also, they want common platforms for things like databases and message queues. Most enterprises have a rats nest of different platforms waiting for consolidation and PaaS enablement.
He added:
“For the large enterprise, it will take several years, possibly a decade, before they commit to moving to a public cloud provider. Private clouds represent the transition path, which is the reason we’re putting so much emphasis on making our solutions compatible with the leading cloud provider, Amazon Web Services.
The platform side of Cloud Computing seems to be at cross roads for the enterprise. IaaS or even PaaS have not changed much the way IT deploys and operates solutions. Will the Private Cloud be a stepping stone towards the vision of Enterprise Cloud Computing? Will most large companies still run datacenters in 2020? What's your take on it?
相关文章推荐
- How to Configure Tomcat/JBoss and Apache HTTPD for Load Balancing and Failover
- Configuring Floating IP addresses for Networking in OpenStack Public and Private Clouds
- System Operations on AWS - Lab 6W - Using Auto Scaling (Windows)
- Installing haproxy load balancing for http and https--转载
- Auto-Publishing and Monitoring APIs With Spring Boot--转
- Installing haproxy load balancing for http and https--转载
- Along with all the above benefits, you cannot overlook the space efficiency and performance gains in using DataFrames and Dataset APIs for two reasons.
- How to Configure Tomcat/JBoss and Apache HTTPD for Load Balancing and Failover
- 10g & 11g Configuration of TAF(Transparent Application Failover) and Load Balancing [ID 453293.1]
- Real-Time SQL Monitoring using DBMS_SQLTUNE (REPORT_SQL_MONITOR, REPORT_SQL_MONITOR_LIST and REPORT_
- Hadoop WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using b
- Using Qt to build an Omi App for iOS (and Android)
- build dynamic libraries for iOS and load them at runtime
- METHODS OF AND APPARATUS FOR USING TEXTURES IN GRAPHICS PROCESSING SYSTEMS
- Oracle Introduces Oracle Cloud File System for Private Clouds
- 金融信息系统中Data Integrity、Support HA and Load Balancing及Multi-locations的技术实现举例
- Apache/Tomcat with Failover and Load Balancing in 20 minutes or less…
- Tutorial for building J2EE Applications using JBOSS and ECLIPSE Chapter 4
- Suggestion for using "auto" from Herb Sutter
- Tutorial for building J2EE Applications using JBOSS and ECLIPSE -7