Understanding Azure Serverless

In the previous chapters, we created a document structure as a repository and implemented ASP.NET Core services as containerized microservices so that we could cover our main application use cases. These use cases can be considered the primary data flow through the application, and our main concern for performance is concentrated around these data paths. Nevertheless, the secondary use cases, such as keeping track of the statuses of auctions for a user that he/she has previously got involved in, or creating a feed to inform users about new vehicles up for auction, are the features that could increase the return rate of the users and maintain the user base. Therefore, we would need a steadfast, event-driven strategy that will not interfere with the primary functionality and should be able to scale without having to interfere with the infrastructure...