Summary

In this chapter, we have learned about and implemented caching and rate-limiting functions in our Smilecook API. Such functions make our APIs even more efficient. Our Smilecook application is saving the cache in application memory, though, which means the cache will be gone after a server reboot. To address this, we can work with Redis or Memcached in the future, which can persist the cache even after a server reboot. They also support sharing the cache with multiple servers. This is something we encourage you to explore outside of this book. The most important thing at the moment is for you to learn all the fundamental concepts covered in this book. So, later, if you want to extend to more advanced implementation, it shouldn't be too hard for you.

In the next and final chapter, we will build the Smilecook frontend client for you to work with the backend API. Through this frontend client, we will understand the whole picture better. You will see how the frontend and...