Marco de Freitas - Create a .Net Core Rest API (Workshop) #10
Description
Lets create a Web API using .NET Core
- Speaker : Marco de Freitas
- Available : Most probably after September
- Length : Since it is a workshop I would aim for 6h~8h, we can see how to adjust to better fit the contents
- Language : English
Description
Most people have heard about .NET Core or how fast it is or how cool it is (it's really cool!) but they do know how easy it is to create a Web API app? In this workshop my aim is to present all that I have learned so far on creating endpoints to be consumed by others, following some best practices or patterns, how we can add authorization and authentication and consuming other web services from our web services.
Speaker Bio
Open-minded, detail-oriented professional with more than five years of experience as a software developer and is also a Certified Scrum Product Owner. Loves programming in C#, operating in Visual Studio and is an avid fan of testing. He likes to learn and help others and has a problem-solving creative approach. Did he mention he has a sense of humor? 😄
Links
- GitHub: https://github.com/marcolinopt
- LinkedIn: https://www.linkedin.com/in/marcolinopt/
- Photo: https://drive.google.com/open?id=0B7yFYja1PZplZjNsQlJBVFl6M2M
Extra Information
The aim of the workshop would be to create a web app using Visual Studio (VS) 2019. We would start by cloning a provided repo and implement a small application with GET, POST, PUT, DELETE and PATCH endpoints to exemplify how they are implemented, with a special focus on PATCH since it differs from .NET framework a little bit. To consume the endpoints we would use Postman but attendees can use other tools like HTTPPie.
To complicate things a little more we would then add authorization and authentication using IdentityServer4 (ID4), a middleware that is very popular in the .NET community and is very straightforward to implement. We can talk about the possibilities of implementation, how it is implemented and why we are implementing using ID4.
Another point I was thinking of introducing in the workshop would be consuming web services from within a web service by calling another set of endpoints already scaffolded and consuming them using .NET Core's HTTP client which can be customized and even has its own small set of best practices.