https://github.com/dominikangerer/spring-second-demo

Tried myself ot the Getting Started: Building REST services with Spring with slightly different packages
https://github.com/dominikangerer/spring-second-demo

Last synced: 14 days ago
JSON representation

Tried myself ot the Getting Started: Building REST services with Spring with slightly different packages

• Host: GitHub
• URL: https://github.com/dominikangerer/spring-second-demo
• Owner: DominikAngerer
• License: mit
• Created: 2015-01-22T21:43:50.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2015-04-11T17:23:50.000Z (over 9 years ago)
• Last Synced: 2024-11-06T20:19:30.764Z (2 months ago)
• Language: Java
• Homepage: https://spring.io/guides/tutorials/bookmarks/
• Size: 207 KB
• Stars: 2
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Getting Started

## Building REST services with Spring

REST has quickly become the de-facto standard for building web services on the web because they’re easy to build and easy to consume.

There’s a much larger discussion to be had about how REST fits in the world of microservices, but - for this tutorial - let’s just look at building RESTful services.

Why REST? REST In Practice proffers, to borrow Martin Fowler’s phrasing, "the notion that the web is an existence proof of a massively scalable distributed system that works really well, and we can take ideas from that to build integrated systems more easily." I think that’s a pretty good reason: REST embraces the precepts of the web itself, and embraces its architecture, benefits and all.

What benefits? Principally all those that come for free with HTTP as a platform itself. Application security (encryption and authentication) are known quantities today for which there are known solutions. Caching is built into the protocol. Service routing, through DNS, is a resilient and well-known system already ubiquitously support.

REST, however ubiquitous, is not a standard, per se, but an approach, a style, a constraint on the HTTP protocol. Its implementation may vary in style, approach. As an API consumer this can be a frustrating experience. The quality of REST services varies wildly.

[Want more?]

[Want more?]: https://spring.io/guides/tutorials/bookmarks/