For small businesses limited by budgetary constraints and few resources to allocate towards maintaining and improving their infrastructure, VIDIZMO offers a deployment architecture using the following configuration:

Application, Content Provider and Encoder

All of the media types are associated with some content providers. Using a local CDN, VIDIZMO will store, encode and serve the content to the end users. In some cases, for instance, document or image might not need the same storage or encoding provider as that of audio and video files since a user might require different renditions of audio and video files. Therefore, the content providers are selected according to the media file being uploaded.


By default, VIDIZMO uses Microsoft Azure as its primary content provider for SaaS models but for On-Premise deployments, VIDIZMO can be configured as the content provider. 


In this configuration, VIDIZMO Application, the Content Provider, and the Encoder are all installed on the same dedicated server.

Streaming Server

VIDIZMO integrates seamlessly with other leading video streaming servers for live and on-demand video streaming. In the deployment scenario below, Wowza is used as the Streaming Engine and uses its functionality to serve VOD content for large-scale deployment. Wowza utilizes Media Cache where the Origin is a Web Server or a Network Share since Wowza Streaming Engine does not use its own storage.

VIDIZMO application, combined with the VIDIZMO ECDN module, has a pre-configured option to use Wowza as the streaming server, allowing users to simply select Wowza as the Origin Server. Using VIDIZMO's On-Premise encoding and Wowza's Streaming Engine to stream your media helps you to leverage the power of a locally installed infrastructure to economically deliver compatible media to mobile devices and computer screens alike.

For more details on how Wowza can be configured, click here on How To Setup Wowza Cloud Streaming Server for Live Streaming.


VIDIZMO recommends deploying the Application and the Database Server on separate machines mainly because of the factors related to security and performance. Installing the database server on a separate machine allows the application to utilize available resources for optimum performance as opposed to the shared database which is prone to resource consumption as the database grows. 


Network Storage

When setting up a Streaming Server in VIDIZMO, content storage location needs to be defined which can either be a local drive or a network location. VIDIZMO recommends using any fast and secure Network Storage (SAN/NAS) which can be mapped to a drive for VIDIZMO to store content. Network Storage is an efficient way to manage storage, disaster recovery, and availability.


Single Sign-On (SSO)

This is the customer's Identity Provider which integrates with the VIDIZMO's Web component.

VIDIZMO supports industry standard implementations of SSO that works with widely used Corporate Authentication services such as Directory and Federation Services, Identity and Access Management (IAM) solutions, as well as 3rd Party Login services using industry standard protocols as outlined below. Note that using these options only enables federated login (Authentication) with your VIDIZMO Portal, while Authorization is still handled in VIDIZMO Application. 

To learn more about SSO click here on Understanding Single Sign-On (SSO) Options.

To learn more about the installation of individual VIDIZMO components, click on the links below: