Skip to main content

RESTful SOA !

It is common that whenever we talk about SOA, immedietly our discussion will jump into web services, SOAP, WS-* etc. In fact, for many of the techies, SOA mean SOAP and web services. They very rarely give due weighatge to the business side of it. Interestingly, in the recent days more awareness about significance of HTTP in SOA is growing and hence it resulted in more adoption of RESTful services for service enabling applications & business logic than sticking to SOAP/RPC web services. The XML metadata information and SOAP headers associated with webservices are considered to be an overhead than the HTTP headers. When HTTP itself is providing all facilities for an efficient, secured consumption of business logic & data, contractual SOAP web services is loosing its position as a key technology option for enabling services. It is witnessed by the fact that key players in the web like Google, Amazon, Digg, Flickr & Twitter are exposing RESTful services.

Plain Old XML (POX) and Java Script Object Notion (JSON) are the key data formats available from RESTful services. When it comes for data consumption by a machine or application code, JSON is preferrred option over POX because of its smaller foot print. It is also the preferred option for consumption by AJAX applications.

From the development perspective, in Microsoft.Net platform, multiple options are available for developing RESTful services. Either we can leverage Windows Communication Foundation (WCF) or ASP.NET MVC.

So in future, whether we will service enable our applications only through RESTful services or SOAP web services will still exist? We should wait and see.

Comments

Popular posts from this blog

Lambda Architecture on Microsoft Azure

Gone are those days when Enterprises will wait for hours and days to look at the dashboards based on the old, stale data. In this fast world of BYOD, fitness gears and flooding of other devices, it is becoming super important  to derive out “actionable” information from huge volume of data / noise that is generated from these devices or any other data sources and act proactively on them  in real-time, to stay competitive.

At the same time, the need for having dashboards and other analytical capabilities based on the quality, cleansed, processed data still very much exists.

With the emergence of more data types and need to handle huge volume, shift is happening from the conventional data warehouse practice to cloud based data processing & management capabilities where high volume batch processing is possible at the optimized cost. Business scenarios demanding the need to process the data in real-time   More

SharePoint 2013 Architectural Trade-Offs

When planning for deploying SharePoint 2013 based Enterprise workloads, it should be done with the consideration / awareness of impact of various architectural decisions what we make. As SharePoint 2013 is a flexible platform providing lots of options in terms of configuration of the existing OOB features and development of custom development solutions to address specific business functional needs, care should be taken when making a particular decision and its impact on overall solution. Even though SharePoint is a matured product, the effectiveness of various business capabilities such as Enterprise Social, Enterprise Search, BI, Document Management, Web Content Management, and Enterprise Content Management that will be delivered based on it, in terms of addressing the business requirements depends on architecture planning. Effectiveness here means performance, security, up-time and other architectural qualities like Scalability, Reliability etc. more ...

Flexibility through product customization - How Secured it is ?

When providing solutions based on the multiple products, the success of the solution depends on what level of OOB features of those products helps in addressing the business / functional needs and what level of flexibility those products offers in terms of customization.

Also, how those products help in addressing business needs is very important in terms of time-to-market through:
Capabilities for seamless integration with federated business partners through adapters (like what Microsoft BizTalk, & StreamInsighthave rich set of adapters minimizing the development time), Partner ecosystem with solutions(like what partners have solutions basedon SharePoint in addressing various business requirements such as document storage, DRM / IRM, BI etc)
In addition to above mentioned factors, success depends on how the products allow developer community in extending its capabilities to address complex techno-business requirements.
While allowing the developer community for customization, it is a…