Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: e5193d2 ca670ec)
Merge "Maintain server checkpoint locations"
authorThomas Nelson <nelson24@att.com>
Mon, 8 Jul 2019 17:55:56 +0000 (17:55 +0000)
committerGerrit Code Review <gerrit@onap.org>
Mon, 8 Jul 2019 17:55:56 +0000 (17:55 +0000)
commit8676c0e2fa908386d81ed8e3f0ee4018e99445f7
tree4f5aca1c88b6be8b562a2cd55385c5fefac6bb0etree | snapshot
parente5193d27f0f6d0ded1c59360f89e0543ee7f10aacommit | diff
parentca670ecc97305331c27d0491b88cca490e1fdecfcommit | diff
Merge "Maintain server checkpoint locations"
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcConnection.java diff1 | diff2 | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ownership/OwnershipAndCheckpoint.java diff1 | diff2 | 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.