.net - Homegrown integration system OR ESB? -

I have recently started working for a small company which is currently experiencing increasing pain . I'm not sure what kind of arrangement is that I am about to describe here. Essentially we have a lot of different 3 applications that are talking to each other from one house to another. ???? Integration system ???? Which is a mix of SQL jobs, background services are written in NIT, FTP transfers, and SSIS etc.

Here's the bird's eye: Our public face website is the Order Entry System (third party shopping cart software) The seller has submitted the offsite, we download the order information every 4 hours. This data then develops in our home "integration system" which feeds this information to our inventory and Warehouse Management System (WMS). It also gives information to MS Great Plains, Pulse, Payfews, and Third Party CMS etc.

As you have already predicted that this architecture is very weak and a slight accident (such as SQL Job Failure) may cause anomalies in the data, a Domino effect can occur several times when data Due to issues or replication issues, the entire warehouse may still be the reason for standing and we are unable to order, process or ship order several times.

My job is to architect our system again and remove the system's robust coupling to allow business development. What areas should I see? I am researching ESB and SOA but I am told that my company can not undertake half a million dollars to go with Ivy or Tanland.

What are the options? Is the answer to the development of the house and is cheaper than the implementation of ISB? Is anyone going through such a growing pain and if so, how did you handle the integration?

Forget the design in front of the same "perfect" system.

Forget about everything at once in place.

Find out which causes a lot of pain, is relatively easy, and does not threaten the existence of business, work on it.

In some ways, the fact is that "many vessels of 3 different applications" is a good thing.

Find and model your stable business concepts, you can leave better people while focusing on fixing those people. Command and Event Pattern Here are your friends. These concepts should group the following principles in "theories".

From your lesson, it seems that the discussion around SLA has already begun to clarify those SLA discussions, but rather focus on improving on time in the direction of a goal rather than overnight change.

The hand rolling infrastructure is probably not worth the time for this change, but before you spend 6 or 7 figures on the product you know where you are going either are not intelligent, as you mentioned is. Net, I have used it and it's a pleasant programming experience. You focus on your domain and your business logic and NSB has to handle piping / infrastructure. For lesser message throughput, a free option allows you to give some business value before discussing budget and financing. Apart from the documentation on the website, there is a thriving one to help you get started.

There are other options in .net space as well. I have not used them personally and they are not functionally equivalent, so you need to see them and see what your needs and your team's capabilities are.