Bizagi Studio Collaboration Services architecture includes a set of technical components to assure a secure, reliable, and scalable service. Our cloud-based technologies and services offer modern features that will let your cloud development environment satisfy your requirements.
A service-oriented architecture
Bizagi Studio Collaboration Services introduces a service-oriented architecture, which was designed and built for the cloud. By implementing a highly-modular structure (based on a service-oriented architecture),Studio Collaboration Services produces compatible and independently-deployed services which are easy to update, while leveraging modern services which enhance security, reliability, and scalability. This structure and architecture enable Bizagi's continuous delivery process that keeps up with the demands of software evolution.
Given that everything changes in the digital world at a significant pace, a service-oriented architecture design, along with implementation of agile development programmers, makes Studio Collaboration Services a flexible service that quickly adapts to new business or IT requirements. Service orientation is an approach fit for the cloud due to the flexibility inherent in loosely-coupled architecture.
Though powered by Azure (as its Infrastructure As A Service provider) and managed by Bizagi,Studio Collaboration Services takes it one step further by building a Bizagi service layer on top of some of the robust Azure services we are leveraging.
Applications each co-developer uses
Users of Bizagi Studio Collaboration Services have access to the following applications:
•Bizagi Studio: a desktop application that gives you access to projects of your development environment.
•Work Portal: The development environment, as a web-based application. You have as many development environments (cloud-based Work Portals) as the number of Studio Collaboration Services packages with environments you have acquired, Refer to Bizagi Studio Collaboration Services subscription. If you run the Work Portal locally, you need to install all the development environment resources. Refer to Running a project.
•Management Console Web: Web-based application where the environment administrator controls environment configuration parameters. Refer to Management Console Web.
•Customer Portal: centralized web app that allows to manage users of all the services acquired from the Bizagi Cloud Platform (Automation Service, Studio Collaboration Services, Modeler Services, Business Insights and Artificial Intelligence). Refer to Customer Portal.
Behind these applications, there are different web-based components that are described in Bizagi Studio Collaboration Services' architecture.
The modularity of the architecture is based on web applications independent modules. Each web app includes middle-ware systems such as interfaces or databases that process information based on the purpose of the web app. Isolation of each web app from others, reduces the load on the whole system, which prioritizes requests based on their destination. For example, Studio Collaboration Services manages synchronization of data between co-developers through a different path than integrations with external systems. This architecture also permits robust controls and administration on each module.
BizagiStudio Collaboration Services architecture empowers a design which:
•Optimizes the development of intelligent process automation with geographically distributed teams working collaboratively.
•Complies with strict governance and security requirements.
•Is built to handle service interruptions and remain reliable (resiliency).
The following diagram illustrates how end users around the globe access Studio Collaboration Services, and make the most out of features oriented to performance, security, reliability, and scalability:
Studio Collaboration Services offers a virtual private cloud that grants each customer team access to an isolated environment where the data and resources are not shared beyond those with access to a dedicated Customer subscription. Having separated resources, along with data isolation, allows for more predictable performance and gives a base for strict compliance in terms of data privacy, best governance and security practices.
Here are descriptions of each module depicted in the diagram:
Bizagi cloud operations teams manage the following modules, You and your team do not have to administer any of them, freeing you to focus on your business development through intelligent process automation as each co-developer uses shared applications. This reduces your management efforts and costs.
DNS: Resolves the service’s URL.
Traffic manager: Routes requests to the customer's subscription, while considering availability of the service.
Security layer: A logical tier, filters requests and protects access, while having:
oNext generation firewall: Offers IDS, IPS, antimalware, along with preventing leaks and protecting the ports.
oApplication gateway (includes a WAF): Offering extra security at the web application level (that prevents sql injection, cross-site scripting attacks or other treats), while routing requests to the target environment and its authorized endpoint (performing as well load balancing).
Studio Services: Web app that controls access to the customer subscription. Through this module, metadata between the Bizagi Studio instance of co-developer moves to the cloud metadata catalog, which holds metadata for all projects stored in yourStudio Collaboration Services.
Customer Portal: Web app that allows to manage users of all the services acquired from the Bizagi Cloud Platform.
Platform: Controls access to Bizagi’s platform resources, for example, users in the subscription or available environments.
Accounts: Authenticates users added to the customer subscription, and validates users included within each project of a subscription.
Catalog: Metadata repository of all your Studio Collaboration Services projects.This module is responsible for synchronizing metadata. Refer to this link for further information.
Deployment: This module synchronizes metadata between users and the catalog, opening a maintenance window when metadata changes affect components in a way that require a restart of the Work Portal or the Scheduler. Refer to this link for further information.
Scheduler: A web app executing all programmed jobs. Refer to programmed jobs.
Work Portal: This module contains all the Work Portal’s computing resources for one development environment.
Management console web: This module controls and manages all development environment parameters. Refer to Management console web
Connector: Web application for invoking Bizagi connectors.
Storage layer: A logical tier that holds the storage services which process applications rely on. This tier holds
-Database (a relational, SQL database for process applications definitions and business data) and the
-Table storage service (holding logs), and encrypts data at rest.
-Blob storage: storage for all the files uploaded in Bizagi through the Work Portal.
SMTP services: Bizagi Studio Collaboration Services offers a service to send all notifications tested in your development environment. This module is configured for all the environments of your subscription.
Email integration: Email inbox available for configuring tasks to be completed via Email.
A Bizagi security center monitors security across all components so that incoming and outgoing network traffic is strictly controlled (traffic is also encrypted).
Bizagi Cloud Operations team monitors security 7x24 such aspects, along with receiving alerts about potentially malicious traffic.