WCF REST Vs Web API

1. SOA
2. WCF REST Vs Web API

WCF REST	Web API
To use WCF as WCF Rest service you have to enable webHttpBindings.	This is the new framework for building HTTP services with easy and simple way.
It support HTTP GET and POST verbs by [WebGet] and [WebInvoke] attributes respectively.	Web API is open source an ideal platform for building REST-ful services over the .NET Framework.
To enable other HTTP verbs you have to do some configuration in IIS to accept request of that particular verb on .svc files	Unlike WCF Rest service, it use the full featues of HTTP (like URIs, request/response headers, caching, versioning, various content formats)
Passing data through parameters using a WebGet needs configuration. The UriTemplate must be specified	It also supports the MVC features such as routing, controllers, action results, filter, model binders, IOC container or dependency injection, unit testing that makes it more simple and robust.
It support XML, JSON and ATOM data format.	It can be hosted with in the application or on IIS. It is light weight architecture and good for devices which have limited bandwidth like smart phones. Responses are formatted by Web API’s MediaTypeFormatter into JSON, XML or whatever format you want to add as a MediaTypeFormatter.

Integration GLOSSARY

• API A software interface that allows users to configure and interact with other programs, usually by calling from a list of functions.


• DENIAL OF SERVICE (DOS)ATTACK An attack on a resource, caused when a perpetrator intends to make a resource unavailable by placing massive amounts of requests on the given resource.


• DOCUMENTATION-DRIVEN DEVELOPMENT A philosophy of software development in which documentation for a feature is written before the feature is created.


• ENTERPRISE INTEGRATION (EI) A field that focuses on interoperable communication between systems and services in an enterprise architecture; it includes topics such as electronic data interchange, integration patterns, web services, governance, and distributed computing.


• ENTERPRISE INTEGRATION PATTERNS (EIP) A growing series of reusable architectural designs for software integration. Frameworks such as Apache Camel and Spring Integration are designed around these patterns, which are largely outlined on EnterpriseIntegrationPatterns.com.


• ENTERPRISE SERVICE BUS (ESB) A utility that combines a messaging system with middleware to provide comprehensive communication services for software applications.


• FARMING The idea of providing services by leveraging the services of another resource or resources.


• GRAPHQL A query language and runtime for completing API queries with existing data.


• HYPERTEXT TRANSFER PROTOCOL (HTTP) A protocol used to exchange hypertext. The foundation of communication for websites and web-based applications.


• INTEGRATION FRAMEWORK A lightweight utility that provides libraries and standardized methods to coordinate messaging among different software.


• IPAAS A set of cloud-based software tools that govern the interactions between cloud and on-premises applications, processes, services, and data.


• MESSAGE BROKER Middleware that translates a message sent by one piece of software to be read by another piece of software.


• MICROSERVICES Small, lightweight services that each perform a single function according to a domain’s bounded contexts. The services are independently deployable and loosely coupled.


• MIDDLEWARE A software layer between the application and operating system that provides uniform, highlevel interfaces to manage services between distributed systems; this includes integration middleware, which refers to middleware used specifically for integration.


• REPRESENTATION STATE TRANSFER A set of principles describing distributed, stateless architectures that use web protocols and client/ server interactions built around the transfer of resources.


• RESTFUL API An API that is said to meet the principles of REST.


• SERVICE DISCOVERY The act of finding the network location of a service instance for further use.


• SERVERLESS COMPUTING A cloud computing model in which a provider manages the allocation of servers and resources


• SERVICE ORIENTED ARCHITECTURE (SOA) An application architecture built around the use of services that perform small functions.


• SIMPLE OBJECT ACCESS PROTOCOL (SOAP) A protocol that is used by web services to communicate with each other, commonly used with HTTP.


• STATELESS SESSION STATE A session which no information is maintained between the sender and receiver.


• SWAGGER A definition format used to describe and document RESTful APIs, to create a RESTful interface to develop and consume APIs.


• WEB SERVICE A function that can be accessed over the web in a standardized way using APIs that are accessed via HTTP and executed on a remote system.