This is a bird’s-eye view:
Our public-facing website is an order entry system (third-party shopping cart software) hosted by the supplier off-site. We download order information every 4 hours every day. Then, our local ” The integrated system” massages these data. The system provides this information to our inventory and warehouse management system (WMS). It also provides information to MS Great Plains, Pulse, PayFuse and third-party CMS.
< p>As you might have guessed, this architecture is very fragile, and minor accidents (such as FTP failures for SQL job failures) may cause data discrepancies, resulting in a domino effect. Sometimes due to data-related issues or duplication The problem may cause the entire warehouse to stagnate, and we sometimes cannot accept orders, process or ship orders.
My task is to rebuild our system and eliminate the tight coupling of the system to achieve business growth. I need What aspects of research? I have been researching ESB and SOA, but I was told that my company cannot afford the $500,000 commitment related to iWay or Talend.
What are the options? Internal development is the answer, is it cheaper than ESB implementation? Has anyone experienced similar growing pains, and if so, how did you deal with integration?
>Forget The front-end design of a single “perfect” system.
>Forget to replace everything at once.
>Find things that cause a lot of pain, relatively easy to replace, and will not threaten the existence of the business. Do this first.< /p>
In some respects, the fact that there is a “middle of many different third applications” is a good thing. You can put the better ones in place while focusing on fixing those commercial The most valuable ones.
Find stable business concepts and model them clearly. Commands and event patterns are your friends. Group these concepts into “services” according to SOA principles.
>
From your text, the discussion around SLAs has begun implicitly. Make these SLA discussions clear, but the focus is on achieving goals over time rather than overnight changes.
The infrastructure of manual scrolling for this transformation may not be worth the time, but it is not wise to spend 6 to 7 numbers on the product before you know where you are going. Since you mentioned .Net, I use I used NServiceBus and found it to be a pleasant programming experience. You focus on your domain and business logic and let NSB handle the pipeline/infrastructure. For low message throughput, there is a free option. This allows you to discuss budget and Funding provides some commercial value before. In addition to the documentation on the website, there is a thriving NServiceBus community that can help you get started.
There are other options in the .net field, including MassTransit and EventStore. I don’t have any Use them yourself, they are not the same in function, so you need to check them to see which ones meet your needs and the capabilities of the team.
I just started as a family I am currently working in a small company that is experiencing growing pains. I am not sure what kind of system I will describe here. Basically we have a hodgepodge of many different third applications, which are integrated through a local System” talk to each other. This system is a mixture of SQL operations, background services written in .NET, FTP transmission and SSIS.
This is a bird’s-eye view:
We are open to the public The website is an order entry system (third-party shopping cart software) hosted off-site by the supplier. We download order information every 4 hours a day. Then, our local “integrated system” massages these data, and the system provides this information to Our inventory and warehouse management system (WMS). It also reports to MS Great Plains, Pulse, PayFuse and third-party CMS, etc. provide information.
As you may have guessed, this architecture is very fragile, and minor accidents (such as FTP failures for SQL job failures) may cause data discrepancies , Resulting in a domino effect. Sometimes due to data-related issues or replication issues may cause the entire warehouse to stagnate, we sometimes cannot accept orders, process or ship orders.
My task is to rebuild our System and eliminate the tight coupling of the system to achieve business growth. What aspects do I need to study? I have been researching ESB and SOA, but I was told that my company cannot afford the $500,000 commitment related to iWay or Talend.
What are the options? Internal development is the answer, is it cheaper than ESB implementation? Has anyone experienced similar growing pains, and if so, how did you deal with integration?
This is how I deal with this problem.
>Forget about the front-end design of a single “perfect” system.
>Forget to replace everything at once.
>Find something that causes a lot of pain, it is relatively easy to replace, and does not threaten the existence of the business. Do this first.
In some ways, existence The fact that “a hodgepodge of many different third applications” is a good thing. You can put the better ones in place while focusing on fixing the ones with the highest commercial value.
Look for stable business concepts and model them clearly. Commands and event patterns are your friends. Group these concepts into “services” according to SOA principles.
From your text, around SLA discussions have already begun implicitly. Make these SLA discussions clear, but the focus is on achieving goals over time rather than overnight transitions.
The basis for manual scrolling for this transformation The facility may not be worth the time, but it is not wise to spend 6 to 7 numbers on the product before you know where you are going. Since you mentioned .Net, I used NServiceBus and found it to be a pleasant programming experience You focus on your domain and business logic and let NSB handle the pipeline/infrastructure. For low message throughput, there is a free option. This allows you to provide some business value before discussing budget and funding. In addition to the documentation on the website In addition, there is a thriving NServiceBus community that can help you get started.
There are other options in the .net field, including MassTransit and EventStore. I did not personally use them, they are not the same in function, So you need to check them and see which ones meet your needs and the capabilities of the team.