Use case – Implementing Azure Functions to send emails

Here, we will use a subset of the Azure components we described previously. The use case from WWTravelClub proposes a worldwide implementation of the service, and there is a chance that this service will need different architecture designs to face all the performance key points that we described in Chapter 1, Understanding the Importance of Software Architecture.

If you go back to the user stories that were described in Chapter 1, Understanding the Importance of Software Architecture, you will find that many needs are related to communication. Because of this, it is common to have some alerts be provided by emails in the solution. The use case of this chapter will focus on how to send emails. The architecture will be totally serverless.

The following diagram shows the basic structure of the architecture. To give users a great experience, all the emails that are sent by the application will be queued asynchronously...