Edge synchronizer
Edge Synchronizer Client
We all know that the ability to sell in a physical store is the most important thing, and disruptions to internet connection can be devastating if required to perform a sale. If not corrected it can be a very costly exercise for the individual stores and the retailer.
Edge Computing is a new term for something that has existed in retail for a long time.
A "store server" of some sort has been quite common for years, and the Hii Retail Edge Synchronizer client is a Hii Retail specific library that can be used to enable Cloud to Edge data synchronization of certain master data entities.
The client library can be used in an existing application that runs on an in-store computer with the proper specifications.
This means it can run on a server, POS machine or any other computer capable of handling the load for that particular Business Unit. In addition, we can offer a dedicated Edge Computing solution, which simplifies the deployment and maintenance of such edge services.
The client library will synchronize with the Cloud and transfer delta changes in near real-time.
When the data is transferred it will be stored in a local document database and an event will be fired to trigger any custom handling of the data.
This allows us to support offline scenarios and/or failover transaction processing.
Stores can be set up to have local or cloud as primary endpoints, and failover to the other if needed.
Having the local server will of course also allow edge to be the primary, so that offline scenarios will not be noticed by the individual POSes.
Example implementation - existing transformation service
The Edge Synchronizer Client can be embedded into a new or an existing Edge transformation service running on qualified in-store hardware.
Contact Extenda Retail if this is a viable option for you. We must assess your existing environment before committing to an implementation like this.
The Edge Synchronizer Client will synchronize with Hii Retail Cloud automatically, and reactively. This means it will react to changes and download the delta-changes in near real-time to the local service.
The information will be saved into a local database at the same time as an event is emitted for the implementing service to respond to the downloaded data.
This data will require to be transformed into whatever local format is supported by the existing legacy system.
The transformation service will also need to maintain any relationship requirements or validations before the data can be used in the legacy system.
Example implementation - Avassa Edge Computing
Avassa is Extenda Retails provider of Edge Computing devices.
With this implementation the Edge device is set up to allow deployments from Hii Retail Cloud. This allows the services to be updated according to Hii Retail deployment frequencies.
It also allows the physical stores to have failover to or from Cloud, depending on what is the primary endpoint.