music/mdbc - 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.

Age	Commit message (Expand)	Author	Files	Lines
2018-11-20	MusicSqlManager Removal, othe code refactors	Tschaen, Brendan	21	-2106/+1636
2018-11-20	Merge "TxDigest replay and code restructure"	Bharath Balasubramanian	31	-1147/+810
2018-11-19	Query processing with Calcite	Vikram Potturi	47	-0/+282
2018-11-16	TxDigest replay and code restructure	Tschaen, Brendan	31	-1147/+810
2018-11-14	Remove unwanted Trigger creation	st782s	7	-12/+23
2018-11-06	Self contain the unit tests	Tschaen, Brendan	7	-452/+49
2018-11-05	Modularized mdbc build	Rob Daugherty	81	-0/+15048