Enterprise Integration for Beginners

Database technologies are growing at a somewhat slower rate than other technology areas. But still, it is a major component of any enterprise software architecture. Due to the lack of innovation in the user experience side of the database technologies and the amount of “fear” people having when exposing databases to the end users have put the databases into a corner within the enterprise software systems. If you need to access a particular data set from a database table, you need to go through several layers and go after DB admins to get your work done. Databases have become the “precious” things in the enterprise. But do you need to be that way forever? The below medium post explains how databases can be exposes through a managed API which will democratize the database access within your enterprise. https://medium.com/wso2-learning/how-to-expose-your-database-as-a-managed-api-with-wso2-in-10-minutes-c9ac2595738b

WSO2 API Manager has become a leader in the API Management space according to the latest Forrester Wave report which was published on 30th October 2018 (Q4, 2018). This announcement has marked a significant landmark on open source development where all the other vendors in the leaders' section are proprietary vendors. In the below medium post, I discuss about what are the important aspects of this announcement to the enterprise software world and the open source community. https://medium.com/wso2-learning/how-wso2-api-manager-is-leading-the-open-source-pack-34277ad1a80f

Continuous Integration and Continuous Deployment (CI/CD) has become a core requirement within the enterprise IT ecosystem. It does not matter what type of software you develop (e.g. back-end services, UI/UX, APIs, middleware), you should be able to automate your development, test and deployment process. WSO2 ESB is one of the popular open source integration solutions available for implementing middleware services. The below mentioned medium post discusses how to implement a CI/CD pipeline with WSO2 ESB. https://medium.com/wso2-learning/how-to-build-a-ci-cd-pipeline-for-wso2-esb-wso2-ei-1f7ba3cc833d

WSO2 updates are delivered through open source and commercial channels to make your WSO2 deployments perfroming at best level. This is my latest article on the WSO2 updates and how you can utlize them to build great software systems which are upto date and upto great! https://medium.com/@chanakaudaya/understanding-wso2-product-updates-and-open-source-release-model-1bcedcb8c942  

Enterprise Application Integration (EAI) is a complex problem to solve and different software vendors have produced different types of software products like ESB, Application Server, Message Broker, API Gateways, Load Balancers, Proxy Servers and many other forms. These products have evolved from a monolithic, heavyweight, high-performing runtimes to lean, modularized, micro-runtimes. Microservices Architecture (MSA) is having a major impact on the way architects design their enterprise software systems. The requirements which were there 10 years ago has been drastically changed due to modern advancements of MSA, Containers, DevOps, Agility and mainly due to crazy customer demands.    The below post discusses the requirements which needs to be fulfilled by modern enterprise application integration projects.    https://medium.com/@chanakaudaya/understanding-the-modern-enterprise-integration-requirements-4ae58913a59d    

I wrote a medium post on how to build a fully automated CI/CD process to develop APIs with WSO2 API Manager. The original post can be found in the below link. In this post I'm discussing about how to utilize WSO2 API Manager product level APIs to implement the continous integration (CI) and continous deployment (CD) aspects within your enterprise ecosystem and how that can be fully automated with tools like GitHub and TraviCI. https://medium.com/wso2-learning/building-a-fully-automated-ci-cd-process-for-api-development-with-wso2-api-manager-d787431110aa

WSO2 API Manager is one of the leading open source API management platforms available in the market. According to a recent Gartner research (2018) it has been identified as the best “visionary” type vendor in the market. It comes with a support for full API lifecycle management, horizontal and vertical scalability and deployment options of on-premise, public cloud (SaaS) and managed (private) cloud. In this article, I’m going to discuss about how you can implement a service mashup (or service orchestration) with WSO2 API Manager within 10 minutes. Let’s get started by downloading the WSO2 API Manager from the following link. https://wso2.com/api-management/install/ Once you downloaded the product, you can install it to the desired location. Let’s consider the directory which WSO2 API Manager is installed as “APIM_HOME”. You can start the product using the following command within the APIM_HOME directory. $ sh bin/wso2server.sh Before implementing the use case, let’s understand the sce

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig

In the first part of this tutorial, I have explained about the concepts around WSO2 Stream Processor and how they are correlated with each other and which components users can use to implement their streaming analytics requirements. It laid out the platform for this tutorial (part 2) where we get our hands dirty with WSO2 SP. The first thing you have to do is download the WSO2 SP runtime from WSO2 website. https://wso2.com/analytics/install Once you download the product distribution, you can extract that into a directory and run the product from the bin directory. You need to set the “JAVA_HOME” environment variable to your java installation (1.8 or higher) before starting the product. In this part of the tutorial, we are going to implement some streaming analytics use cases with WSO2 SP. Hence we need to start the SP in “editor” mode using the following command (for linux). $ sh bin/editor.sh This command will start the editor profile of the WSO2 SP and prints the URL of the

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