Database Reference
In-Depth Information
Here's what a potential polyglot persistence architecture could look like for a
hypothetical, or speculative, retailer:
An example of polyglot persistence
In the
Speculative Retailer's Web Application
featuredintheprecedingigure,
there may be different use cases that rely on different data patterns, and that
would be best implemented in different data stores.
The consequence of a strategy like polyglot persistence is, of course, that you introduce
theimmediateandsigniicantneedfordataintegration.DifferentDataIntegration
strategies are of course conceivable, but at least one of these will rely on third-party
tooling to read from and write to the Neo4j Graph Database Management System.
Therefore, we would like to introduce two examples of tools like these and discuss
their characteristics and potential use cases.
