Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: a98c068) | patch
Configurable "write only locks" 26/92926/1
authorTschaen, Brendan <ctschaen@att.com>
Wed, 7 Aug 2019 16:36:06 +0000 (12:36 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Wed, 7 Aug 2019 16:36:06 +0000 (12:36 -0400)
commit14d46d99cb31f20da0bcfbdd559703cb97bf0baa
tree1319ab6254fb8435ad3ea398d8188a7c3fbc8e15tree | snapshot
parenta98c068aa9a97b73aa1423f432674485a05bdb60commit | diff
Configurable "write only locks"

Issue-ID: MUSIC-466
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
Change-Id: I29c9e0fab3432d152824080ac197a57e0eaf0eff
mdbc-server/src/main/java/org/onap/music/mdbc/Configuration.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/MDBCUtils.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/StateManager.java diff | blob | history
mdbc-server/src/main/resources/mdbc.properties diff | blob | history
The most crucial recipe is a multi-site database cache (mdbc) that enable ONAP components that maintain state in a SQL database to avail the benefits of MUSIC without compromising their need to use transactional SQL DBs. These ONAP components can rely on existing db clustering techniques like MariaDB for transactionality and complex querying within a site. mdbc will intercept each of these read/write calls to the db cluster and mirror this state to other geo-distributed sites through MUSIC either synchronously or asynchronously (configurable at a table-level). For example, components like the ONAP Service Orchestrator that use MariaDB to maintain state can directly use this recipe with no change to their SQL code.