OverviewUntil now, we've been writing code without taking into account how many users would be accessing our application. However, applications are put on the Web because we want lots of people to use them. In most cases, the more people accessing a web site, the more successful it's deemed to be. Now that you've learned the basic aspects of data-driven application development, we need to start talking about how to use what you've learned to create applications that can support the number of users you hope to have. If your application crashes because one half of an update your user makes is successfully written to the database but the other half fails, users are going to go elsewhere. If, for example, you have an online ticket-ordering application and an error occurs after reserving the tickets in a customer's name, but before charging their credit card, you have lost money.
In this chapter, we're going to cover the following areas:
|