Timeline for Shared database vs tightly coupled message model
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2020 at 13:03 | vote | accept | johnknoop | ||
| May 4, 2015 at 10:30 | comment | added | Clément Prévost | I don't know Azure Service Bus and how well it integrates with .Net. This could be a good choice but it is more complex than a simple API. So I can't see why it's required in this case. Maybe with more precision about the future of the application, the accepted amount of maintenance and development, the expected workload to process,.. Everything that can be a blocker to one or the other solution | |
| May 4, 2015 at 9:26 | comment | added | johnknoop | I wasn't really thinking of an ESB, but something more along the line of Azure Service Bus. The bus is really just a message queue without any orchestration. | |
| May 3, 2015 at 22:20 | comment | added | Clément Prévost | Yes, based on the described system, an ESB is way too complex for the task, you just need to consume the web app data within an internal application. | |
| May 3, 2015 at 22:13 | comment | added | johnknoop | So what you are saying is, we should set up an internal API hosted within the web app, that our public API may consume? | |
| May 3, 2015 at 21:20 | review | First posts | |||
| May 3, 2015 at 22:56 | |||||
| May 3, 2015 at 21:16 | history | answered | Clément Prévost | CC BY-SA 3.0 |