Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Single tier is still the most
Message
 
À
03/05/2001 16:02:23
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00502430
Message ID:
00503458
Vues:
27
>So I guess what I am saying is that it's easier to design and implement an n-tier system when you have a fully matured, automated business process ...which usually starts as a simple monolithic app that evolves over some time.

yuck... i disagree. It's pure hell to reformulated a monster app to be n-tier after-the-fact. It's much much easy (not too mention cheaper) to design a new app n-tier, and then the subsequent evolution into maturity is so much easier to manage when it's starts out n-tier. If you already have a monolithic app, you've already cooked your goose in my opinion... and I say this because even before n-tier, big apps should of been broken into independent modules atleast, not too mention layered classlibs. And since your goose is cooked, you got twice as much work to re-bake that same goose as n-tier as opposed to taking a fresh goose and doing it right from the start.

Rewrites are always more work, more hassles, and more money than fresh writes... even when the architecture is the same. Even if there's no enhancements to the existing app... it takes more time to sort out the mess in monolithic app than it does for a sharp cookie analyst to draw up accurate requirements on a fresh slate.

And when the rewrite includes an architecture switch, well you just made the work/hassles/money double. In my opinion and experience, rewriting an app to be n-tier will cost the client more money than what they've already invested into a monolithic app that gave no consideration whatsoever to any type of layered/modular/scaleable approach. And that's why I'm not surprised at all by the stat of more single tier vs. n-tier. Of course there's more single tier! And that's because it takes a lot more resources an expertise to do n-tier right as opposed to single tier (it's easy to make bad single tier work than it is to make bad n-tier work). But the pay off is in the long run with n-tier ROI, it just takes a lot more effort to get there for well evolved business processes that need re-architected as opposed to a brand new process.
Roxanne M. Seibert
Independent Consultant, VFP MCP

Code Monkey Like Fritos
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform