While we are working hard in getting our first Beta Release at the end of March (beginning of April) we wanted to share a couple of introductory videos about our work so far.
We have introduced some new concepts to align BPM concepts to the Cloud Native era and for that reason we wanted to share some examples of these concepts in action.
The first video go over some of the changes in paradigm that we adopted while creating Activiti Cloud and the technology choices that we made in order to provide solutions that can scale up to support global scenarios.
Then it covers the main building blocks in Activiti Cloud covering our Infrastructural Services such as Identity Management, SSO, Services Registry, Configuration Server, Data Stores and Message Brokers and our Core Building Blocks such as Runtime Bundle, Query Service, Notification Service, Audit Service and Cloud Connectors
While all these concepts are important to understand see them in action is way more valuable.
The second video covers our BluePrint: Trending Topic Campaigns Scenario (Source Code and GitBook Section) where we aim to share a running example that shows most of our building blocks solving a real life situation that requires great amount of flexibility and dynamic scale. We will use these BluePrints to test our releases and to iteratively improve each of the building blocks. One key aspect of this BluePrint is that is designed with Kubernetes in mind as the main target deployment platform. This is an important aspect that highlight the intention of this fictional scenario. We are not building BluePrints as just cool demos, we want to make sure that these scenarios represent generic scenarios that you as implementor will face when using our building blocks. We use these scenarios to recognise pain points so we can fix them and improve the overall experience of using these Cloud Native services. As you will see in the video, the BluePrint app can be started as a set of Spring Boot apps, using Docker Compose or straight into Kubernetes where the first two are only recommended for development purposes, but if you are really thinking into going into production running in Kubernetes is a must. The BluePrint scenario is a great place to experiment performance, load and how, with different configurations, the topology of the services can behave differently to cover different scenarios.
It is also important to notice that even if this BluePrint was built using Activiti Cloud you can use it to learn about Cloud and distributed architectures mainly because each Building Block is autonomous and packaged as a container, you can kill Runtime Bundles (campaigns), create replicas (to support more load) or even add new Campaigns dynamically and the whole system should adapt and the cluster will do its magic to make sure that each service has enough resources to operate correctly.