fmoidu writes "I am a developer for a midsize company, and I work primarily on internal applications. The users of our apps are business professionals who are forced to use them, so they are are more tolerant of access times being a second or two slower than they could be. Our apps' total potential user base is about 60,000 people, although we normally experience only 60-90 concurrent users during peak usage. The type of work being done is generally straightforward reads or updates that typically hit two or three db tables per transaction. So this isn't a complicated site and the usage is pretty low. Finally, the amount of data generated for a user during the lifetime of their use is large, but we can get by with a simple archive of the data because the older data is rarely accessed.
The types of problems we address are typically related to maintainability and dealing with fickle users. Also, from what I have read in industry papers and from conversations with friends, the apps I have worked on just don't address scaling issues. Our maximum load during typical usage is far below the maximum potential load of the system, so we never spend time considering what would happen when there is an extreme load on the system. What papers or projects are available for an engineer who wants to learn to work in a high availability environment but isn't in one?"
This discussion was created for logged-in users only, but now has been archived.
No new comments can be posted.
Learning high-availability server side development 0 Comments More Login /
Get More Comments