Here's my notes from his talk:
RPC (Remote Procedure Call) vs. REST (REpresentational State Transfer)
RPC endpoints are verbs (api.example.io/getUrser), in REST endpoints are resources (/User)
HATEOAS - hypermmedia as the engine of application state
Data exchange should be treated as if the client were a web browser
No documentation or out-of-band info needed
Use RPC when dealing with a simple object, like the Slack API
Use REST when dealing with lots of different objects with CRUD operations possible on all of them
GraphQL is useful when trying to traverse a graph of REST calls
REST + JSON is popular but hard because no schema is available for the data.
HAL and JSONSchema try to solve that. Also Ion trys to give structure to JSON data.
The Ion content type is application/ion+json
Ion data is embedded in JSON with fields, like "href","rel", and "value".
ASP.NET Core is a full rewrite of .Net to be portable, faster and cleaner.
Dependency Injection is now in the framework, don't have to download StructureMap
Nate has a free eBook about starting with .Net Core at https://www.recaffeinate.co/
Demo to create new .Net Core API with Web API template. No diff between MVC or API controllers.
Nate used package Entityframework inmemory to do development of demo. inmemory just gives an inmemory
ASP.NET Core is friendly to async/await pattern. async first philosophy.
@nbarbettini
https://www.recaffeinate.co/
Nate has a Lynda.com course on this.
https://github.com/nbarbettini/BeautifulRestApi is the result of his 4 hour Lynda course.
Nate has done a great job of learning .NET Core and sharing his knowledge with the community free of charge.
No comments:
Post a Comment