Chapter 17. Transact.NET Order Fulfillment
Distributed application programming is, at least partly, a science of compromises. When building a distributed application, you need to decide which parts of the system will bear the greatest burdens. If you choose carefully and balance the workload between client and server according to the available resources, you can create the foundation for a scalable application. If you rely on a shortcut, however, you might create a bottleneck that won’t appear until later, when the load increases and your system becomes a victim of its own success.
This chapter’s case study considers a company that wants immediate order notification and processing and is willing to go to a little more trouble to make it possible—and ...
Get Microsoft® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
