- HTML5 user interface
- Content preview
- Multitenant & Multi-user
- Native, proprietary
- Multi-layer, multi-threading
- Android, Windows & Tizen
- Reliable 24x7
- Host your own server
- SDK - API
QL Server requirements depends on the number of concurrent player downloads your platform is expected to handle. The configuration profiles are measured based on Microsoft Azure offering. It can be used to make your hardware configuration for on premise hosting or third party web hosting vendors such as Amazon or Rackspace.
MIDDLE TO LARGE SCALE DEPLOYMENTS HOSTED BY OWNER ON MICROSOFT AZURE:
|Basic Shared Folder||CDN /Azure BLOB|
|Number of IIS Servers Azure A4 Equivalent||1 server A3||2 servers A4||3 servers A4|
|Number of players downloading concurrently||350||1500||3250|
|Operating System||Windows server 2012||Windows server 2012||Windows server 2012|
|SQL Server Azure hosted||S2||P2||P2|
Using QL Server in a load balancing architecture requires that each server has access to a shared virtual drive compliant with SMB-3 protocol. Optionally, a BLOB (Microsoft Azure) can be used in order to offload the IIS server content download and to provide a drive redundancy.
SQL Server Azure S2 supports 50 DTU. P2 supports 250 DTU – SSD
SMALL DEPLOYMENTS HOSTED ON PREMISE:
|Number of hosted players||1-60 players||61-120 players||121- 250 players||251-500 players|
|Operating System||Windows Server 2012||Windows Server 2012||Windows Server 2012||Windows Server 2012|
|SQL server 2008+ Edition||Express||Standard||Standard||Standard|
|Hard Drive||HD – SSD||SSD||SSD||SSD|
QL Server host PC will be running both Microsoft IIS and SQL Server (versions 2008, 2012, 2014).
Note: The number of players downloading concurrently means that your QL Server may host up to 5 times more players. Player beyond this value will be queued and delivered as soon as the first players would have completed their download.