Future work

Congratulations, you have a fully functional web application to store and share recipes! But for all the projects you develop, it is crucial to keep in mind that there are always points of improvement for your architectures, and you should always conduct a regular review to understand the improvement points. That’s what you are going to do now.

Using secure protocols

It’s clear why HTTP is not a good option. So, if you followed option 2, the first improvement you could focus on is to migrate to option 1 and configure HTTPS for API communication.

Infrastructure auto-scaling

By now, regardless of the option you followed, you have one EC2 instance supporting your backend, but what happens if the load increases? A lack of compute resources brings a bad user experience and can lead to instance failure, so how can you cope with a failed instance?

Architecting with failure in mind is the path for resilient applications. So, it is always a good practice...