Last post Dec 10, 2018 10:02 AM by DA924
Dec 10, 2018 02:46 AM|wavemaster|LINK
I have a ASP.NET core based socket application monitoring incoming data.
When a trigger condition is met particulars are written to a staging table.
Now I want to process records in this staging table where I will be making several api calls to 3rd parties.
This needs to be done separate from the main thread.
Previously there was a loop checking that table every few seconds to see if new records were written.
Can this be done a little bit more elegant in Core?
Dec 10, 2018 09:07 AM|Xing Zou|LINK
Entity Framework Core Triggers meets your requirements. Add triggers to your entities with insert, update, and delete events. There are three events for each: before, after, and upon failure.
Dec 10, 2018 10:02 AM|DA924|LINK
So you could use CLR triggers at the database level.
You can use MS SQL Server Service Broker using its message queuing features using XML data being processed as messages.
Let MS SQL Server do it, possibly. I have seen Service Broker in action back in year 2008. It's powerful technology.