London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

Per Bjurström
Dec 3, 2013
  3697
(2 votes)

Remote Events Providers (EPiServer 7.5)

A long time ago I wrote an article that among other things used a trick to change how Remote Events works (the system used in load balancing). The implementation switched out Windows Communication Foundation (WCF) in favor of a custom database implementation to get events flowing in synch with data (when using SQL replication).

But now we have official support for Event Providers in 7.5 – and it’s used by both Commerce and CMS. It’s a pretty easy API to implement if you want to make your own provider:

 

image_thumb9

The built-in provider, based on WCF, is the same implementation used in previous versions so it should be a smooth upgrade if you have a complex setup with TCP endpoints for example.

But we are also releasing more providers on the NuGet feed, one for Azure Service Bus and one for Amazon SQS/SNS to take advantage of the elastic scaling of cloud environments. How to configure them are available in the CMS SDK.

Anyhow, I picked up the old code from my custom implementation and rewrote it into the new event provider system. Basically its just serializes and deserializes message to and from a table in SQL Server, more a proof of concept than anything I would put into production. It’s available on GitHub if you want to play with it.

Dec 03, 2013

Comments

per@hassle.net
per@hassle.net Dec 3, 2013 03:37 PM

Cool!

Dec 4, 2013 08:34 AM

Awesome stuff, how are the bus providers (Azure / Amazon) in terms of reliability?

The previous UDP based multicast system was a fire and forget system and If a server missed an event the server would be out of sync.

Is a message only removed once all servers have "received/acknowledged" a message it or is it still a fire and forget system in Azure as well?

Dec 4, 2013 02:11 PM

They are implemented using a publish/subscribe pattern so senders hand off the message to a topic and receivers poll their subscriptions (which are individual queues per server). So basically if UDP is as synchronous you can get the cloud providers are as asynchronous you can get with guaranteed message delivery.

Please login to comment.
Latest blogs
Optimizely Product Recommendation Troubleshooting

In today’s fast-paced digital landscape, personalization is everything . Customers expect relevant, tailored experiences whenever they interact wit...

Sanjay Kumar | Apr 28, 2025

Natural Language Q&A in Optimizely CMS Using Azure OpenAI and AI Search

In Part 2, we integrated Azure AI Search with Azure Personalizer to build a smarter, user-focused experience in Optimizely CMS. We used ServiceAPI ...

Naveed Ul-Haq | Apr 25, 2025 |

Identifying Spike Requests and Issues in Application Insights

Sometimes within the DXP we see specific Azure App Instances having request spikes causing performance degredation and we need to investigate. I fi...

Scott Reed | Apr 25, 2025

Optimizely Frontend Hosting Beta – Early Thoughts and Key Questions

Optimizely has opened the waitlist for its new Frontend Hosting capability. I’m part of the beta programme, but my invite isn’t due until May, whil...

Minesh Shah (Netcel) | Apr 23, 2025

Developer Meetup - London, 21st May 2025

The London Dev Meetup has been rescheduled for Wednesday, 21st May and will be Candyspace 's first Optimizely Developer Meetup, and the first one...

Gavin_M | Apr 22, 2025

Frontend hosting for PaaS & SaaS CMS

Just announced on the DXP, we FINALLY have a front end hosting solution coming as part of the DXP for modern decoupled solutions in both the PaaS a...

Scott Reed | Apr 22, 2025