![]() Sso service saga use Cosmos DB persistence (it was previously used InMemmory and I thoguh this will fix the problem, but it also hapening with Cosmos DB persistence). Here are details about how I setup everything.Īll services are hosted in Azure AKS and use RabbitMq as a message broker (also hosted within same AKS cluster in same network). Message has been sent to bus but it doesn't initiate new saga instance. Most of the time everything is working fine, but some of requests from 'authenitcation service' to 'sso service' just timeout without any reason. This 'authentication service' is calling sagas as request/response because process must be done in same request for client. ![]() It actually calls 'sso service' saga always and then 'sso service' call 'provisioning service' when needed (provisioning is not always required). There is an 'authentication service', that when complete authentication part, calls these sagas to do provisioning and generate sso link. I'm using publish/subscribe way of communication here.īut the problem is with a caller to these sagas. And communication between these 2 sagas is OK. One is just 'sso service' to generate URL and the other is 'provisioning service' that orchestrate provisioning activities (I know I could use just one saga but I was playing with it and tried various scenarios). It's specific case since some provisioning is required and a lot of operations must be done in background so I found saga really helpful to orchestrate all operations. I'm using it in one of my projects and recently I've stuck with one issue. I'm relative new to MassTransit but I really like it more and more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |