Summary
|
|
Main Page Technical Docs Scaling WebObjects Example Apps Step 0 Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Summary Postscript
|
None of this scaling stuff is rocket science. You figure out what
you're limited by, you fix that limit, and you move on. The key
lesson is that the unlimited WO license didn't come into play
until we'd already spent $200,000 on equipment and database software.
So at that point, WebObjects was only a small portion of the total.
Yet WebObjects let us move across two different machines, two
different database vendors, and six different database network
topologies without having to reengineer everything each time.
In the process, nile.com could go from $10000 in sales a month to nearly $10,000,000 in sales/month. Yippee.com could go from 150 users to 15,000 users. I'd say that WebObjects can scale pretty well if I can go from a single desktop machine to multiple high-end Solaris machines without a hiccup. What I find, is that with WebObjects, my customers can start small, and work their way up, while maintaining profitability. Ultimately, that's what its all about. I've also found my Apple sales representatives to be quite willing to work with me when I'm trying to put together a cost effective solution for a customer, so be sure and discuss any problems you're having with them, that's what they are there for. |