This post originated from an RSS feed registered with Java Buzz
by dion.
Original Post: Planning for size in your web application
Feed Title: techno.blog(Dion)
Feed URL: http://feeds.feedburner.com/dion
Feed Description: blogging about life the universe and everything tech
In the fun application that I have been talking about, we keep running into issues like the slow tree. They all come down to one thing. Noone thought about success, and how it would handle size.
When you are running on a dev machine and have 3 test users, it may make sense to have one "Users" tab that has on it:
list all users
list all special users
add user form at the bottom
However, when you get popular and have a million registered users or so, this page becomes REAL slow, and what if you just wanted to add a damn user!!!
Obviously, we went in on the new system and have 'add user' as a separate action, and instead of listing all of the users admins go in and search for what they need.