![]() ![]() Using MassTransit.EntityFrameworkIntegration Using MassTransit.AzureServiceBusTransport The Policy looks as follows: namespace .Policies "AzureSbKeyName": "RootManageSharedAccessKey", "ConnectionString": "Database connection string", "$type": ".Policies.AbandonCartsPolicy, ", ![]() This policy is defined in "Shop.json" file of the environment of Commerce as below: We also define our Policy named AbandonCartsPolicy. First we have different contracts to communicate to our external API. I have implemented a small list of applications as mentioned in the below image to accomplish the approach: It does mean that different commerce operations/events can be published to ESBs and Saga (i.e a state machine) can be configured to listen to those ESB and interact accordingly means of updating our entity tables, sending mail to customers etc. Most interestingly MassTransit ("" ) who already implemented framework to communicate through enterprise messaging systems (ASB, MSMQ etc), they also provide a Saga implementation with it meaning we can hook our Service Bus messaging system with it. Can be a event when we have a cart convert to Order. Now the event can be a Cart line item to be added to a cart or removed. ![]() Last week i came to know what is Saga design pattern and how can we efficiently define a state machine which will be interacted with different events (So basically it's something a process which sleep by default but can be fired with different events). I know there is a Sitecore's way of dealing with Abandon carts but i am going to discuss something other approach. Today i am going to describe how efficient we can handle abandon carts in Sitecore commerce. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |