It seems that we have past the top of the hype around Platform-as-a-Service. A good moment to assess how serious the adoption of PaaS is in the enterprise. The different PaaS flavours It’s a while ago that I tried to structure and categorize the different cloud approaches to clarify the different types of “cloud” that we see in todays market. I distinguished among 3 layers of Platform-as-a-Service (and some more layers that.
Last month I was in Barcelona at the HP Discover conference and I followed the coverage of DockerCon a bit as well. Two conferences, the first from one of the largest tech companies on the planet, a company which inception was one of the triggers of the start of what we now call Silicon Valley. The second conference organized by a relatively new company that you could consider a far offspring.
A couple of weeks ago we had Mendix World, our global community event. I really enjoyed the event! It was inspiring to talk with so many of our users, customers, and partners, and to just feel the vibe. If you missed it you can get a glimpse of the experience from this photo overview as well as all the content on the Mendix World recap page. I opened the second.
A couple of months ago I was keynote speaker at an event about modern application development environments. Here are the slides and a brief abstract.
Platform-as-a-Service (PaaS) is hot! Why? Because the year started with a lot of link-bait articles declaring PaaS dead. That’s a clear sign, right? More seriously, the expected size of the public PaaS market will be $14 billion by 2017. That’s about 10 percent of the application development and deployment market, which means two things: PaaS is becoming significant and there still is plenty of room to grow. If this doesn’t.
“I work for a PaaS company” I answered him. “Ah, okay, great”, and he moved to another subject. It was a cold winter day on a hipster cloud conference. He wasn’t the only one that directly knew what my company did. Most people there knew the difference between Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS) and therefore knew exactly what a PaaS company did, right? Well, not exactly… Nowadays, it’s.
This morning I was part of a panel at the GigaOM Structure:Europe 2012 conference in Amsterdam., titled: The Evolution of Private PaaS solutions. The abstract: Enterprises are starting to take interest in running PaaS solutions virtually, as app developers want to focus on building apps rather than dealing with infrastructure issues. Enterprises that use PaaS solutions almost always go down the private route. In this session we focus on private.
Earlier this year a Technet sponsored study showed that in February there were roughly 466,000 jobs in the “App Economy” in the United States. This so-called App Economy had zero jobs just 5 years ago, before the iPhone was introduced. The term “App Economy” isn’t formally defined but is often used to refer to the economy that has been created due to the development and delivery of software applications for.
I finished my last blog post by introducing a Platform-as-a-Service subcategory called “Application Delivery Platform-as-a-Service“ as a way to distinguish platforms that focus on improving the entire application delivery lifecycle (and not just application development or deployment). I would like to clarify my views on Application Delivery and PaaS a bit more. My first attempt has been published on InfoQ yesterday. The short summary: business agility is key, so focus.
Platform-as-a-Service (PaaS)… I guess you heard this term quite a bit last months. I wrote about PaaS earlier when arguing that Model-Driven Engineering is essential for the success of a PaaS and when I announced the new major release of our platform. If you look at the industry perception of PaaS the main definition is something like: it is a public cloud platform where you put code in and get.