Enterprise application architecture

August 28th, 2005

A quite prominent round (see link) came up with a list of the 40 most important principles of Enterprise application architecture. As Marinescu I found the least valued principles the most interesting:

1) Use Model Driven Architecture.
2) Determine all your requirements upfront.
and a three way tie between:
3) Use EJBs.
4) Prefer web based UI’s.
5) Prefer open source projects.

Why it came out like this? - Don’t know, perhaps we all resigned viewing the staggering complexity of nowdays systems and perhaps we are a little bit disappointed about the promises of technology and their shortening lifecycle (which is sometimes even too short for a single project).

Well non of the above explains why Web based UI got bashed. I must admit that I never really liked them. Neither from user nor from developer side.

As user I like to use Oracle’s Enterprise Manager. As DB-setup is not my main vocation, I liked its simple, but rather complete interface. With 10g this tool got replaced by a WebUI. Even simpler - but by far less powerful. Precious space on my desktop gets lost by opening multiple sessions to get the same view I had with the former Java App.

As developer I see the promise of thin-client fading. The more comfort we put to these UIs the more client-side code we are about to create. Sometime even duplicating functions from the server side, because the server-langauge is not available on th client. And even the killer-argument that you don’t hav to think about deployments is not true anymore. Where we had to beat ourselves with different client-platforms, the problem is now simply replayced by browser-versions and brands that tend to get as different as Windows & Unix used to be. Add the problems with corporate firewalls and all enthusiasm for web-stuff goes down the toilet.