|By Christopher Keene||
|October 24, 2008 07:15 AM EDT||
Chris Keene's "Keene View" Blog
For cloud computing to take off, there need to be tools available that enable a developer to build and deploy an application without having to download anything to their desktop. This requires an on-demand development tool that sits on top of the cloud and provides a development Platform as a Service (PaaS).
There are two paths that a vendor can take to create a development platform for cloud computing: cloud-first or tool-first.
- Cloud-first approach to PaaS: first build a cloud platform, then build a development tool that runs on top of it. This is the approach pioneered by Force.com and followed by Coghead and Bungee Labs.
- Tool-first approach to PaaS: first build a development platform that is host-able tool (e.g., studio runs in a browser), then "push" that platform into the cloud. This is the approach taken by WaveMaker.
For Force.com, it made a great deal of sense to take the cloud-first approach. SalesForce.com already had a robust cloud platform and expertise in building proprietary development tools to create their CRM application. There was also no requirement to make Force.com work on any other cloud, because SalesForce is aiming to be the only cloud you will ever need for all your enterprise apps.
For most software vendors, however, the cloud-first development process has distinct disadvantages. First of all, it puts you in the data center operations business, which requires a very different DNA than software development. Next, it makes development itself difficult, because the cloud adds a level of indirection and complexity to all development tasks. Finally, you will be forced to do cloud port eventually to get to a SaaS cloud people want to deploy on, like Amazon EC2 or Google App Engine (assuming they ever exit the Python ghetto).
A tool-first approach to PaaS development is much more straightforward. You start by creating a host-able development studio (pretty much rules out Eclipse plugins) and do your build and test on standard hardware. After you have build a solid product, you add multi-tenancy to the studio and customize deployment for your cloud of choice (or use a partner like Elastra to do the deployment and administration for you).
A final oddity of the cloud-first vendors is that they have all delivered proprietary development platforms. This provides a "roach motel" level of lock-in - your logic and data can checkin, but just try moving them to another RIA or AJAX platform! Again, SalesForce can throw its 500-pound gorilla weight around and make the Apex language successful. It is hard to imagine, however, that 5 years from now people who have learned the Coghead language will be in more demand than, say, Java developers.
|claeton 11/03/08 10:10:15 PM EST|
Proprietary development toolsets have a long history. PowerBuilder and VisualBasic didn't offer the flexibility and power of C, but they enabled rapid, if inelegant, development of business apps. In the Cloud, the same could end up being true of Coghead. There are a lot of reasons why that would be a suboptimal outcome, nonetheless a possible one.
|Gameshowhost 08/25/08 02:40:15 PM EDT|
What about other PaaS vendors like LongJump and Quickbase? Anyone have experience in using them?
|kennyo 08/23/08 05:04:54 PM EDT|
Don't forget tools that help create "cloud-like" Utility Computing infrastructures out of what you own today (any HW, any VM). Cassatt can primarily do this, although there are other less automated tools on the market too, and even VMware has its eyes on trying to help make clouds.
These tools can automate how HW is repurposed, how and when VMs are created, where networks should be routed etc. etc. with the express purpose of maintaining application service levels, regardless of demand. This is essentially PaaS that is the underpinning behind "clouds".
May. 23, 2016 06:15 PM EDT Reads: 325
May. 23, 2016 05:00 PM EDT Reads: 4,591
May. 23, 2016 04:30 PM EDT Reads: 734
May. 23, 2016 04:00 PM EDT Reads: 1,781
May. 23, 2016 03:00 PM EDT Reads: 1,635
May. 23, 2016 03:00 PM EDT Reads: 557
May. 23, 2016 02:30 PM EDT Reads: 1,674
May. 23, 2016 02:00 PM EDT Reads: 2,316
May. 23, 2016 01:45 PM EDT Reads: 2,030
May. 23, 2016 12:45 PM EDT Reads: 1,302
May. 23, 2016 12:30 PM EDT Reads: 1,775
May. 23, 2016 12:30 PM EDT Reads: 2,016
May. 23, 2016 09:15 AM EDT Reads: 1,642
May. 23, 2016 08:15 AM EDT Reads: 2,368
May. 23, 2016 08:00 AM EDT Reads: 1,911
May. 23, 2016 07:30 AM EDT Reads: 2,007
May. 23, 2016 04:15 AM EDT Reads: 2,338
May. 23, 2016 03:45 AM EDT Reads: 1,663
May. 23, 2016 03:45 AM EDT Reads: 2,943
May. 22, 2016 05:00 PM EDT Reads: 1,856