3 years, 4 months ago

Database Hub instead of Message Hub on the service layer

Link: http://www.etc-architect.com/?p=262

About 35 years ago all information was delivered through a data hub, usually a database. However due to limitations mainly on the number of open ports required and the missing latency on the networks in the pre internet time. The solution was to send data packages between applications and later via data hubs. The packages first consisted of a delimited text file and later moved to XML.

The strange thing during this whole time was that virtually every time when someone would suggest to use a database as the hub instead of a message broker, people would state that this idea was tried before and failed without thinking that the limitations may have disappeared. Actually using a data base instead of message broker makes a lot of sense as most messages are often constructed from a database and are again dropped into a database before being consumed by other service. Additionally databases are build on a transaction monitor that takes care of a lot of the transactional error scenarios and validations that first need to be constructed in message hub architecture.

Related Post