WSO2 API Manager is used to manage, govern and monitor APIs. This is the second part of an article that describes how to configure data receivers and data publishers in commonly used patterns that provide scalability in how API traffic is handled by the system. You can read the first part here.
WSO2 API Manager is used to manage, govern and monitor APIs. Within any deployment, Traffic Managers handle throttle policy decisions. This article is the first part of a two-part series that describes how to configure Traffic Managers in commonly used patterns that provide scalability in how API traffic is handled by the system. You can read the second part here.
Today, microservice architecture (MSA) has become an important aspect for enterprises looking to make their businesses leaner and agiler. This article will explain how WSO2 API Manager can be leveraged to expose microservices and the benefits of adopting that strategy.
This article will provide an in-depth analysis of the data mapper mediator that comes with WSO2 Enterprise Service Bus (WSO2 ESB). It will discuss how the data mapper engine architecture integrates with the data mapper mediator and how it can be used with WSO2 ESB to configure mapping.
Previous versions of WSO2 API Manager used legacy throttling implementation that was subject to many changes; however, the most recent implementation is based on Hazelcast atomic counters that sync the local counters of each gateway to sum-up the clusterwide global count. A previous article gave an overview of the new feature. This article will provide a deep-dive into the new throttling implementation architecture.
A middleware component that is positioned between message producer applications and message consumer applications is called a Message Broker. A message broker’s role is to provide complicated message exchange patterns - things other than point to point, RPC-style communications: often this means decoupling parties involved in information exchange, enhanced delivery guarantees, security and so on.
With the advent of internet and network infrastructures, most software systems run on a cluster - and this is true for message brokers as well. Nevertheless, due to the asynchronous nature of communication and reliability factor it has to provide, clustering a message broker system is a challenge.