JSON, REST, SOAP, WSDL, and SOA: How do they all link together -


currently doing exams , i'm struggling through concepts. these have been 'mentioned' in notes didn't understand how linked together. far understanding is:

soa - solution make service consumers/providers communicate. (as far understand umbrella term else)

wsdl - language describes provider service.

soap - xml protocol 'wrapper' used services send messages. works in conjunction wsdl provide parameters?

rest - design pattern similar soap in function avoids xml? (really not sure one)

json - alternative xml uses javascript? (not sure 1 either)

looking around in internet there doesn't seem clear definition of of these , how interlink.

imagine developing web-application , decide decouple functionality presentation of application, because affords greater freedom.

you create api , let others implement own front-ends on well. did here implement soa methodology, i.e. using web-services.

web services make functional building-blocks accessible on standard internet protocols independent of platforms , programming languages.

so, design interchange mechanism between back-end (web-service) processing , generation of useful, , front-end (which consumes data), anything. (a web, mobile, or desktop application, or web-service). limitation here front-end , back-end must "speak" same "language".


that's soap , rest come in. standard ways you'd pick communicate web-service.

soap:

soap internally uses xml send data , forth. soap messages have rigid structure , response xml needs parsed. wsdl specification of requests can made, parameters, , return. complete specification of api.

rest:

rest design concept.

the world wide web represents largest implementation of system conforming rest architectural style.

it isn't rigid soap. restful web-services use standard uris , methods make calls webservice. when request uri, returns representation of object, can perform operations upon (e.g. get, put, post, delete). not limited picking xml represent data, pick (json included)

flickr's rest api goes further , lets return images well.


json , xml, functionally equivalent, , either chosen. xml thought of being verbose, , harder parse, many-a-times, data more adequately represented using json. (e.g. serialization)

it choice nonetheless.


Comments

Popular posts from this blog

SPSS keyboard combination alters encoding -

Add new record to the table by click on the button in Microsoft Access -

CSS3 Transition to highlight new elements created in JQuery -