@conference {2020:bac:iccs,
	title = {Microservice Disaster Crash Recovery: A Weak Global Referential Integrity Management},
	booktitle = {International Conference on Computational Science},
	year = {2020},
	month = {June},
	address = {Amsterdam, The Netherlands},
	abstract = {Microservices which use polyglot persistence (using multiple data storage techniques) cannot be recovered in a consistent state from backups taken independently. As a consequence, references across microservice boundaries may break after disaster recovery. 
In this paper, we give a weak global consistency definition for microservice architectures and present a recovery protocol which takes advantage of cached referenced data to reduce the amnesia interval for the recovered microservice, i.e., the time interval after the most recent backup, during which state changes may have been lost.},
	keywords = {BAC theorem, Microservices},
	author = {Maude Manouvrier and Cesare Pautasso and Marta Rukoz}
}
@article {2018:ieeecloud:bac,
	title = {Consistent Disaster Recovery for Microservices: the BAC Theorem},
	journal = {IEEE Cloud Computing},
	volume = {5},
	year = {2018},
	month = {January/February},
	pages = {49-59},
	abstract = {How do you back up a microservice? You dump its database. But how do you back up an entire application decomposed into microservices? In this article, we discuss the tradeoff between the availability and consistency of a microservice-based architecture when a backup of the entire application is being performed. We demonstrate that service designers have to select two out of three qualities: backup, availability, and/or consistency (BAC). Service designers must also consider how to deal with consequences such as broken links, orphan state, and missing state.},
	keywords = {availability, BAC theorem, consistency, disaster recovery, Microservices},
	doi = {10.1109/MCC.2018.011791714},
	url = {http://ieeexplore.ieee.org/document/8327550/},
	author = {Guy Pardon and Cesare Pautasso and Olaf Zimmermann}
}
