My Latest Pluralsight Course: Building and Securing a RESTful API for Multiple Clients in ASP .NET

I am *very* happy to announce my latest Pluralsight course is now live!  It’s called Building and Securing a RESTful API for Multiple Clients in ASP .NET (that’s about all the words I could fit in one title ;-)).  Keywords: REST.  Web API.  OAuth 2.0 & OpenID Connect.  ASP .NET MVC, Mobile (WinPhone).

The course combines what I’ve learned in the field in my day-to-day job as mobile solution architect: what works (and what doesn’t) when you need to build an API that’s to be consumed by a variety of clients (mobile, web, …)?  What are the best practices for building RESTful API’s?   How do you secure something like that (for example: why should you do things differently when you’re building a native mobile client versus a web client versus a javascript-based client)?

And, even more important than the how: why do you have to keep all these things into account?

Here’s a short description of what to expect:

We all seem to be building RESTful API’s these days, with ASP .NET Web API.  But REST is bigger than that – it’s an architectural system.  If you’re looking to learn what REST actually is and how to build a REST-ful API with ASP .NET Web API, aimed at multiple client types (web/mobile), this is the right course for you.

It’s filled with best practices concerning URI design, data shaping, paging, caching, versioning, and so on – it’s very demo-driven, and we start from scratch. It contains an API and two different clients: an ASP .NET MVC client and a mobile client.

To top it off, you’ll also learn all about securing both client apps and the API with OAuth 2.0 and OpenID Connect.  The focus is on what works for standardized API development for multiple (possibly cross-platform) clients.

If you think this is something for you, make sure you have a look – I hope you’ll enjoy it!