Two ways of Java cloud computing

Recently, people are thinking about how to use Java to implement cloud computing, and I see two trends. They overlap rather than repel each other, but in general they have very different performance in terms of projects:

Re-ui (Heavy UI oriented)

This type of application or framework typically provides a UI-based console, administrative usefulness, plug-ins, and so on, providing the only way to manage resources in the cloud, such as starting and stopping images. The key feature of this approach is that it requires a large number of user input and human intervention, so this becomes relatively dynamic and does not change on demand. The best examples are: Rightscale, Gigaspaces, Elasticgrid.

Re-oriented framework (Heavy framework oriented)

This approach emphasizes the dynamic nature of resource management in the cloud. The key feature is that it does not require user input and human intervention, so resource management can be accomplished programmatically by Grid/cloud middleware. Google App Engine (for Python), Gridgain is the best example of this.

Now, we can easily see the benefits of both approaches. In the traditional computing environment, the network and system administrators manage the cloud (the traditional data center is so managed), the developer has little control over it, so the first method is very effective.

As I said, the second method sounds novel and modern. Its purpose is to remove the barrier between the local workstation and the cloud (internal or external) by providing transparency of relative positioning. This allows developers to write code, build and run them in exactly the same way, regardless of whether the work is done at the local workstation or thousands of-kilometer cloud or both.