Enterprise Integration for Beginners

Streaming analytics has been one of the trending topics in the software industry for some time. With the production of billions of events through various sources, analyzing these events provides the competitive advantage for any business. The process of streaming analytics can be divided into 3 main sections. * Collect — Collecting events from various sources * Analyze — Analyzing the events and deriving meaningful insights * Act — Take action on the results WSO2 Stream Processor (WSO2 SP) is an intuitive approach to stream processing. It provides the necessary capabilities to process events and derive meaningful insights with its state of the art “Siddhi” stream processing runtime. The below figure showcases how WSO2 SP acts as a stream processing engine for various events. Source:  https://docs.wso2.com/display/SP410 With the WSO2 SP, events generated from various sources like devices, sensors, applications and services can be received. The received events are process

Microservices Architecture (MSA) is becoming the SOA of the modern era. Like the way SOA improved the enterprise software architecture with new patterns and architectures around that, Microservices Architecture (MSA) has tripped off several new architectural styles and new concepts around how people build enterprise software. Some of them are - Service Mesh — Technique to communicate amongst microservices - Serverless — Running your code as functions on cloud - Micro Integration — Run your integrations as microservices - Micro Gateway — Run your api gateways in a microservices compatible manner All these architectures can be categorized under the common umbrella of “microservices” and can be called as “micro-architecture”. In this post, I’m going to introduce the micro-architecture and how Micro API Gateway can be utilized in such an architecture.                                   Figure 1: Micro Architecture As depicted in the above figure, micro architecture is indep

WSO2 Identity Server Architecture WSO2 Identity Server a.k.a WSO2 IS is a fully fledged Identity and Access Management (IAM) solution which provides capabilities for your enterprise to secure your resources. The product is build with a rather simplistic but powerful architecture to support variety of identity and access management requirements. Below figure explains the high level architecture of the WSO2 Identity Server. Figure 1: WSO2 Identity Server Architecture The main components included in the above figure are explained below. Service Providers - These are the applications which needs to be secured using WSO2 IS as the authentication and authorization framework. This includes your mobile applications, web applications, SaaS applications, etc. Inbound Authentication - This component deals with various protocols like SAML, OIDC, WS-Federation, OAuth, etc. which are used to authenticate the users by the service providers (applications). Authentication Framewor

Let’s say you have a URL which needs to send an email address as a query parameter. If you create a standard REST API within WSO2 ESB (or EI) and try to match the query parameter in uri-template, it will fail during the execution time. As an example, if you have the below API definition. <api xmlns="http://ws.apache.org/ns/synapse" name="EmailAPI" context="/voice"> <resource methods="POST GET" uri-template="/details?email={email}"> <inSequence> <log level="full"> <property name="EMAIL" expression="$url:email"/> </log> <respond/> </inSequence> </resource> <resource methods="POST GET" uri-template="/phone/{number}"> <inSequence> <log level="full"> <property name="PHONE" expression="$ctx:uri.var.number&qu