Home » Community » View question
Question
Integration strategy best pratice?
In a custom project I want to move confirmed orders (added my own order status definition) from Scensum to an ERP system. I've already created a service running on the ERP side. What would be the best approach to integrate with Scensum?
1. Let my ERP Service read directly from the Scensum database.
2. Create a new/extend the Scensum order service and expose a integration API (web service).
3. Create a new/extend the Scensum order service and write to a new database table (e.g. [myproject].[tOrderIntegration] from which the ERP service can read?
Answers
1. That is easy but you possibly end up with a single point of failure. You canot bring down the Scensum because the ERP will be dependent. It´s quick but still it might be an additional load to the Scensum db server depending on how often the batch job runs and the amount of orders. Take care on modifying values because you override all security and business logic.
2. This might be a nice aproach but again you depend on another systems availability... but if the systems are redundant or failover is not a problem. This gives scensum a great deal of control for last checks of availability in stock etc. and for some customers with not so many items per product in stock, this might be a concideration.
3. Based on experience this is the most robust aproch, keeping the systems separated. ERP och system batches can get event triggers och scheduled updates as needed and are independent from each other. But it´s not for all integration, because of laging between the systems, items in stock can be a problem.
So finally, you have to decide depending on the requirements, hardware configuration, estimated load or orders etc.
You need to login to answer this question