Creating Reference Architecture blueprints for self-managed Camunda 8 standardizes deployment and integrates best practices, enhancing security and scalability. It expedites onboarding, reduces implementation costs, and ensures consistency across projects. Blueprints mitigate risks, streamline integration, allow for strategic customizations, and facilitate compliance with European regulations.
The new C8 architecture introduces simplified deployments using a single JAR package on IaaS without an additional orchestration layer, which will suit several use cases for running C8 in Production.
User Problem
While k8s offers a consistent approach to managing applications across different infrastructures, it requires an advanced knowledge of the Cloud-native landscape. Our customers still run older infrastructure stacks, which prevent them from running C8.
There is no clear explanation of how to deploy C8 in pure AWS IaaS.
Release Notes
User Stories
As an IT Admin, I can get a clear deployment blueprint that defines C8 deployment in Production.
As an IT Admin, I can get clear requirements to operate C8 in Production: backup, restore process, troubleshooting, logging, monitoring, failure recovery, HA.
Implementation Notes
We need to Define the Basic production configuration - similar in performance to the SaaS Small cluster.
Our blueprint will contain requirements for infrastructure and its configuration with examples in CLI and\/or Terraform.
Scaling cluster it out of scope.
Do we will use existing services for ES (OpenSearch) and SQL (postgressql)
How do we configure connectivity?
We will find an easy way to explain how to connect to the cluster. We will work on the assumption that the customer will connect to C8 cluster via a private network.
Monitoring and Logging: We will use AWS CloudWatch
We need to include an option for simple\/small production cluster option. (Consider line of business tools) Users must be able to pick which configuration options they woud like to use and exclude more advnaced topics like keystore
Value Proposition Statement
Creating Reference Architecture blueprints for self-managed Camunda 8 standardizes deployment and integrates best practices, enhancing security and scalability. It expedites onboarding, reduces implementation costs, and ensures consistency across projects. Blueprints mitigate risks, streamline integration, allow for strategic customizations, and facilitate compliance with European regulations.
The new C8 architecture introduces simplified deployments using a single JAR package on IaaS without an additional orchestration layer, which will suit several use cases for running C8 in Production.
User Problem
While k8s offers a consistent approach to managing applications across different infrastructures, it requires an advanced knowledge of the Cloud-native landscape. Our customers still run older infrastructure stacks, which prevent them from running C8.
There is no clear explanation of how to deploy C8 in pure AWS IaaS.
Release Notes
User Stories
As an IT Admin, I can get a clear deployment blueprint that defines C8 deployment in Production.
As an IT Admin, I can get clear requirements to operate C8 in Production: backup, restore process, troubleshooting, logging, monitoring, failure recovery, HA.
Implementation Notes
We need to Define the Basic production configuration - similar in performance to the SaaS Small cluster.
Our blueprint will contain requirements for infrastructure and its configuration with examples in CLI and\/or Terraform.
Scaling cluster it out of scope.
Do we will use existing services for ES (OpenSearch) and SQL (postgressql)
How do we configure connectivity?
Monitoring and Logging: We will use AWS CloudWatch
We need to include an option for simple\/small production cluster option. (Consider line of business tools) Users must be able to pick which configuration options they woud like to use and exclude more advnaced topics like keystore
:robot: This issue is automatically synced from: source