SCALABILITY: When to use components

Results 1 to 3 of 3

Thread: SCALABILITY: When to use components

  1. #1
    Jason S. Harmon Guest

    Default SCALABILITY: When to use components

    Sorry for the cross-post, but it&#039s somewhat applicable...<BR>I&#039m on the verge of implementing an ASP site to front-end an Oracle 8i database, using stored procedures exlusively. The database is designed well, appears to run fast, and the interfaces appear to be not much more than displaying parameters from the sp&#039s. Here&#039s the catch: the proposed number of users for this site by next year could be pretty phenomenal. Ten to twenty thousand active users is probably not an outlandish number, in the short term. Long term, this number could grow exponentially.<BR>My question is this: If I&#039m simply calling sp&#039s from the database to display parameters, is there truly much of a scalability advantage with building a custom component just to call the sp&#039s? I&#039m actually a big proponent of using them, but in this case, I think that timeframe may be the big issue on their minds, as opposed to quality of coding or long term vision. I&#039m just trying to justify my VB component design.<BR>Does anyone have some general stats or articles on when you should/shouldn&#039t consider component based design? Sorry for the wordiness, but thanks in advance....

  2. #2
    Join Date
    Dec 1969

    Default RE: SCALABILITY: When to use components

    The difference in speed is largely due to the stuff being compiled vs interpreted. Each time someone calls the same page, the asp.dll must interpret the code in the asp file and execute the instructions accordingly. When you compile a component dll file, the stuff is already interpreted/compiled. There are other advantages, but, at least for my money, this is the biggest one.

  3. #3
    Michael D. Qualls Guest

    Default RE: SCALABILITY: When to use components

    I always compile my data access scripts into VB DLL&#039s. That way I am able to take advantage of everything MTS offers. I have found in my experience that when you are getting 100&#039s of hits a day, there is little performance difference between interpreted scripts Vs. compiled scripts. But when you start getting into 1000&#039s of hits, you will notice a big difference. PLUS the scalability support that MTS offers should never be underestimated. If your site should grow to 10&#039s of thousands of hits a day (or more) the ability to use MTS to distribute your application across multiple servers can be a life saver!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts