|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".
Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
Sep. 30, 2016 02:30 PM EDT Reads: 5,177
There are several IoTs: the Industrial Internet, Consumer Wearables, Wearables and Healthcare, Supply Chains, and the movement toward Smart Grids, Cities, Regions, and Nations. There are competing communications standards every step of the way, a bewildering array of sensors and devices, and an entire world of competing data analytics platforms. To some this appears to be chaos. In this power panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, Bradley Holt, Developer Advocate a...
Sep. 30, 2016 02:30 PM EDT Reads: 2,458
24Notion is full-service global creative digital marketing, technology and lifestyle agency that combines strategic ideas with customized tactical execution. With a broad understand of the art of traditional marketing, new media, communications and social influence, 24Notion uniquely understands how to connect your brand strategy with the right consumer. 24Notion ranked #12 on Corporate Social Responsibility - Book of List.
Sep. 30, 2016 02:30 PM EDT Reads: 288
Sep. 30, 2016 02:15 PM EDT Reads: 1,720
Sep. 30, 2016 02:15 PM EDT Reads: 1,153
Sep. 30, 2016 02:15 PM EDT Reads: 709
Sep. 30, 2016 02:00 PM EDT Reads: 3,569
Sep. 30, 2016 01:45 PM EDT Reads: 576
Sep. 30, 2016 01:15 PM EDT Reads: 1,287
Sep. 30, 2016 01:15 PM EDT Reads: 311
Sep. 30, 2016 01:15 PM EDT Reads: 5,164
Sep. 30, 2016 01:00 PM EDT Reads: 4,235
Sep. 30, 2016 12:45 PM EDT Reads: 4,492
Sep. 30, 2016 12:45 PM EDT Reads: 2,703
Sep. 30, 2016 12:30 PM EDT Reads: 2,262
Sep. 30, 2016 12:30 PM EDT Reads: 3,271
Sep. 30, 2016 12:30 PM EDT Reads: 497
Sep. 30, 2016 12:15 PM EDT Reads: 3,233
Sep. 30, 2016 11:15 AM EDT Reads: 3,105
Developing software for the Internet of Things (IoT) comes with its own set of challenges. Security, privacy, and unified standards are a few key issues. In addition, each IoT product is comprised of (at least) three separate application components: the software embedded in the device, the back-end service, and the mobile application for the end user’s controls. Each component is developed by a different team, using different technologies and practices, and deployed to a different stack/target –...
Sep. 30, 2016 11:15 AM EDT Reads: 1,576