Since the goal of the API to connect to any database and explore it the API project cannot store connection information in config file. Instead connection info must be passed with every request.
Initially I was thinking to pass info in the body of the request, but since I have to implement GET requests also (which according to REST is not supposed to have bodies) I had two options:
- put connection info into request parameters (not safe)
- put connection info into request header
The latter solution seems to be the correct and simplest one: I used middleware in Express.js to read header and populate request’s connectionString parameter.
I found couple helpful links for anyone who wants to build API project:
So at this point the API structure I think will be following:
db – get list of all databases
db/:dbname – get, put, post, delete db named as :dbname
db/:dbname/collection – get list of all collections in db named as :dbname
db/:dbname/collection/:colname – get, put, post, delete collection named :colname in db named as :dbname
db/:dbname/collection:colname/doc – get list of all documents in collection named :colname in db named as :dbname
db/:dbname/collection/:colname/doc/:docid – get, put, post, delete document with id :docid in collection named :colname in db named as :dbname
There was some break since I have written anything, but I was not abandoning the project. Instead I took a class provided by MongoDB University:
I also read a book on Node.js:
When reading this book I felt at home first time I started learning web development – probably because I am really a back end developer.
After some consideration I came to conclusion that I need to start with API project first, so I added a new project on Github: