Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: dd2937c 999f808)
Merge "Include primary key in insert query"
authorBharath Balasubramanian <bharathb@research.att.com>
Thu, 28 Mar 2019 13:12:38 +0000 (13:12 +0000)
committerGerrit Code Review <gerrit@onap.org>
Thu, 28 Mar 2019 13:12:38 +0000 (13:12 +0000)
commit9715bb302ae309810fe533ad024cafe87e5480dd
treefec250275e2d7c51f81b356edd5e2b5fc6ae6585tree | snapshot
parentdd2937cafd226068dbe518d0b706dc4e6fd164eecommit | diff
parent999f808ea68eeeacf7af36f44a0fea8f9fe6ed88commit | diff
Merge "Include primary key in insert query"
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MySQLMixin.java diff1 | diff2 | 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.