Summary
In this chapter, we explored how we can evolve a graph database in two ways: changing design wherever necessary and adding more varied data.
Adding more varied data should always be for business reasons. Re-design of data might be done for optimizations or could be driven by business reasons. Either of the evolutions are simple to carry out in graph databases like Neo4j, and if planned properly, there is no outage required.
In the next chapter, we will learn about modeling communication chains.
Get Neo4j Graph Data Modeling now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
