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
2019-03-20	Warm up ranges across sites	Tschaen, Brendan	1	-0/+6
2019-02-26	Improve serialization and table own	Enrique Saurez	1	-0/+6
2019-02-18	Use MariaDB libraries	Tschaen, Brendan	1	-7/+0
2019-02-07	Update sql parse interface	Tschaen, Brendan	1	-1/+1
2019-01-31	Switch to using mariadb connector	Tschaen, Brendan	1	-0/+7
2019-01-23	Fix node configuration/executable, and minor bugs	Enrique Saurez	1	-0/+38
2019-01-17	mdbc-server throws exception	Rob Daugherty	1	-0/+5
2018-12-20	Remove netty dependency pulled in by music library	Tschaen, Brendan	1	-0/+6
2018-11-30	Upgrade to MUSIC 3.2.1	Rob Daugherty	1	-1/+1
2018-11-19	Query processing with Calcite	Vikram Potturi	1	-0/+6
2018-11-14	Remove unwanted Trigger creation	st782s	1	-0/+5
2018-11-06	Self contain the unit tests	Tschaen, Brendan	1	-5/+0
2018-11-05	Change MDBC version, nexus repo property	Arthur Martella	1	-2/+2
2018-11-05	Modularized mdbc build	Rob Daugherty	1	-0/+198