architecture

  • JumpMind presents on ORPOS Centralization

    The demands of Abercrombie & Fitch’s international expansion goals required new store systems and infrastructure. After selecting Oracle Retail Point-of-Sale (POS) as their new POS platform, A&F sought to eliminate the requirement for a store server in order to reduce per store hardware requirements, centralize infrastructure management and further harden offline capabilities. Abercrombie will be sharing the challenges and solutions for the migration from a store centered client/server architecture to a centralized model that supports a multi-brand, global retail chain.

     

    Follow along in the presentation on Oracle POS Centralization for more details.

  • SymmetricDS: Behind the Scenes

    We have received many inquiries about the architecture of SymmetricDS lately.  I think the user’s guide does a nice job of laying out how to implement and configure SymmetricDS, but we have noticed (after taking a step back) that it doesn’t provide a concise, technical overview.   You can probably piece everything together from the guide, but it is probably worth some effort to describe how SymmetricDS works under the covers.  We’ll be updating the documentation with this information in the near future.

  • Three Tier Replication Done in Two Tiers

    One of the most common replication patterns we see here at JumpMind is a three tier setup with a central, regional, and site group.  Retailers commonly use this approach with groups named: corp, store, and register.   However we often see setups that try to reduce this approach down to two tiers with a similar set of functionality.  Deciding between a two or three tier approach can be tricky and each may have advantages and disadvantages based on your needs.  This article will help to explain these differences and hopefully help in making the best design choice for your needs.