Posted by: Jack Vaughan
Cloud Services, middleware
When cloud computing first appeared it looked something like grid computing – albeit with a goodly dose of new age virtualization. The fact was that cloud carried with it the seeds of a revolutionary data architecture that greatly reduced reliance on the relational data base. Relatively new companies such as Google and Amazon built large-scale Web applications – ones that diminished the RDB’s role – and they became the poster children for the cloud …
Some people wondered which languages programmers would use for cloud. Google said “Python.” SalesForce.com said “Apex.” Amazon.com said “Anything you like – plus Web services.” Microsoft said “Dot-Net.” By and large, this all left the established ranks of enterprise Java developers and the emerging ranks of PHP and Ruby developers without a clear stake. But that has changed. SalesForce.com, just as one example, now supports Apex, Java Spring frameworks and Ruby on Rails as a service for the cloudward bound.
When cloud first appeared, in-memory data caches were an interesting grid-style pattern that had found use on some Java server farms. Not without a lot of tweaking, such caches have quietly become standard for high-performance Web apps and compute intensive enterprise jobs. Their role in the cloud is evolving. Both large vendors and smaller best-of-breed players have added them to their arsenal, sometimes via acquisition. Just last week, broad-based SoftwareAG bought caching specialist Terracotta.
Amazon’s services offerings had a big role in getting cloud going. Then, the services buzz subsided, as attention focused on the transformative role of cloud in the data center. Now, more and more, SOA is seen in cloud strategy. Cloud computing may herald new approaches to development and integration, the latter being the primary focus of SearchSOA.com’s ”SOA in Action: Navigating SOA, Integration and the Cloud” virtual trade show, coming up Thursday June 2, 2011. Click here to learn more.