The architecture of Bizagi PaaS offers a series of technical features aimed at providing a highly secure, reliable, and scalable cloud platform, which at the same time, deliver a service that is optimized to run in the cloud.
Bizagi PaaS is cloud-centric and it makes the most out of modern technologies and services, including those that are not typically embraced by standard on-premises installations.
For introductory information about Bizagi PaaS, refer to Bizagi PaaS overview.
A service oriented architecture
Bizagi PaaS introduces a service oriented architecture, which from its very design, has been built for the cloud.
By implementing a highly-modular structure (principles from a service oriented architecture), Bizagi PaaS produces compatible and independently-deployable services which are easy to replace, while seizing and leveraging modern services which enhance security, reliability, and scalability.
This structure and architecture enables Bizagi to have a continuous delivery process that keeps up with the demands of software evolution.
Given that everything changes in the digital world with a significant pace, a service oriented architecture design, along with the implementation of agile development programs makes Bizagi PaaS a flexible service that quickly adapts to new business or IT requirements.
Service orientation has been proven to be an approach fit for the cloud, due to the flexibility inherent in loosely-coupled architecture.
Though powered by Azure and managed by Bizagi, Bizagi PaaS takes it one step further by building a Bizagi service layer on top of some of the Azure robust services being leveraged.
Bizagi PaaS architecture empowers a design, which:
•Optimizes the execution environment of your business applications.
•Complies with strict governance and security requirements.
•Has been built to support service interruptions and remain reliable (i.e, resiliency).
•Can dynamically scale up or down.
•Adheres to traditional Bizagi principles, such as offering: a consistent user experience across the different supported devices (e.g. mobile phones), experience design to empower knowledge workers, no coding required for your applications, among others.
The following diagram illustrates how end users around the globe access Bizagi PaaS, and make the most out of the architecture features oriented to performance, security, reliability and scalability:
Note that access from the internet is controlled by a traffic manager.
End-user access is routed by relying on the Work Portal CDN, and authorized by an Identity Manager service, which may integrate your corporate Identity and Access Management system.
Bizagi PaaS allows customers to access a reliable and available scale set that allows for the use of the Bizagi Engine, while also having both a network security group that filters access and a load balancer to distribute requests.
Bizagi PaaS storage takes into consideration the different ways in which different types of information, such as transactional data, documents, logs, and archives should be optimally treated.
On a closer look, the following image represents resources inside of Bizagi PaaS architecture:
A description of the components and services of Bizagi PaaS architecture is listed below:
•Work Portal CDN: Offers high performance by delivering static content from the nearest geographical location to the end user.
•Bizagi Scheduler Dispatcher: Runs scheduled jobs and tasks.
•Identity Manager: Grants secure sign-in to your end users while supporting authentication against an integrated Identity provider.
•Traffic Manager: Provides global access to Bizagi PaaS via HTTPS protocol.
•Virtual network: Provides secure communication between services, while implementing isolation measures.
•Network security group: Implements ACLs (additional security rules) for Bizagi PaaS access and communications.
•Load Balancer: Enhances service reliability by distributing requests according to processing capacity.
•Scale set: Enables the dynamic assignation of an additional set of resources, in order to support a highly scalable service.
•Cache: Optimizes access to Bizagi metadata.
•Server: Runs instances of Bizagi Engine while implementing a high-availability model.
•Process store: Stores transactional data while supporting high concurrency and reliability.
•Logs: Stores logs regarding Bizagi Engine operations.
•Document storage: Optimizes storage for attached files and documents.
•Archiving storage: Stores data of closed cases that are not queried on a daily basis.
•Async Messages: Uses queues for synchronization purposes.
Bizagi PaaS offers a virtual, private cloud that grants each customer access to an isolated environment and the ability to choose appropriate levels of performance to match demand, where the customer data and resources are not shared.
Having separate resources, along with data isolation, allows for a more predictable performance behavior and a base for strict compliance in terms of data privacy and best governance and security practices.