Creating REST-ful, Hypermedia-based Micro-services with Spring Boot
Vložit
- čas přidán 23. 11. 2014
- Recorded at SpringOne2GX 2014.
Speaker: Ben Hale @nebhale
Web / JavaScript Track
Slides: www.slideshare.net/SpringCentr...
As data-driven applications become ubiquitous, the services that provide the data are proliferating. As teams become responsible for more and more of these services, it becomes critical that they be designed and implemented in a way that is as lightweight as possible.
This session will cover how to design micro-services as RESTful APIs and implement them with minimal code using Spring Boot. It will focus on API design using REST and HATEOAS, with live coding progressing from a tweet-length implementation all the way to a full-fledged app running in the cloud. - Věda a technologie
This was the most compreehensive material on REST-full, and what it really means, that I have come across so far. Thank you Spring and Ben Hale.
This is so helpful to understand REstful concepts
Its been very helpful, Thanks!!
Thanks for the understandable and to the point presentation on RESTful and Spring boot example.
Do you have the code in github? Please share it.
How would you adapt it to enable clients to make optimistic ui updates? In a more general sense, how would use hateoas without being tied to network to use an application?
Looking cold...
why not add subtitle
very nice explanattion
Much helpful!
ok
Can you make English subtitle for this video? My English listening skill is bad :)
Just REST no Micro services
Funny how people are still trying to bend their API to respect REST constraints, and still don't understand what REST is. RESTful just means "browseable" !! very few people actually need browseable APIs. Having a RESTful API means that one's client should only understand the media-type of your resource (the format, think HTML), and know how to interpret it to browse from a resource to another. Implementing it correctly will probably mean you have just invented a new form of media type (think HTML or atom) and a new form of browser. Your so called "RESTful" API (which is in fact an HTTP API) will probably never be RESTful, while your good old website already is. Roy Fielding's thesis just describes how the web works in the douchiest way possible. Do yourself a favor and stop trying to shoe horn hypermedia in your services when you absolutely don't need it, unless you're implementing a whole new protocol.
HATEOAS is crap. Rest of the REST is good
Michael and 009
@1:24"However being a good engineer ... I can't stand UI development at all" LOL ... So all the bad engineers are UI developers ?
:)
Really? WOW. don't be soo stupid, man
Thank you Ben. Please stop saying aaaahhhh so many times. Very nice presentation though.
I don't see why it's worth worsening the performance for the little benefit HATEAOS gives.
maybe ur missing what hateoas is all about then.
Useless