I will be making an API for my Portfolio. In order to make the API, I need to first choose what I want my stack to be. I think a good starting point will be deciding what language I want my API to be developed in. In order to decide what language I need to first list the needs of my portfolio.
Fast - Fast language, and Integration of caching of large API responses(Redis maybe?).
Reliable - Replication of data in case of Database failure.
Maintainable - Clean code that is easy for updates and changes.
Modular/Reusable - Develop the application as if it could be a portfolio for anyone or any profession.
RESTful API. - If I decide to revamp the front-end later, the backend needs to be able to support any new front end changes.
Cost. - Since it is a portfolio and there is no annual financial ROI (Return on Investment), The cost of hosting is crucial. This is primarily an informative website and cost needs to be kept to a minimum.
I am not the type of developer that is stuck in any particular language or stack, So I will be weighing the choices very carefully. I already know many languages, so choosing the right one given all of these application requirements will take some research. I will update my findings below as time permits.
dgallegos
commented
7 years ago
I will be making an API for my Portfolio. In order to make the API, I need to first choose what I want my stack to be. I think a good starting point will be deciding what language I want my API to be developed in. In order to decide what language I need to first list the needs of my portfolio.
I am not the type of developer that is stuck in any particular language or stack, So I will be weighing the choices very carefully. I already know many languages, so choosing the right one given all of these application requirements will take some research. I will update my findings below as time permits.