Home/ Questions/Q 9012665
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-16T03:03:43+00:00

So here is the basic structure I’m proposing: Data warehouse (for want of a

  • 0

So here is the basic structure I’m proposing:

Data warehouse (for want of a better word)

  • E-commerce online
  • Back-end MIS
  • etc

So the idea is that I have an Order for example. An order can be created via e-commerce site, or via back-end MIS. Either case the order should filter out to e-commerce to show order to user, and vise versa.

There will be other apps in the future.

So the thinking is, to have a central warehouse that wraps this data in a service API, and then the other apps push / pull to it.

Sound OK? I guess the question is syncing the data. When I create an order, do I push the order at create time to the warehouse, or put it to some queue, or is there some other method to keep all these in sync, assuming, near realtime to realtime sync is required.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Assume your REST server is just another data store. How would each client get updates from a plain old database when needed?

    If you had each client poll the data store at regular intervals, that would be one solution.

    • 0