CamundaClient or Camunda Api which one best?

[yadav1990]

Hi,

I am using Camunda 8.8 self-managed. Now, I have requirement to manage the task lifecycle through React UI and sync with relational database so, which one is best approach, using camunda exposed API or write own api using camundaClient service layer?

What would be the challenges while doing migration?

NOTE: I want to use wrapper api and call camunda service layer instead of using Camunda Api to have more control on logic.

Any idea?

TIA

[zee-bot]

For Camunda 8.8, I recommend using a wrapper API with the unified Camunda 8 REST API (v2) rather than direct API calls, as this gives you the control you need for custom logic and database synchronization. I found the following relevant resources:

• User task lifecycle with Camunda 8 REST API
• Camunda 8.8 API announcements and CamundaClient
• Custom tasklist architecture for database sync
• Access control patterns for wrapper APIs
• Migration challenges from v1 to v2 API
• Tasklist API v1 deprecation timeline

Does this help? If not, can anyone from the community jump in?

---

Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process.

[GotnOGuts]

Reading the Java Client doc page, the Java Client is calling the REST or gRPC APIs under the covers, and handling the webclient calls for you.

So at the end of the day, you aren’t using a Java Service Layer, but are using a REST (or gRPC) API.

Or… at least, that’s how I read it.