In this chapter, we dived into some rather complex topics. Let's sum up what we covered. We started by specifying the operations of our Web API and defined that an operation is a combination of a URI and HTTP action. Next, we implemented routes and bound them to an operation. Then we requested each operation using the RestClientTool of the Enide Studio to request the URIs that we routed. In the content negotiation section, we handled the Accept HTTP header to provide the results in the format requested by consumers. Then, we had a brief look at the CORS recommendation, and you learned how to enable it via middleware provided by the CORS package. Finally, we covered the topic of API versions that allow us to develop backward-compatible APIs.
We used old-fashioned filesystem storage for our data in this chapter. This is not suitable for a web application. Thus, we will look into modern, scalable, and reliable NoSQL storage in the next chapter.