Software Design Patterns and Methodology Cheat Sheet

Web Services Descri­ption Language, describes the functi­onality offered by a web service. Provides a machin­e-r­eadable descri­ption of how the service can be called, parame­ters, data structure returns.

A software design pattern that restricts the instan­tiation of a class to one object. This is useful when exactly one object is needed to coordinate actions across the system. Private or protected constr­uctor with a public static method to retrieve the instance.

Define an interface for creating an object, but let subclasses decide which class to instan­tiate. Factory Method lets a class defer instan­tiation to subcla­sses.

Repres­ent­ational State Transfer, a way of providing intero­per­ability between computer systems on the Internet. REST-c­omp­liant Web services allow requesting systems to access and manipulate textual repres­ent­ations of Web resources (XML, HTML, JSON) using a uniform and predefined set of stateless operat­ions.

Strongly advocate automation and monitoring at all steps of software constr­uction, from integr­ation, testing, releasing to deployment and infras­tru­cture manage­ment. Aims at shorter dev cycles, increased deployment frequency, more dependable releases, in close alignment with business object­ives.

Corres­ponding or similar in form and relations.

The Hypertext Transfer Protocol (HTTP) is an applic­ation protocol for distri­buted, collab­ora­tive, and hypermedia inform­ation systems

GET
The GET method requests a repres­ent­ation of the specified resource. Requests using GET should only retrieve data and should have no other effect.
HEAD
The HEAD method asks for a response identical to that of a GET request, but without the response body. This is useful for retrieving meta-i­nfo­rmation written in response headers, without having to transport the entire content.
POST
The POST method requests that the server accept the entity enclosed in the request as a new subord­inate of the web resource identified by the URI. The data POSTed might be, for example, an annotation for existing resources; a message for a bulletin board, newsgroup, mailing list, or comment thread; a block of data that is the result of submitting a web form to a data-h­andling process; or an item to add to a database.
PUT
The PUT method requests that the enclosed entity be stored under the supplied URI. If the URI refers to an already existing resource, it is modified; if the URI does not point to an existing resource, then the server can create the resource with that URI.
DELETE
The DELETE method deletes the specified resource.

TRACE
The TRACE method echoes the received request so that a client can see what (if any) changes or additions have been made by interm­ediate servers.
OPTIONS
The OPTIONS method returns the HTTP methods that the server supports for the specified URL. This can be used to check the functi­onality of a web server by requesting '­*' instead of a specific resource.
CONNECT
The CONNECT method converts the request connection to a transp­arent TCP/IP tunnel, usually to facilitate SSL-en­crypted commun­ication (HTTPS) through an unencr­ypted HTTP proxy.
PATCH
The PATCH method applies partial modifi­cations to a resource.

All genera­l-p­urpose HTTP servers are required to implement at least the GET and HEAD method­s,[22] and, whenever possible, also the OPTIONS method