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.
There is something interesting going on in our industry. From the inception of the first programming language we always have been uncovering new ways to program computers. New ways triggered by new hardware architectures and new ways triggered by developers wanting languages that are easier to grasp and are more productive. We have made major steps from machine code to today’s higher-level modern languages. However, over the last decade it.
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.
Platform-as-a-Service (PaaS) is all about abstraction and automation. Abstracting away from underlying technology layers by automation. That’s basically what is happening on each layer of a cloud architecture, from hardware to IaaS, to foundational PaaS, to aPaaS. All this abstraction and automation is aimed at making application deployment a one-click or one-command experience for the developer. It makes deployment a self-service experience for the developer, which eliminates hand-offs and thus improves.
Over the last couple of years the engineering team at Mendix has grown fast. Over the last 1.5 years the team has almost doubled and we are still looking for bright minds. There is a lot that can and will go wrong if you grow this fast. Here are my four most important lessons learned during the process (disclaimer: a lesson learned doesn’t necessarily mean that I execute it flawlessly.
Software is eating the world! Every company is becoming a software company. If companies don’t, they cease to exist. Just imagine: you are a thermostat maker and suddenly you have Google as a competitor (via its Nest acquisition). This is just one of the many recent examples. Interestingly a lot of the innovations in the software industry are fuelled by abstraction and automation, concepts that are well-known in the Model-Driven.
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.