Abstract
This work describes main concepts of architecture style and technologies selection for building distributed e-Archive system. The paper presents overall concepts, vocabulary, data models, responsibilities that an electronic archive system must fulfill, and a set of recommended functions to cover these responsibilities. The article describes the main information flows and functions. It outlines the theory of the OAIS model, illustrates an example of complex microservices architecture design and approaches to solve data consistency and application deployment challenges. The comparative analysis of software architecture styles was performed and, as result, the combination of Microservice and Event-Driven architectures was chosen as the most suitable architecture for building electronic archive system. It implies having microservices that communicate with each other via some message bus instead of direct calls. The technology stack chosen for that architecture implementation and application delivery is proven to be production-ready, has detailed documentation and large community support. The technology stack is Asp .Net Core 2.1 – framework, Rabbit MQ, Apache Tika, Elasticsearch, Mongo DB, MS SQL Server, Azure Blob Storage, Event Store, Signal R, Docker, Kubernetes.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
