[Ryan Marfone]

One common question I get from people all the time is: "How should I seperate my application into layers?"

Depending on the nature of the application I will generally answer "In three tiers. One for your UI. One for your business logic. One for your Data.".

I've stuck with this paradigm for a while now because it's served me well. So, I'm curious. How does everyone else do it? How do you architect YOUR applications?

[DeCompile]

Usually you look at it depending on what the program is meant to perform.

When working with databases, you'd create a class/function to check the input before it's inserted/updated/deleted from the databases. Certain checks would include making sure the input is the correct format, correct length, does not contain any nasties etc.

That's your data layer.

Other layers are entirely similar.