Universal Containers manages a catalog of overone million products that it makes available to its customers.
The master product catalog is stored and managed in their ERP application with frequent updates made to the product catalog by their sourcing team. The sourcing team may update attributes suchas price, general catalog availability, and the product description. When the sourcing team makes an update that change must go into effect during the next business day and there may be thousands of changes made over the course of the day.
What integration pattern would you recommend to best manage this scenario?

Universal Containers wishes to move data between 3 back office systems: ERP, financial and a legacy home-grown shipping system that will be replaced 3 months after integration is scheduled to be complete.
What integration pattern should an architect recommend to ensure minimal throwaway code?