WIN2K IIS web servers
WIN2K server(s) for COM/COM+
WIN2K SQL Server 7
VB 6 - Primary tool
C++ - Where needed on COM layer
Hello everyone -
I have a new client I am working with who has programmed themselves into
a corner (oh yes, we've all been there) and I am now charged with archicting
them into the future.
My biggest concerns are the middle tier issues like:
-- Should we put both COM servers for Business Logic and Data Abstraction
- ie all COM components on the same servers.
-- How big is the cost going to be to marshall data across Tiers where each
Tier represents an actual set of servers ?
My biggest disaster at present:
-- My client has ( do not laugh now ) maxed out the number of fields allowed
in a SQL Server 7 table - ie there are over 250 fields per table in many
of the key tables ( and yes, there are SELECT * in the ASP Pages ). My approach
will be to create a Data COM layer FIRST, where all data will be accessed.
This will allow me to change the underlying schema to a more efficient without
heavy re-writes on the front end ASP. Thoughts ?
The complete application must end up being highly scalable and able to handle
over 5,000 concurrent users during a registration process. And the only way
we can attack the application re-writes is in an evolutionary approach and
not a complete re-write.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL