Activiti & Activiti Cloud Developers Guide
  • Introduction
  • Overview
    • 12 Factor Apps
    • Personas
    • Previous Versions (5.x & 6.x)
    • References
    • Cloud Native BPMN support
    • BPMN Comformance
      • BPMN Comformance Set 0
      • BPMN Comformance Set 1
      • BPMN Comformance Set 2
      • BPMN Comformance Set 3
      • BPMN Comformance Set 4
      • BPMN Comformance Set 5
      • BPMN Comformance Set 6
  • Getting Started
    • Getting Started - Activiti Cloud
      • Amazon EKS
      • Google Cloud GKE
      • Docker Compose
      • Jenkins X
        • Amazon EKS
        • Google GKE
    • Getting Started - Activiti Core
  • Components
    • Spring Cloud
    • Activiti Cloud Infrastructure
      • Gateway
      • Identity Management / Single Sign On
    • Activiti Cloud Application
      • Activiti Cloud Runtime Bundle
      • Activiti Cloud Connectors
      • Activiti Cloud Query Service
      • Activiti Cloud Audit Service
      • Activiti Cloud Notification Service
  • FAQs
    • Activiti Core FAQs
    • Activiti Cloud FAQs
  • BluePrints
    • Trending Topic Campaigns
  • Community
    • Roadmap
    • Repositories
    • Contributing
  • Releases
    • 8.2.0
    • 8.1.0
    • 8.0.0
    • 7.11.0
    • 7.10.0
    • 7.9.0
    • 7.8.0
    • 7.7.0
    • 7.6.0
    • 7.5.0
    • 7.4.0
    • 7.3.0
    • 7.2.0
    • 7.1.0-M17
    • 7.1.0-M16
    • 7.1.0-M15
    • 7.1.0-M14
    • 7.1.0-M13
    • 7.1.0-M12
    • 7.1.0-M11
    • 7.1.0-M10
    • 7.1.0-M9
    • 7.1.0-M8
    • 7.1.0-M7
    • 7.1.0.M6
    • 7.1.0 M5
    • 7.1.0 M4
    • 7.1.0 M3
    • 7.1.0 M2
    • 7.1.0 M1
    • 7.0.0 SR1
    • 7.0.0 GA
    • 7.0.0 RC1
    • 7.0.0 Beta5
    • 7.0.0 Beta4
    • 7.0.0 Beta3
    • 7.0.0 Beta2
    • 7.0.0 Beta1
    • 7.0.0 Early Access 201802
    • 7.0.0 Early Access 201801
    • 7.0.0 Early Access 201712
    • 7.0.0 Early Access 201711
    • 7.0.0 Early Access 201710
    • 7.0.0 Early Access 201709
Powered by GitBook
On this page
  • Activiti Cloud Developers
  • Activiti Cloud DevOps
  • Tooling and integrations
  1. Overview

Personas

Previous12 Factor AppsNextPrevious Versions (5.x & 6.x)

Last updated 1 year ago

It is important to understand which personas we are targeting with our different set of tools. For that reason, the following chart shows the main Personas that we will target and which features they will be using to perform their work.

Activiti Cloud will first target Activiti Developers & Activiti DevOps which are in charge of setting up the infrastructure and making sure that Activiti Applications can be deployed to a cloud provider.

Activiti Cloud Developers

Activiti Cloud Developers are responsible for building System to System connectors which will serve as integration points with existing internal/external systems. The Process Engine (inside our Runtime Bundles) will have no knowledge about these connectors and the integration will happen via Events. These Cloud Connectors will be discovered at runtime and they will use the infrastructure to provide failover and fallback mechanisms. Developers will be in charge of testing these connectors, packaging and releasing them (Maven/Docker). Developers are also in charge of testing business process definitions in addition to the required connectors. After testing, Developers will be in charge of releasing these Runtime Bundles and Connectors.

Activiti Cloud DevOps

Activiti Cloud DevOps are responsible for picking up released Runtime Bundles and Cloud Connectors and deploying them into an instance of our infrastructure. DevOps will only have access to and be able to pick up released versions which Developers have tested and released to a specific repository (Maven/Docker).

Tooling and integrations

For both Developers and DevOps personas, the Activiti Cloud team is always looking for tools to simplify their daily work. We have found the following tools to be extremely useful:

: CI/CD done right for Kubernetes

: Spring Cloud and Angular/React generators

: Kubernetes Package Manager, we use it for doing deployments of Activiti Cloud applications in K8s.

: we use it to avoid duplication/overlap with the infrastructure

: Service Mesh on top of K8s

: Function as a Service layer on top of K8s

Jenkins X
JHipster
HELM
Spring Cloud Kubernetes
Istio
KNative