Question

I’m trying to design a solid server side architecture and came up with this :

http://www.monsterup.com/image.php?url=upload/1235488072.jpg

The client side only talks to a single server file called process.php, where user rights are checked; and where the action is being dispatched. The business classes then handle the business logic and perform data validation. They all have contain a DataAccessObject class that performs the db operations.

Could you point the different weaknesses such an architecture may have? As far as security, flexibility, extensiveness, …?

Answer 1

Your architecture isn’t perfect. It never will be perfect. Ever. Being perfect is impossible. This is the nature of application development, programming, and the world in general. A requirement will come in to add a feature, or change your business logic and you’ll return to this architecture and say ‘What in the world was I thinking this is terrible.’ (Hopefully… otherwise you probably haven’t been learning anything new!)

Take an inventory of your goals, should it be:

this architecture perfect

or instead:

this architecture functions where I need it to and allows me to get stuff done