Skip to content

Commit

Permalink
docs: fix formatting of list (#613)
Browse files Browse the repository at this point in the history
# Description

Fixes list formatting in blog post. I should've done this for
Hacktoberfest to get some swag 😄
  • Loading branch information
ChrisKujawa authored Nov 11, 2024
2 parents f152f6e + 3e1acfd commit 3c37bd3
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions chaos-days/blog/2024-10-24-Camunda-Exporter-MVP/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,12 +45,12 @@ The plan for this project looks something like this:
We plan to:

1. Harmonize the existing indices stored in Elasticsearch/Opensearch
2. Space: Reduce the unnecessary data duplication
- Space: Reduce the unnecessary data duplication
2. Move importer and archiver logic into a new Camunda exporter
3. Performance: This should allow us to reduce one additional hop (as we don't need to use ES/OS as a queue)
4. Maintenance: Indices and business logic is maintained in one place
5. Scalability: With this approach, we can scale with partitions, as Camunda Exporters are executed for each partition separately (soon partition scaling will be introduced)
6. Complexity: The Camunda Exporter will be built-in and shipped with Zeebe/Camunda 8. No additional pod/application is needed.
- Performance: This should allow us to reduce one additional hop (as we don't need to use ES/OS as a queue)
- Maintenance: Indices and business logic is maintained in one place
- Scalability: With this approach, we can scale with partitions, as Camunda Exporters are executed for each partition separately (soon partition scaling will be introduced)
- Complexity: The Camunda Exporter will be built-in and shipped with Zeebe/Camunda 8. No additional pod/application is needed.

Note: Optimize is right now out of scope (due to time), but will later be part of this as well.

Expand Down

0 comments on commit 3c37bd3

Please sign in to comment.