The End of the Stovepipe

A recent question for us was, what latest technologies like cloud services, databases, containers and so on we’d be choosing as application architects for the travel industry. Somehow, this question implies that future solutions need to be built having SaaS in mind.

We’d go for Serverless ( and use Docker containers as a deployment scenario, but not on AWS, Azure, Oracle or other giants since these will probably be turned into a lock-in trap very soon and keep al the benefits from their technical scalability as monopoly wins. Nowadays it's that easy as 123 to set up your OwnCloud and you will find tons of metal in all places of the world where you can install your Linux and run it.

The software building blocks should be of very solid material, which, in our view, disqualifies all php frameworks, but also JavaScript Server side approaches, including ECMAScript or TypeScript or however they will be called tomorrow. Who will pay for re-inventing the wheel every day?

Html5 is for the front-ends. Native app development is not an issue any more except perhaps for gaming. The browser is the new desktop and the new mobile.

And yes, you will need some fast transactional databases and also a place where complex attribute definitions can be stored comfortably. Having a good persistency framework takes away much of the database problems. Relational is commodity, and open source databases like MariaDB have a proven success record in many critical configurations.

Years ago, we decided to become a 100% Java company when it comes to programming for it covers most of the above considerations. We would rather stick with JEE, because it is an industry standard and avoids early mistakes or pitfalls letting the Spring guys sort it out first. As a small company we can’t afford many mistakes. So here are the corner stones:

- Linux

- Docker

- Java

- Payara Micro Application Server (we just love executing our services on Raspberry Pi devices)

- MariaDB