LS Central offers multiple deployment options to cater to different customer needs. These options include:
LS Central SaaS (Software as a Service)
LS Central SaaS is hosted in the Microsoft Dynamics 365 cloud and provided as a Software as a Service solution. It encompasses the full functionality of Dynamics 365 Business Central along with the base functionality of LS Central, including features for hospitality and member management. LS Central SaaS is accessible through the LS Retail Portal, and specific information regarding country availability can be found there.
Within LS Central SaaS, you have two deployment options:
-
Online POS: This option enables running the POS devices online, leveraging the stable internet connection and real-time data synchronization with the cloud.
-
Hybrid POS: With the hybrid deployment, you can combine both online and offline (stand-alone) POS devices, providing flexibility and the ability to operate even when the internet connection is unavailable. You can choose the optimal deployment option based on customer requirements, transaction volume, internet stability, and other factors.
To understand the pros and cons of different deployment options, you can refer to the Choose the Right Deployment Option resource. For more insight into LS Central SaaS architecture, the LS Central SaaS Architecture documentation provides detailed information.
To learn more about LS Central SaaS, visit the LS Central SaaS page.
On-premises
LS Central can be deployed on-premises or in a private cloud environment. In the on-premises deployment, the system can be hosted either in a dedicated server hardware on-site or in a Virtual Machine (VM) hosted in Azure/AWS or other private cloud environments. Multiple VMs can be hosted if the server hardware has sufficient resources. You have the flexibility to choose in-store deployment if you wish to run online POS devices, stand-alone (offline) POS, or a combination of both.
In this context, the server is typically a Virtual Machine (VM) hosted on dedicated server hardware either on-premises or in Azure/AWS. If the hardware has sufficient resources, it can host multiple VMs.
During the setup process, it is crucial to allocate virtual hardware resources (such as vCores) according to the capabilities of the physical server. It is important not to assign more virtual resources than the server can handle.
While having multiple services on the same VM does not significantly impact performance, sharing the same resource pool can have implications. However, if the VM is larger and adequately equipped with hardware resources, this concern can be mitigated.
The terms "Small," "Medium," and "Large" are used for differentiation purposes, providing options based on the deployment scale and resource requirements.