Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • You can also: 4. Cache the data in each API. That way, you will only have one point of data duplication, your responses can be quick and the best thing: you will have control over the cache. In the first option, if a catalog item has been removed, you will continue to process orders with that catalog item. But if the service catalog has control over the cache, it can delete the cache for that item when it is removed. Commented Apr 11, 2020 at 3:23
  • Thanks Gabriel - if I understand correctly, your suggestion would entail my entire persistent storage being cached? My choice of words perhaps wasn't great - wherever I said 'cache' I was referring to persistent storage of duplicated data. I'm focusing less on performance optimisation and more on design patterns for accessing data owned by another service. Commented Apr 11, 2020 at 20:49