Building a serverless “Shopping Cart” microservice using Azure functions and Durable entities with c# [Tutorial]

We will be building a fully functional “microservice” that will be able to add, remove, and return a list of products. For this example we will model the way this microservice will be consumed will be done via REST. Get your coding hat on, we are about to start.

The setup

Before we begin you should have a new function project setup and the durable functions set-up. If you are not very sure about how to achieve this, here is a link to the official documentation.

Pro tip: in some IDEs (I use Rider) you have the option on the project setup to chose durable functions, so you don’t need to install the required NuGet packages by hand.

Durable entities and the actor pattern

So, since you found this article via searching or by clicking somewhere on social media, you should already know what durable entities are, or at least have an idea about them. But, just to be sure that we are all on the same page we will be doing a small introduction on durable entities, and why, when, and where we might be able to benefit from them.

“Durable entities” or “entity functions”, how they are called nowadays, are mostly inspired by the virtual actors pattern from the Orleans project, which in term are quite inspired by Akka/ Going into this topic is well outside of our scope, but you will find an introduction in them in the links provided, also I highly recommend looking a bit into them, because understanding the strengths and weaknesses of the actor pattern will help you when trying to determine if the durable entities might be a good match for you or should you use a more traditional SQL or NoSql storage.

Well, probably you haven’t clicked any of the links above … in case you did, well done!

Anyway, long story short, an actor is an isolated construct that holds it’s own state and has its behavior, they do not share memory and the communication is done asynchronously using some kind of message box/queues. They are kept in memory while in use and when disposed they are usually serialized to disk. They can run in grate numbers, and depending on the implementation they can be hierarchical. In general actor, systems are self-healing.

So, more or less the durable entities are some kind of actors. They are very good at keeping track of some small to mid-sized objects state and behavior, and also quite interestingly they hold the state in the table storage of the storage account that is used by the function app. This can be seen as an advantage through the lens of scalability and availability since both of these are handled automatically by Azure storage. Also, what is quite important to know is that the entities themselves are event-sourced.

Before we dive in the actual code there is one more thing I still need to address, why use entities for a shopping cart rather than using a classic SQL or NoSql DB. And this is quite a good question. As I usually say, almost all the things could be built in a lot of ways, each of them having particular benefits and downsides, so next, we will be diving in and see why it might be beneficial to use entities rather than SQL or CosmosDB.

We are operating on the assumption that azure functions are running on a consumption plan.

So one of the most appealing parts of the whole serverless movement and compute offer is the near “infinite” auto-scaling. So, by utilizing something that is also “serverless” for holding the state seems to be a good match. One would argue that CosmosDB is also serverless, but although the connection between Cosmos and functions could be done via binding it still is not as seamless as with the entities functions. Regarding SQL, well it is kind of evident why something that can scale as much and as fast as required should not be paired with something that isn’t able to scale as fast.

Also, one of the benefits of actors in general, and in our case durable entities, is that they are kept in memory for a time whiteout being offloaded, using them we avoid the latency of a round trip to the DB, since we are essentially using in-memory objects, that get serialized and serialized behind the scene.

The Code

Regarding the overall design, the microservice will expose a restful endpoint with the following API methods:

As you can see here, there is an {id} that should be a GUID generated by the client, this way in theory this type of microservice could be used with any client software, without the need of knowing anything about it. Regarding the GUID type, this could be changed to a regular string, but this way ensures against collisions.

The heart of the whole demo is the durable entity, which is defined as follows:

After a glance at the code, some interesting things could be noticed. It looks more or less like a regular domain entity with properties and behavior. Also, the property that keeps the actual state is private (I wouldn’t go as far as saying encapsulated) and only modified using the exposed public methods, and also it’s content is also returned via a public method. One thing that we need to keep in mind is that a method of an entity function can only return void, Task or Task<T>, nothing else.

For the state container we also use the following class:

In this class, we could have all the imaginable properties as long as they are serializable, for sake of the example I tried to keep it as short as possible, but here you could have also the price when added, or the name and description, even a link to a product image or whatever.

Now that we have set up the entity itself, we will manipulate it using rest triggers, again for simplicity’s sake, the recommended way of interacting with entities is using orchestrator/durable functions, but the interactions are required in our example could be done directly from the triggers.

So for adding an item to the cart here is the trigger code:

So, here we are using a command approach, with a simple accepted response.

For removing an item from the cart, the code is remarkably similar:

And for retrieving the elements from a cart:

And more or less, this is it. We now have a serverless microservice that could scale on demand.

Before we end this, I just want to remind you that this is a high level presentation of the concept, if you have any question, or would like to see more content about this feel free to add a comment on reach out to me on twitter.

As usual, you could get a closer look at the code on this github repository.

Originally published at on September 18, 2020.




Special, like everybody else …

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Distributing Gatling load tests with Kubernetes

Inheritance and Polymorphism in Java

Leveraging the most out of Managed App Configurations: An Android Enterprise focal point

Fluentd Pulsar Plugin

AWS Elastic Load Balancer — Overview

Problem Solving and Expert definition to work on a Project

Static code analysis for your Infrastructure Deployments

Python Code for Identifying Seasonal Customers

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


Special, like everybody else …

More from Medium

Access DynamoDB from Lambda (.Net, C#)

AWS SDK + .NET Core | Part 2

Creating a Dev Container for TypeScript and VS Code — Part 2

GraphQL Authentication and Authorization in DotNet 6 using MongoDB