Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: ad9faf2) | patch
Deprecated unused method. logged CREATE statement. 53/74353/2
authorVikram Potturi <vikramaditya.potturi@att.com>
Thu, 6 Dec 2018 20:05:22 +0000 (15:05 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 13 Dec 2018 20:42:01 +0000 (15:42 -0500)
commit8469652e97d83dad0aa3870eb6c78c150ca5b869
treeaccb65a424e325a282a87d0a04c711d1e94026e6tree | snapshot
parentad9faf285c9348728859c49b0883bff82ec5031ecommit | diff
Deprecated unused method. logged CREATE statement.

Change-Id: I39155ef4e523fe4a643089eb26be388ca47aa4d2
Issue-ID: MUSIC-164
Signed-off-by: Vikram Potturi <vikramaditya.potturi@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/query/QueryProcessor.java 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.