18 Dec 2018 - garfbradaz - blog
I liked the idea around this, so I’m going to do the same, but in a blog style, but replacing Node.js and Express with ASP.NET Core WebAPI. I also want to use a MongoDB as a the backend.
The API itself will be for a Book Shop Chain who want to expose their stores and titles via a public RESTful service for other companies to use. This can be used for stock lookups and to see which stores have stock available to sell.
Here are some example Epics to show the shape of the API needed:
As a book store I can add our store to the database So we can be accessible
As a book store I can add our inventory to our database So we can expose our inventory
As a book store We can update a books stock level For an accurate stock level
As a API consumer I can look up a stores address So we know where to buy a book
As a API consumer I can look up a book So we can get a list of stores who sell a book
As book store IT Security We can add API Keys to the API For API Consumers to use when querying the API
My plan is to release weekly blog posts covering in a similar fashion like Nathan’s:
I will post any code on Github as well.
So before starting cracking on with this, make sure your environment is set up. Because this is .NET Core, this is cross platform, so if you own a Mac or Linux box, feel free to join in. I’m going to be building this on a Surface Book, but I will try to be a good Xpat-Citizen and test across environments.
Please make sure the following is installed:
We wont need to install Mongo as we will be running it using Docker.
I will be using Visual Studio Code for cross platform .NET Core support. I use a bunch of extension which I have put here:
You can import these using the following Settings Sync extension on the marketplace:
If you already use VSCode, you may just want to find the C#, Docker GitLens and .NET Core Test Explorer extensions.
Note:My list contains extensions like Jekyll support which you wont need for this.
We will create the ASP.NET Core WebAPI template, set up the project structure. Join me next time!.