Skip to main content

Building a reusable API platform with WSO2

API driven digital economy is here to stay. Whether you like it or not, you have to embrace that if you have plans to stay along with the competition in your respective domain. But API adoption comes at a cost. Depending on which vendor you are going to choose, you will end up with a considerable cost. Good things do not come easy and they are not free. It is a given that you have to spend some amount of money to get things going in terms of the API driven business. But the real problem is that, what is the benefit you get out of that investment? How long will it take to show some benefits? These problems are nothing new to business leaders since they deal with these sorts of problems day in day out.

This article discusses

  • What is Reusability in enterprise IT landscape?
  • What is API Development?
  • How Reusability is affecting in development?
  • What are API Marketplaces?
  • How Reusability is affecting in API consumption?
  • Benefits of API Reusability
You can find the link to the full article below.

https://medium.com/wso2-learning/building-a-reusable-api-platform-with-wso2-api-manager-bfd1273b8b57?sk=e1487c948e89aaaede3093db7cf21d8c


Labels:

Comments

  1. E Square System and TechnologyApril 8, 2024 at 4:53 AM

    System Integration: Building Bridges for Seamless IT Operations
    System integration services, such as IT Matching, connect the various computer programs and databases they use, allowing them to work together. This means information flows easily between them, saving you time and effort.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

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...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
Read more

WSO2 ESB usage of get-property function

What are Properties? WSO2 has a huge set of mediators but property mediator is mostly used mediator for writing any proxy service or API. Property mediator is used to store any value or xml fragment temporarily during life cycle of a thread for any service or API. We can compare “Property” mediator with “Variable” in any other traditional programming languages (Like: C, C++, Java, .Net etc). There are few properties those are used/maintained by ESB itself and on the other hand few properties can be defined by users (programmers). In other words, we can say that properties can be define in below 2 categories: ESB Defined Properties User Defined Properties. These properties can be stored/defined in different scopes, like: Transport Synapse or Default Axis2 Registry System Operation Generally, these properties are read by get-properties() function. This function can be invoked with below 2 variations. get-property(String propertyName) get-property(String scop...
Post a Comment
Read more