Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 24f854d) | patch
Sequential IDs and firstnames for multi-thread test script 91/91291/1
authorArthur Martella <arthur.martella.1@att.com>
Thu, 11 Jul 2019 20:02:22 +0000 (16:02 -0400)
committerArthur Martella <arthur.martella.1@att.com>
Thu, 11 Jul 2019 20:02:22 +0000 (16:02 -0400)
commitef6c1fdb836b7ecb79d9ff1cd29b7c5debe1a7f8
treed9c4602a944b468df1161cb6eeee9001211e5826tree | snapshot
parent24f854ddde6164f18ec2c7b6223befe83c583181commit | diff
Sequential IDs and firstnames for multi-thread test script

Issue-ID: MUSIC-420
Signed-off-by: Martella, Arthur <arthur.martella.1@att.com>
Change-Id: I484d4d20699458522a81985908c94e4b1d652248
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.