Blog Post

Managing artifacts of a service oriented solution is one of the most important features expected from any SOA middleware platform. In a typical service oriented project, SOA artifacts are subjected to move through multiple phases. Usually, separate environments are maintained for the activities associated with those phases.

Read the full story in Charitha's blog.

WSO2 Application Server mainly supports hosting Web Services and Web Applications. One of the major features included in the upcoming release (version 4.5.0) of WSO2 AS is the integration of Apache CXF. So from AS 4.5.0 on-wards, CXF users also will be able to host their applications inside WSO2 AS with great ease. Once you deploy your CXF application inside WSO2 AS, it automatically inherits lots of benefits from the underlying WSO2 Carbon platform.

Read the complete blog post at Isuru's blog.

A middleware platform on premise can be used to host the applications that are developed for the use of the departments in the organization. A cloud middleware platform, on the other hand, can be used to replace the set of middleware platform servers that are deployed for the servers. A cloud middleware platform can be hosted as a public or private cloud for the organization's requirement utilizing the cloud middleware platform's cloud-native attributes. This blog post looks into the Platform, cloud middleware platform, and the Platform as a Service.

Unlike static server capacity measurements (e.g. CPU processing speed, memory size), performance is a dynamic measurement. Latency and throughput are strongly influenced by concurrency and work unit size. Larger work unit size usually negatively influence latency and throughput. Concurrency is the number of aggregate work units (e.g. message, business process, transformation, or rule) processed in parallel (e.g. per second). Higher concurrency values have a tendency to increase latency (wait time) and decrease throughput (units processed). Read Srinath's full blog post.

All Enterprise Service Bus (ESB) products may be used to build and deploy services, encapsulate legacy systems, route messages, transform message formats, and perform protocol mediation. Many WSO2 prospects ask me ‘What differentiates WSO2 Enterprise Service Bus?’ This blog post shares my perspective and scales the conversation.

Continue reading Chris Haddad's blog.

Ability to store a message in a temporary storage is a fundamental requirement in many enterprise integration scenarios. There are many occasions where a systems integrator would have to design a message flow which simply dumps all the messages into some kind of a storage facility for later retrieval. Here are several scenarios that I’ve encountered while working on real-life integration projects which required me to consider using an intermediate message store:..

Read the complete blog post.

Load Balancer is a crucial component in scalable architectures. WSO2 Load Balancer not only balances the load across the application instances, but also scales the system automatically to cater the dynamically changing load. WSO2 Load Balancer is a WSO2 Carbon based product. In this post, we will look how autoscaling works with the Load Balancer.

This post gives an introduction to StratosLive, the Platform as a Service (PaaS) offered by WSO2. If you are a SaaS application developer, architect, researcher, or an enthusiast on cloud computing, searching for an enterprise ready PaaS, StratosLive is the answer for you.