2

I am looking for a solution for real-time data integration between few on-premise databases. There is no much transformation of data involved. I am evaluating various ESBs available. I am thinking that data integration using Azure Service Bus as quick to develop a solution. Is it advisable to use Azure service bus for integration of all on-premise databases?

tRuEsAtM
  • 3,517
  • 6
  • 43
  • 83
Srinivas
  • 2,479
  • 8
  • 47
  • 69

3 Answers3

5

Unless there is extraordinary complexity in the integration, BizTalk is probably not the right tool for the job here. On the other hand, sending data out to the cloud just to transform it back to another database (on the same LAN?) is also not the right approach - this will introduce latency and traffic cost.

(Near) Real Time integration of databases sounds like a job for something like:

If you really want to build a service bus, either build a local AMQP based bus as Sam suggests (e.g. Windows Service Bus or Rabbit), or buy an existing product (NServiceBus etc).

Community
  • 1
  • 1
StuartLC
  • 104,537
  • 17
  • 209
  • 285
  • If it is indeed database to database communiation, go with SSIS, as Stuart mentions! That service is built to do exactly that. – Sam Vanhoutte Mar 17 '14 at 08:29
4

If you have all your applications 'on prem', you introduce an extra risk by moving your integration layer to the cloud (suddenly your internet connection could bring down your integration layer) but the good news is that you can use Service Bus for Windows Server, that you run locally (even with Windows Azure pack!) The same programming model, similar messaging features, so that might be a good option.

Comparing with BizTalk... Service Bus is light weight, messaging only. BizTalk provides much more rich features (transformations, pipelines, BAM, Business Rules, adapters).

Good luck

Sam Vanhoutte
  • 3,247
  • 27
  • 48
  • Thanks for the idea, here in the Supported Topologies it is mentioned like one server for all databases . my upstream databases are in multiple servers (around 12 servers). does service bus for windows server still works? – Srinivas Mar 17 '14 at 04:36
  • 1
    Service Bus really has nothing to do with your other databases. Service Bus just used his own database for persistence, configuration, etc (hence the topology diagram you refer to). If you need to connect to other databases or systems, you will have to write/code this yourself. Service Bus will just do the messaging, eventing, etc. If you don't want to do that, BizTalk can help you out – Sam Vanhoutte Mar 17 '14 at 08:29
0

If you are only looking to integrate between a few on premise databases then you might consider using Sql Server's Service Broker (http://msdn.microsoft.com/en-gb/library/bb522893.aspx).

It provides a reliable asynchronous way of passing data between databases in a real time way. It can manage the message order and can have numerous conversations running at the same time on the same queue, each being processed by its own instance of the receiver.

There's a good overview here... http://technet.microsoft.com/en-us/library/ms166104(v=sql.105).aspx

AJC812
  • 13
  • 3