Re:The 2002 mandate for internal communication systems at Am...
by badpun on Wednesday October 02, 2019 @03:56AM
(#21134221)
Directly interacting with other service's DB is an "Enterprise Integration Pattern" AFAIR? It can make sense in lots of cases.
[ Parent
| on HN ]
Re:The 2002 mandate for internal communication systems at Am...
by dragonwriter on Wednesday October 02, 2019 @05:06AM
(#21134564)
Shared database is, in fact,a classic enterprise integration pattern, and much of classic relational database engineering assumes that multiple application will share the same database; in the classic ideal, each would use it through a set of (read/write, ad needed) application-specific views so as to avoid exposing implementation details of the base tables and to permit each application, and the base database, to change with minimum disruption to any of the others.
Re:The 2002 mandate for internal communication systems at Am...
by arethuza on Wednesday October 02, 2019 @04:03AM
(#21134256)
Reading data from another application's database is pretty common (although even this can cause chaos if done without some care) but writing to application databases is often a very bad idea and often explicitly forbidden by CRM/ERP vendors.