Share a large invoicing supply Chain project (multi-tiered architecture, distributed WCF Multi-server deployment, Microsoft Enterprise Library architecture)

Share a large invoicing supply Chain project (multi-tiered architecture, distributed WCF Multi-server deployment, Microsoft Enterprise Library architecture)

This is a relatively large project, ready to open source. Support N store operation simultaneously. Remote Wcf+ Enterprise Library 5.0 implementation.

This piece should be considered as the core module in the Inventory module, because the block's business logic is more, more cumbersome, roughly speaking business logic bar, the approximate logic is: out of the library single/out of the library single--and fill out the order--out of the library/storage--and modify the inventory information, in order to complete the warehouse, Order can not be reversed, but also to achieve the deletion of the order, modify, in the inventory information changes due to the table and the table has a lot of foreign key relationship, so at the same time to delete more than one table contains delete information content, to achieve the cascade Delete, because here to ensure consistency of results, so with the transaction to achieve. Look at the interface, in order to ensure that the user in accordance with this logical sequence operation, first I added a pair of radio box (out of the library list, warehousing orders), when the radio box is not selected, Save Order button, out of the library, the inbound button is not available, when the user selected the order type, save Order button to become available, Need the user fill in the order information, fill in the corresponding information after saving the order, after the success of the list box to save the order, and the order number is automatically generated, the storage is "s_i" beginning, the library is "S_o" beginning, the following five digits for random generation, so that the order number is easy to distinguish, Also avoids the repetition of the order number, and then according to the user's choice of order type, the corresponding button to be available (out of the library and the Library button), so that the user is always in this order to operate, while the order list box has the Delete Order button, click can delete the Check button.

Directly on the project diagram: A total of three items,

The data entity layer, which is used primarily to obtain data.

The surface of the report, with the Crystal Report.

Business Processing layer. Used to deploy a single server for processing business logic.

In the creation of specific product instances we also use the caching mechanism, each time the use of product features to go back to instantiate a specific product return, so many times using the same product to do a lot of meaningless instantiation, so I added a layer of cache, used to cache the product instances, The next time you need the product, you can read it directly from the cache, improving performance.

I'm using Runtime.Cache.Get () to get the Save,Runtime.Cache.Insert () to add the cache.

Of course, there is also a way to use HttpContext.Current.Cache.Get () to fetch,HttpContext.Current.Cache.Insert () to add the cache.

As for the difference between the two, it involves the ASP. NET life cycle and other aspects of the content, here is not resolved .....

The content in Sqldal is similar to Oracle and establishes a factory to create specific products, inheriting and implementing the methods defined in Idal, and not listed here ...

Large-scale invoicing supply chain system source code. WCF architecture, Microsoft Enterprise Library architecture.

Want to discuss can add my QQ 309159808

Email: [Email protected]

Distributed has two large projects, one is the Entity Data layer: Entityflow, one is the business processing layer WorkFlow. Can be deployed separately to multiple servers. Achieve global operations. The front desk uses the WinForm of the type SAP system. If you need to change to Web. You can change the front desk directly. Background basically do not move.

Share a large invoicing supply Chain project (multi-tiered architecture, distributed WCF Multi-server deployment, Microsoft Enterprise Library architecture)