Paasmaker — Paasmaker 0.9 documentation. Introduction to-paa s. What Exactly is Cloud Foundry? We Recommend These Resources The PaaS on PaaS marketure has me confused. The ecosystem surrounding Cloud Foundry demonstrates how PaaS, the middle level between SaaS and IaaS is actually a multi-layered market space. A way to unwind the recursive relationship between Cloud Foundry and ecosystem partners is to first start calling the technology a ‘cloud-enabled platform’, and limit PaaS as an instantiation of the cloud-enabled platform delivered as a service.
The CloudFoundry ecosystem partners (e.g. AppFog, Stackato, Uhuru, Tier3) seem to be competing on ease of use enhancements, bundled technology (e.g. language support, cache support, database support), or managed hosting. I get confused when I hear AppFog or Stackato described as PaaS’ running on top of Cloud Foundry, which is also marketed as a PaaS. But the last paragraph still doesn’t describe ‘What is Cloud Foundry?’ WSO2 Carbon / Stratos Application Platform. Using Federated Authentication via OpenID in Google App Engine - Google App Engine. Everything Is PaaSible. PaaS will allow application developers to always use the right tool for the job; including tools that aren’t even conceived as potential application tools. I'm not much of a cook. Of the many errors I commit in the kitchen, the most common is a failure to use the right tool for the job.
Not because I don't have it, or I don't know how to use it, but because I over-optimize for the post-cooking cleanup at the expense of the cooking experience. The saucepan used to boil the potatoes isn't the best tool for a sauté, but it's already out and it will do. The wooden spoon used to stir-fry vegetables doesn't make as good a serving instrument as the metal ladle, but it's already dirty so let's use it. What is true for cooking is true for software development. Enterprise applications are made of more than just code. The next leap in making it practical to always use the right tool for the job will come with PaaS. This change is even more profound than it seems.
Example 2: Business is code. What is Platform as a Service (PaaS)? | Mitesh's Blog. PaaS – Platform as a Service what is platform as a serviceAs per NIST’s definition of Cloud Computing, Cloud has 5 essential Characteristics, 4 deployment models and service models. NIST’s Architecture of Cloud Computing (Source: NIST) What exactly Service models mean? In plain English, Models which provides “Services”. We get Electricity as a service in our daily routine and we pay for what we use right? Similarly we get “Services” from the Cloud Service Providers in different forms. Service models are also known as SPI Model: Software as a ServicePlatform as a ServiceInfrastructure as a Service Different business objectives and different requirements results into different service models as described in following Figure: Everything as a Service – XaaS So, let’s talk about Platform as a Service, commonly known as PaaS in the Cloud World.
What you get? What is Platform as a Service What can you do? Develop-> Deploy->Test->Deploy… Which are the components of PaaS Platform? Benefits? Challenges: 1. 2. As PaaS funding winds down, Standing Cloud raises $3M — Cloud Computing News. Threading the Needle with PaaS-based Policy. After my previous posts on PaaS, JP Morgenthal (Twitter: @jpmorgenthal) and I have had some offline conversations. The discussion resulted in JP putting together the following blog post.
He has graciously allowed me to post it here at ServiceMesh.com. It should be noted that the issues JP identifies below are largely restricted to public PaaS. Private PaaS can avoid these issues through private deployment location choices. With that said, take it away, JP… The common definition and reference architecture for cloud computing lists three service models: Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS).
To illustrate how these service models relate to issues of governance, let’s look at the requirements for data sovereignty—the rights over the data based on geographical control of locale. Cloud service providers are finding solutions that satisfy their clients’ needs to this issue. Let’s explore this need with a concrete example. OpenShift: Is it really PaaS? Redhat recently announced an upgraded version of OpenShift with exciting new features including support for Java EE6, Membase, MongoDB and more. See details at: As I dug through the descriptions, I found myself with more questions than answers. When you say Membase or MongoDB are available as part of the PaaS, what does this really mean? For example: They're pre-installed in clustered or replicated manner? Ok, you get the idea. It's no secret that I'm a fan of Amazon's approach of releasing their full API's (AWS Query, WSDL, Java & Ruby API's, etc.) along with some great documentation.
CumuLogic. PaaS Is The Future Of Cloud Services: Cumulogic Goes Public Beta. Cumulogic, the first company to offer private PaaS solution, today announced that they are making their platform open to public in beta form. You can download Cumulogic platform from their website and run on public and private clouds. They offer a powerful Java PaaS supporting all the Java Frameworks including Spring. I have been talking to Cumulogic from their early days and I am pretty impressed with their platform. Once the IT department deploys their platform on a public or private cloud platform, the developers can just upload their war files and, boom, they have a easily scalable application running on the cloud. It is as simple as that. First, some background on the PaaS space Regular readers of this blog know that I am bullish on the future of PaaS. Cumulogic’s Position In PaaS Market Even though VMware’s CloudFoundry is on a strong footing, they are still in early stages when it comes to deploying in production environments at the enterprises.
Cumulogic Platform Conclusion. What’s in Store for 2011: A Few Predictions. It is true that predictions for the new year are best made before it begins. And predictions regarding consumer technology trends specifically should certainly be made prior to CES. All fair complaints. Which I will now ignore. The following are my predictions for the upcoming calendar year. They are informed by historical context and built off my research, quantitative data that’s available to me externally or via RedMonk Analytics, and the conversations I’ve had over the past twelve months, both digital and otherwise.
They cover a wide range of subjects because we at RedMonk do. With respect to their accuracy, as with all predictions these are best considered for what they are: educated guesses. On to the predictions. Browsers Firefox Will Cede First Place to Chrome, But Not Without a Fight We built RedMonk Analytics to track developer behaviors, and what it is telling us at present is that Firefox and IE both are losing share amongst developer populations to Chrome. Cloud Developers Data. Coté's People Over Process » Despite much hope, PaaS momentum hasn’t blown the doors off yet. Touted at the next thing in cloud, Platform as a Service is receiving much attention now.
While PaaS has been far from a failure, it hasn’t been a mega success…yet. I’ve been talking with several people about Platform as a Service use recently: with all the vendors (and us analysts as well!) Going on about how great it is, I’ve been trying to assertion both current momentum and ongoing developer desire. The point of PaaS is to make a developer’s life even easier: you don’t need to manage your cloud deployments at the the lower level of IaaS, or even wire together your Puppet/Chef scripts.
The promise of PaaS is similar to that of Java application servers: just write your applications (your business logic) and do magic deployment into the platform, where everything else is taken care of. Pioneers like Heroku have certainly proven that out, initially. Taking Stock Coming across PaaS usage numbers can be difficult. Sentiment, anecdotes, and other fuzzy analysis PaaS 3.0. Anant Jhingran's Musings: Pain vs. Gain for Different Cloud Layers. I have talked about in the past that cloud decisions are not made in vacuum, there is a definite tradeoff of pain vs gain. On the gain side are obvious reductions in capex, opex and even increased business flexibility (by making IT available very easily so that more things get done).
On the pain side are increased requirements for standardization, increased application model change, and risks (perceived or real) that come with increased sharing. I have also talked of the fact that IaaS, PaaS and SaaS are not one thing. I will elaborate on it in more detail in a later post (gotta write it!) , but as I alluded to here. Pattern based deployment, a la IBM Workload Deployer Standardized Shared but conformant to current application structures, such as Relational-Database-as-a-ServiceStandardized Shared but requiring new application structures (i.e. rewrites to take advantage) such as Google App Engine's view of databases. So the key question for all of us is: how linear is the pain/gain curve? Enterprises want app stores too. (Page 1 of 2)Apple's iPhone didn't just revolutionize smartphones; it also introduced the first concrete and successful app store in the world. Four years later, app stores aren't just for consumers anymore.
A number of companies are pushing their own variation on the app store theme in order to bring enterprises onboard with this simpler way to distribute software. App stores in the last year have begun to creep off of phones and onto desktops. With Apple's newer Mac Store and Intel's AppUp app store, a large variety of software can be found for uses that have traditionally been performed by boxed software. But with the app store model comes the ease of automatic updates, simple installations and quicker discovery by users, all benefits that are appealing to the enterprise. To that end, MobileIron offers private enterprise app stores that can be hosted from within a company in order to disseminate applications to employees. The platform-as-a-service cloud: Developers are in charge | Application Development. Platform-as-a-service (PaaS) cloud computing, in which full-fledged application development and deployment capabilities are provided rather than just raw iron and compute cycles such as in Amazon Web Services, is set to gather steam as a deployment option for programmers.
But the market is still in start mode, and developers are calling the shots. Currently, PaaS is a $2.8 billion market, but "it will become over the next 10 years a $10 billion market," says Forrester Research analyst Stefan Ried, who recently published a report on PaaS. Microsoft's Windows Azure and Salesforce.com's Force.com are currently the leading platforms for coders in the fledgling PaaS marketplace, according to Forrester. But the list of contenders is long, ranging from Google App Engine to services from companies such as Caspio, Engine Yard, LongJump, OrangeScape, Tibco, and WaveMakers, Ried says. On the Battle Lines of PaaS–The Future is Bifurcated. Friend and one-time colleague Krishnan Subramanian posted recently his view of the different ways PaaS products can be differentiated. Very briefly, Krish classed products in three distinct categories; Traditional PaaS models (push your app to the PaaS and all the underlying stuff is taken care of).
Examples – Heroku, Google App Engine, PHPfogThe Amazon model (package the PaaS but allow devs to get their hands on the underlying infrastructure). Examples – Amazon Beanstalk, Azure VMRoleFederated PaaS (a federated ecosystem at the PaaS layer). Examples Cumulogic and VMware CloudFoundry I’m not sure the battle lines are quite so distinct, but hats off to Krish for trying to show the continuum that exists here. I spent some time talking with a friend who is deeply involved in developing on Heroku – his perception is that the new functionality is highly relevant to the technical critique they’ve been facing – specifically at an enterprise (read robust) level. In his post, Krish contends that; Node.js PaaS Nodejitsu Open-Sources Several Tools. Nodejitsu, the original Node.js platform-as-a-service, has open-sourced several of its tools, some of which are used in its own production stack.
These could be useful to those running their own Node.js servers or private clouds. Some of the tools are very simple, like forever, which ensures that a script runs continuously. Others are more involved, such as the application server haibu and the cloud deployment tool jitsu. You can find all sort Node.js goodness at Nodejitsu’s GitHub. Here’s a partial list of tools: Nodejitsu now has several competitors in the Node.js PaaS space, including VMware CloudFoundry and most recently Heroku. Also, Nodester (formerly known as NodeFu) runs a Node.js PaaS based on some of Nodejitsu’s open source tools, but promises to release some of its own open source tools. Advanced Computer Science Courses : Paper Trail. Below I’ve collected some links to advanced computer science courses on-line. I’m concentrating on courses with good lecture notes, rather than video lectures, and I’m applying a rather arbitrary filter for quality (otherwise this becomes a directory with less semantic utility).
This is the good stuff! But only a subset of it – any recommendations for good courses are gratefully received. I’m mainly interested in systems, data-structures and mathematics, so reserve the right to choose topics at will. Courses are organised by broad topic. Systems Graduate level operating systems courses don’t typically have notes – they all come with long reading lists taken from SOSP and other places. Cornell CS 614 – Advanced Course in Computer Systems – Ken Birman teaches this course. Databases Brown CSCI 2270 – Advanced Topics in Database Management – no notes but a good set of readings. Distributed Algorithms Data Structures and Algorithms Discrete Mathematics and Probability. Why a JavaScript hater thinks everyone needs to learn JavaScript in the next year. I’ve long looked at JavaScript as a second-class citizen in the programming world. Early on, it was the source of numerous security problems; it was a nice bit of glue to patch together HTML applications with a bit of styling, but nobody would use it for serious code; and so forth.
Java, Ruby, Python, they were the languages for doing real work. But my attitude toward JavaScript has changed completely in the past few years. JavaScript has “grown up.” I’m sure there are many JavaScript developers who would take issue with that judgement, and argue that JavaScript has been a capable, mature, and under-appreciated language all along. They may be right, though you can write any program in any complete programming language, including awful things like BASIC. The potential of Node.js Node.js has the potential to revolutionize web development. Two things make Node particularly valuable, though. Second, Node has benefitted from an enormous pool of JavaScript developers. HTML5 is about JavaScript. App Engine: Google's deepest secrets as a service [printer-friendly]