Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 07ea54c) | patch
New multi-threaded test client script 51/90551/1
authorArthur Martella <arthur.martella.1@att.com>
Wed, 26 Jun 2019 20:03:25 +0000 (16:03 -0400)
committerArthur Martella <arthur.martella.1@att.com>
Wed, 26 Jun 2019 20:03:25 +0000 (16:03 -0400)
commit654d7e7cc76bf98ad29d93cfa53c37cafa79a1f0
tree4af7980c2d11c4015a715f0c62dac409af79433ftree | snapshot
parent07ea54cfc9341cfc5cc64526e1d357981e6841edcommit | diff
New multi-threaded test client script

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