• Steve Jones - SSC Editor (11/30/2015)


    Gary Varga (11/30/2015)


    Eric M Russell (11/30/2015)


    ...For example, a shopping cart for an ecommerce website is not the same thing as a purchase order for accounting, and only when the customer actually enters their credit card information and clicks the submit button does it become a set of golden records worth managing permanently...

    In the example when saving an actual order it doesn't have to be to a database. This could be implemented using transaction message queues thus further decoupling the back office from the online presence to ensure that both systems can remain performant without disturbing each other.

    Amazon appears to do this. The orders don't go into a live db, or the same db I query as an "order" in real time. There are delays at times. Usually seconds/minutes, but delays, yet AMZN seems to manage that well.

    This is true. I have read an Amazon white paper (a LONG time ago) and all I can recall was that they had a RDBMS at the back end and a different technology initially storing the orders. I think, but I may be recalling incorrectly, that they used a third technology for the basket - which I think was a NoSQL database (although it was not referred to as that).

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!