Showing posts with label rest. Show all posts
Showing posts with label rest. Show all posts

Tuesday, 3 May 2016

JAX-RS 2.0 : Server side Processing Pipeline | Thinking in Java EE (at least trying to!)

JAX-RS 2.0 : Server side Processing Pipeline | Thinking in Java EE (at least trying to!): "The inspiration for this post was the Processing Pipeline section in the JAX-RS 2.0 specification doc (Appendix C). I like it because of the fact that it provides a nice snapshot of all the modules in JAX-RS – in the form of a ready to gulp capsule !"



'via Blog this'

Sunday, 21 February 2016

REST and Web Services links


How to design a REST API



http://blog.octo.com/wp-content/uploads/2014/12/OCTO-Refcard_API_Design_EN_3.0.pdf

Best Practices for Designing a Pragmatic RESTful API

 Good article on #SOA and #REST alignment http://t.co/OJutT8AiKS

Web Application Description Language


REST API Documentation Using JAXRS-ANALYZER


SWAGGER The World's Most Popular Framework for APIs

The Swagger framework addresses server, client, documentation, and sandbox needs for RESTful APIs.[citation needed]
As a specification, it is language-agnostic. It is also extensible into new technologies and protocols beyond HTTP.[citation needed]
With Swagger's declarative resource specification, clients can understand and consume services without knowledge of server implementation or access to the server code.[citation needed]
The Swagger UI framework allows both developers and non-developers to interact with the API in a sandbox UI that gives clear insight into how the API responds to parameters and options. Swagger may utilize both JSON and XML.

Friday, 17 April 2015

Software Architecture links

Ben Morris: What role do architects have in agile development?

Enter the “master developer”

In this case, some kind of design authority is generally required to work across the teams to ensure the integrity of the overall system and spot issues before they become obstacles. This role shouldn’t be confused with governance, where design edicts are sent down to teams from the “ivory towers” and architecture boards. It can only be effective with the consent of the teams.