Library

For many enterprises, trust, or lack thereof, remains the most significant barrier to service-oriented architecture (SOA) adoption.

An SOA initiative is meant to knock down internal barriers and help an enterprise evolve from separate silos of technology and information into a leaner, shared-service organization. However, many application development leaders struggle to create a consistent service architecture that is widely shared, reused, and adopted across internal development teams. Instead, these teams often go rogue, ignoring SOA procedures and swapping out IT toolsets, message formats, and protocols to build their own solutions, which ultimately fail to support enterprise growth.

Read Chris's article on IT Briefecase

Representational State Transfer (REST) is an architectural style widely used to communicate over the web. In this model, each resource is uniquely identified by an URI and there are four operations - GET, POST, PUT and DELETE - defined for each resource. The HTTP protocol which is widely used in web communications nicely fit into this architectural model. Therefore we can easily implement Restful APIs and access them using the existing web infrastructure.

In order to provide the interoperability between the business entities, most organizations tend to expose their APIs as Restful services. However in most organizations the back end services may use different types of protocols as well as message formats. These system can be web services implemented with SOAP, some legacy systems like CORBA or some SAP system end points. A middleware layer, which can be used to implement Restful APIs integrating those back end systems, allow users to expose their APIs as Restful services easily.

In present world big data visualizations have become a vital part in corporate decision making. There are dozens of products emerging to analyze and visualize big data. There are vast variety of reporting tools and data analyzing tools. Through this article we are going to explain how to use WSO2 Business Activity Monitor with different reporting tools to analyze and visualize your data.

I’m excited about a new web application/web API development technology that WSO2 has been working on. Jaggery is a language for writing web applications, like PHP, ASP, JSP, and others. These technologies are pretty well established, so why do we need another one? I believe the demands of web applications have changed a bit over time and Jaggery offers a valuable refresh on web application development.

Read Jonathan's blog post