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 scalable. The solution is end-to-end Microsoft .NET, with a smart Microsoft Windows client, an order-processing XML Web service, and an internal Windows application used to fulfill orders. One interesting aspect of this system is that Microsoft Message Queuing is used to send notification messages when orders arrive. Another interesting factor is the Windows client, which sports a data-driven interface. It provides an excellent example of how you can make a dynamically updatable Windows application without relying on automatic downloads.



Microsoft. NET Distributed Applications(c) Integrating XML Web Services and. NET Remoting
MicrosoftВ® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting (Pro-Developer)
ISBN: 0735619336
EAN: 2147483647
Year: 2005
Pages: 174

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net