We are interested in using Temporal as the workflow engine to serve the online customer request. We just start the learning, so bear with me for sec.
Request & reply use case: Our online portal calls bunch of services behind, the front-end will wait until the orchestration complete . then show the result to user. The elapse time is around 5 sec. How to design the system using Temporal for this case? I am worried about the resource being held on the web portal if there are too many request. Is there a way to listen to the completion of the workflow from the requesting side?
Can queuing API and worker API be deployed separately in order to scale them differently? From the architecture diagram (https://docs.temporal.io/docs/server-architecture), it seems API is held together. Our thought is that queuing part should be super fast and reliable, but worker part can be very heavy and slow. By the way, where can I find the info on how to scale Temporal?
security: is there a way to encrypt the data in the database?