Abstract
This paper elucidates electronic invoice system’s database architecture requirements and its building issues that one may encounter. Enumerated requirements and issues were taken into consideration and it is suggested to use three types of DB in the system. NoSQL model of database for its numbers of advantages is recommended for the information reused by users to store and querying them. The database is able to split database loadequally with the help of horizontal sharding. Making partition numbers equal to the number which has common divisors as much as possible will let splitting load amount equally among possible additional infrastructure. A special approach is required to each element of system to perfectly create architecture of the information system's database.
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.
