By Fernando G.
Overview
First off, we need to have a quick overview of what REST means to the development community, and we can start by what does REST stands for? It stands for Representational State Transfer. Right, it did not help a lot, right?
In the SOA era, we have Service Oriented Systems interacting between them exposing Services, some applications act as consumers and some as producers. At the end, a Service Oriented Architecture allows an organization to create a well thought and organized set of libraries being used uniformly among all of the participants with no redundancy of business rules and specially having a single set of Services. Well, not always the case. It results extremely painful when the Services are done in different technologies; Interoperability between the different implementations is the major issue among Service consumers and producers. Another problem is that development teams do not take in considerations to other areas of the company. This ends up with duplicate Services because they do not provide what the potential consumers need, it is too painful to reuse.
Well, REST style architecture is one alternative to SOA. REST is all about identifying Resources and not Services. These Resources are Stateless, Cacheable and in consequence are stable, scalable, with high performance and simple.
Asp.Net MVC
Microsoft saw a huge potential to MVC pattern for web development. They already tried with a library called Microsoft User Interface Process (UIP) implementation back in 2003, but it was not very popular among developers so it lost track and its last update was version 2 in 2004.
To read the complete story click here.
No comments:
Post a Comment