Per Bjurström
Dec 3, 2013
  3058
(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
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog