Nowadays, every decent developer will tell you that if don’t segregate the logic in three layers (data access, business logic and presentation) you’ll will fall in troubles in the near future. And they’re right. But our beloved Remedy presents us a developing paradigm that is completely apart form the three layers design. A year ago I was explaining a Java developer how are the ARS insights and what are the main concepts of workflow programming. The answer was the greatest truth of all time: “Seems like a big Microsoft Access for servers“.
Think a moment:
- In MS Access the code is attached to the forms.
- In MS Access your code is executed is response to events.
- In MS Access, the data access layer is intrinsic to the platform, and the business logic and presentation layers are joined.
Well, I must say that MS Access is a great product that suffers a not so good reputation. You can build amazing applications using Access. But it lacks the robustness of Remedy, the multiuser environment (yes, Access is multiuser, but … Have you tried to connect a hundred users to the same .mdb?), the scalability, the client-server architecture, …
Although ARS developing is not three layers oriented, you can follow a set of best practices to meet a three layer design. But this is another post…