architecture is for all the business logic in be in the database.
-Matt
On Jan 14, 2004, at 11:58 AM, Adam Churvis wrote:
> > > involved, which is the only way it should be.
> > >
> > That isn't the only way it should be. Many people refuse to put
> > business logic in there database because they are using an N-tier
> > architecture where the business-tier handles all the business logic
> > leaving the data-tier to what it is really good at, storing and
> > retrieving data. You might be interested to know that almost all
> large
> > enterprise systems developed in the last five years use an N-tier
> > architecture. Business logic in the database is a hold over from the
> > 2-tier days long since past.
> >
> > -Matt
>
> Yeah, perhaps "the only way it should be" was a bit too strong a
> statement.
> I was assuming his application was nowhere near the scale of a large
> enterprise system, and so my intention was to emphasize data integrity
> by
> binding such logic to database events.��Perhaps I'm mistaken, but it
> didn't
> sound like he was talking about anything requiring a separate business
> logic
> tier.
>
> Respectfully,
>
> Adam Phillip Churvis
> Member of Team Macromedia
>
> Advanced Intensive ColdFusion MX Training
> ColdFusion MX Master Class:
> January 12 - 16, 2004
> http://www.ColdFusionTraining.com
>
> Download CommerceBlocks V2.1 and LoRCAT from
> http://www.ProductivityEnhancement.com
>
> The ColdFusion MX Bible is in bookstores now!
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
