Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2847

Isolate requests to the Event Ingestion API from rest of the API

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.0.0-alpha1, 3.0.0
    • None
    • backend
    • None
    • 80

      Context:
      To isolate the ingestion API from normal user requests we should either assign it a dedicated threadpool if possible or serve it with a dedicated jetty on different ports (http/https).

      AT:

      • a high load of requests against the event ingestion API doesn't heavily impact the performance of the rest of the API

        This is the controller panel for Smart Panels app

          1.
          		 Evaluate different options for isolating the ingestion API Sub-task Done Unassigned
          2.
          		 Add QoS filter to limit the number of ingestion requests at any given time Sub-task Done Unassigned
          3.
          		 Respond with correct error code when we can't serve ingestion API requests Sub-task Done Unassigned
          4.
          		 Disable the event ingestion endpoints if disabled in configuration Sub-task Done Unassigned

              Unassigned Unassigned
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: