Four Java Cloud computing evaluation

There seems to be a plot in a thriller that says, "It's easy ... It's so easy. "And then all things began to fall apart. When I started testing the top-tier Java cloud Computing in the market, I found that the episode was repeating itself.

Enterprise developers need to be more concerned about these possibilities than others. Ordinary computer users get excited when there are new scenarios in cloud computing that make life easier. They will use cloud-based emails and, if they are lost, they can only shrug their shoulders because e-mail is often lost and sometimes as often as prayers.

Enterprise developers should not be so optimistic. Every choice that allows us to make one-click Configuration will keep us locked in forever. If we adopt an overly easy cloud computing and let it do too much for us, then we are less likely to have any development.

The danger of "being stuck" seems to be hidden in every corner, which is not necessarily the worst part. What happens when we get rid of the features we need, and we're happy with cloud computing, which is something that cloud providers can't or don't want to offer? Cloud computing will be a world of constant change.

To our comfort, cloud developers are already feeling uneasy about the situation. They know that customers want a one-click solution and a high degree of automation to make life easier. But that means sending out interfaces that are non-standard or that won't allow users to adjust freely. Cloud developers have to figure out whether the market needs to do everything for cloud computing and whether customers want to be free enough to avoid "getting stuck".

For that, I tested the cloud Foundry of 4 major Java Cloud--cloudbees, Google app Engine, Red Hat OpenShift and VMware. They all have many solutions. Some clouds rely on standard tools to obtain standard war files and transmit information. Others also have their own many unique ways.

Cloud computing Experiment: Java version

Java Cloud Computing solutions are getting better and more complex, but they are far from being a complete set of products. Here are a few sets of tools that can be fully exhibited in a state where they are not completely mature. The registration form often prompts us that cloud computing is just a test application for research and development, not for production work. In fact, they are more accurate to call perhaps the cloud Postalpha beta or Prebeta beta.

Because it's all in the stones, even cloud computing, which has already been created, is often changed. Since no one really knows how the load and cost increase, the price will be adjusted, and sometimes the adjustment is very large. Cloud-Computing sellers also don't know how to determine their costs, so it's only a guess when they offer millions of of the processing price.

In the future, pricing can be a very difficult and challenging task for both buyers and sellers. People have been disappointed that Google has stopped subsidizing its app engine. Some users complain that each click makes their costs grow twice times, or even three times times. But who can blame Google? Although Google has excellent financial engineers, I am not sure whether they know the reasonable price for each round-trip to the big table Data Warehouse. They may fluctuate by heavy rains in the north-west. Because some of Google's newest data centers are built there, where hydroelectric power is the cheapest source of energy.

Maybe I think more. But there is always going to be a mistake and prices will fluctuate. Cloud computing has a greater degree of flexibility and automation, which saves us the cost of hiring people to manage these racks and ensure smooth data transmission. If Web 3.0 applications are hugely successful, and cloud computing is expensive, it can still generate enough revenue to pay for all of the program adaptations that apply to porting applications to a set of internal servers. If these web programs are not profitable enough to offset costs, the experience price will not fall. Cloud computing will eventually change: they will simplify the experiment and make adjustments.

Choosing cloud computing involves a lot of experimentation. The simplest is to find machines from Amazon or Rackspace cloud computing, but this is a much more complicated operation than a service provider promises. Yes, I press the button and I can start a computer in a few seconds, but then I spend a few hours online to install the JVM and the rest of the stack.

If you have the time and the will to create a machine image with your favorite software, the original cloud computing machine will meet most of your expectations for cloud computing, but it will also "hold You". Amazon and Rackspace make storage mirroring and replication easy. You need to select the software and determine how many machines you need. Theoretically, you can get more machines at any time. I've tried to generate new machines in everyday transactions, which is great and costs 1.5 cents per hour. When the work is done, they disappear.

Of course, you have to have a comprehensive understanding of yourself. Do you want 100 virtual machines or 102? This is a contradictory question. You have to control your costs, but you don't have the time to react, unless you have higher intelligence in this area.