Temporal worker as microservice

I want to eliminate all http/grpc APIs endpoint in my current microservices, and convert all those APIs end point as small temporal workflows, which can invoked from other microservices workflows, my plan is injecting my application service layer to the to worker, and using that in activities. in short, i want temporal worker replacing my old http/grpc microservice.

The downside is I will have many small workflows with one activities as result converting my old http/grpc API endpoints as temporal workflow

  • Is it ok if I design temporal worker like that ?
  • Standard http/grpc server can processing multiple requests simultaneous, is a single temporal worker processing multiple workflows/activities simultaneous too ?

The downside is I will have many small workflows with one activities as result converting my old http/grpc API endpoints as temporal workflow

In this case, you can call activities hosted by other services directly instead of creating single activity workflows.

Standard http/grpc server can processing multiple requests simultaneous, is a single temporal worker processing multiple workflows/activities simultaneous too ?

Yes, a single temporal worker processes multiple workflow and activity tasks in parallel.