Frequently Asked Questions
-
Does there need to be a separate application server and database server?
While VIDIZMO works fine with a single machine scenario, we recommend a separate app, DB server and encoder for the most optimum performance.
-
How many production databases are required by your system?
VIDIZMO requires four production databases. -
What database platforms does your system support (include versions)?
MS SQL 2016/2017 and onwards -- Standard or Enterprise Edition is provided depending on business needs
-
Indicate the number and frequency of release updates to the software over the last three years.
Historically, we've had 2 major releases per year with 3-4 minor releases per year. The current version is 6.5.4.
Read more: Release Notes.
-
Can your video system be deployed to multiple production servers and load balanced?
Yes. Additionally, scaling up and scaling out options are also are supported. Various VIDIZMO software services may also be distributed over several servers for virtually unlimited scalability. -
Is a separate reporting server usually used for generating reports?
Reports and database servers are normally going to reside on the same server. A separate reporting server may be used for reports. However, it is not required.
-
Can user directly connect to the database and query it?
Yes, but that option is only supported when VIDIZMO is deployed in private cloud or within corporate network. Shared VIDIZMO instance does not allow querying database. However, access through separate reporting server is recommended. -
What is the infrastructure of the system for redundancy and backups in VIDIZMO?
VIDIZMO has an uptime of 99.5%. However, to avoid unscheduled downtimes, high availability databases are used. These databases are configured in such a way that single points of failure are eliminated and the databases are optimized to ensure that the end-user does not experience an interruption in service or degradation in user experience when hardware or networks fail. As compared to a relational database, High Availability database architecture design is generally easy, less complex, and ensures high availability in a multiple node and cluster environment. Based on a masterless architecture that uses clustering, with multiple servers grouped together, any server within a cluster can respond to read or write requests. Data replication is achieved across all servers in the cluster to provide system redundancy and to minimize downtime possibility. If required, VIDIZMO can offer a high availability architecture to manage the workload as well as provide redundancy.