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.

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.

Somehow it is a recurring theme in computer science: create a “programming” system that is easier to use and learn than the existing programming approaches. I am not just talking about better tools, like IDEs, but also new languages. It seems as if each self-respecting programmer creates his/her own language or tool-set nowadays, right? Okay, I have to admit that not all efforts are focused on making things easier, often.

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.

If you have been wondering why I was a bit quiet lately… it was for the good cause! Today we launched the third major release of the Mendix platform, which is quite a memorable moment. My team did an awesome job and when I look at the result I can only feel proud! As I have been sharing a lot of my thoughts last years, I want to take the.

Model Driven Development proponents see a lot of advantages of using MDD techniques. Higher development speed, increased quality, more cost-effective, empowering less-experienced developers, just to name a few. If you look at these promises the question arises why the whole world isn’t using MDD right now? Why don’t we hear a lot of MDD success stories? In a recent article I wrote about some of the main concerns which prevent.

About a month ago Kees Dijk asked a question on the programmers StackExchange titled “Why aren’t we all doing model driven development yet?“. He reiterates his question also as “What do you see as the biggest problems that make you not even consider model driven development?“. It shouldn’t be a surprise that I’m interested in these kind of questions. The answers, in this and other discussions about this subject, are.