I’m not a nerd!! But I love to learn technology. Have a good collection of tech book soft copies, hardly read. Always bing to solve problem. Now decided to scribble - whatever I binged for my tech work!!!! Disclaimer: This is not my view ;) itz collated views
Thursday, January 17, 2019
HATEOAS provider for ASP.NET Core
When comes to API maturity model there are two major models:
1. Richardson Maturity Model
2. Amundsen Maturity Model.
To attain RMM 3.0, an API defines resources, respect HTTP protocol and provide self discover able links to other resources.
To attain AMM 3.0, the APIs are focused on the actions the API affords and consumers can take.
So, to reach maturity level 3, the API or resource MUST provide an action or a list of actions a client can identify on that API at the run time. This translates to HATEOAS.
While doing some research on Hypermedia As The Engine Of Application State(HATEOAS), I came across some great HATEOAS providers for ASP.NET Core, but they didn't quite fit my need, so I created my own one.
You can read more details from my github page
- https://github.com/ajopjo/AspNetCore.HypermediaLinks
Subscribe to:
Post Comments (Atom)
Featured post
How to connect to Mongo Atlas from Robo 3T
If you use a local instance of MongoDB, you might be a great fan of Robo3T. However, if you are using Mongo Atlas, the Atlas web interface p...
Popular Posts
-
Last week I was working on on-boarding a few SAP Odata APIs to API Management gateway. The APIM tool used by my organization supports JSON ...
-
Our team has used EWS API's Appointment service to book a meeting room. During our testing, its been noted that the room was not block...
-
When comes to API maturity model there are two major models: 1. Richardson Maturity Model 2. Amundsen Maturity Model. To attain RMM...
No comments:
Post a Comment