Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 361533f) | patch
New test script for MDBC 58/84258/2
authorArthur Martella <arthur.martella.1@att.com>
Thu, 4 Apr 2019 16:51:25 +0000 (12:51 -0400)
committerBrendan Tschaen <ctschaen@att.com>
Thu, 4 Apr 2019 21:51:56 +0000 (21:51 +0000)
commitb7c20b1b912f0e858bd55416ab35c9f93febce94
tree037cc9eb7bfc2bb4aa99f3df8e68f722eb25eb15tree | snapshot
parent361533ff29d77c78a418967229e9fc6d72d46bd6commit | diff
New test script for MDBC

Change-Id: If38bcf83a3d4f6209907f24b358477d158d9eecd
Issue-ID: MUSIC-376
Signed-off-by: Arthur Martella <arthur.martella.1@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/examples/MdbcTestClientNew.java [new file with mode: 0644] blob
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.