P
Patrick
I'm writing a winforms database application in C#. I've come across a lot of
stuff lately about "N-Tier" architecture.
Can anyone give me a simple explanation of N-Tier? The descriptions that
I've found online are chock full of lingo that I simply don't know. I need
the "N-Tier" for Dummies description. Talk to me like I'm in kindergarten.
Of course, I'm particularly interested in how N-Tier relates to creating a
winforms database application in C#.
As far as I understand "tiers", it appears that I'm currently using a 2-tier
architecture. What is N-Tier, and why is that more desirable? What is
"business logic"? Is that where you do your data validation?
(What I really can't wrap my brain around is how you could possibly remove
the data validation from the gui, particularly in a winforms application.)
Thanks!
Patrick
stuff lately about "N-Tier" architecture.
Can anyone give me a simple explanation of N-Tier? The descriptions that
I've found online are chock full of lingo that I simply don't know. I need
the "N-Tier" for Dummies description. Talk to me like I'm in kindergarten.
Of course, I'm particularly interested in how N-Tier relates to creating a
winforms database application in C#.
As far as I understand "tiers", it appears that I'm currently using a 2-tier
architecture. What is N-Tier, and why is that more desirable? What is
"business logic"? Is that where you do your data validation?
(What I really can't wrap my brain around is how you could possibly remove
the data validation from the gui, particularly in a winforms application.)
Thanks!
Patrick