Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 757040c) | patch
Extra features for multi-thread test script 77/91177/1
authorArthur Martella <arthur.martella.1@att.com>
Wed, 10 Jul 2019 16:24:59 +0000 (12:24 -0400)
committerArthur Martella <arthur.martella.1@att.com>
Wed, 10 Jul 2019 16:46:05 +0000 (12:46 -0400)
commit24f854ddde6164f18ec2c7b6223befe83c583181
tree6a6b43b9e6b804cb89422d8fd3bd3b27d8812be5tree | snapshot
parent757040c487343e81a4399bd7030e1ba881c2d141commit | diff
Extra features for multi-thread test script

Add: dynamic table names, rollback chance, max tables per commit, random seed

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