Design Context

Graph Database is made up of many interactive software systems which collectively present a complex structure of components. In order to clearly envision the overall blueprint of the system, multiple views or the overall system are needed. These views can be classified as infrastructure architecture and application architecture. The below gives an overview of those views classified:

Application Architecture, as demonstrated above, it provides the view of how various modules of Graph Database work together to support the different types of users. These modules and components are categorized as:
• Front-end User Interface (e.g. Graph Database GUI Console)
• Application-level Communication Protocol (RESTFUL or SOAP services)
• Core Application (e.g. Graph Database Core Engine)
• Back-end data storage (e.g. MongoDB, SQL Server)

Infrastructure Architecture, as above, it provides a view of how the hardware and network topology supports the Graph Database systems. This includes:
• How and where the server profiles required by the technical architecture are deployed
• How the hardware sizing, network clustering, and virtualization strategy help support non-functional requirements such as performance and availability.