The infrastructure that registers and distributes Crossref metadata has been running and growing for more than two decades. It now does considerably more than it was built to do, and it shows: two large, tightly coupled monoliths (Content System and REST API), where a change in one place risks breaking something in another.
This is a companion discussion topic for the original entry at https://0-www-crossref-org.oasis.unisa.ac.za/blog/investing-4.9-million-of-our-surplus-in-rebuilding-the-crossref-system/
Thank you very much for this helpful information.
But can you please provide us with more information concerning data servers, backups and their security. We know, that Crossref uses AWS, at least we had some hours of disfunction when you migrated to/or bigger servers. As we recently viewed from news, one of AWS servers in Saudi Arabia was completely destroyed. So what are your plans to minimize these kind of risks and etc? Thanks you very much 
1 Like
Hi @thetan,
Currently the system runs in AWS (US regions). As part of an ongoing infrastructure resilience review, we are building in redundancy through a cloud-based disaster recovery environment outside of the US. We are designing a geographically separate infrastructure in the EU, with copies of data, applications, and operational procedures, to support a timely restoration of services following a major outage. Additionally, we are establishing copies of our data and code at an alternative cloud provider other than AWS and outside of the US.
4 Likes
Hi Dominika, thank you very much. I don’t really see that you really know what the “disaster” is.
Thank you very much for your answer.