Skip to main content

SOA Governance to API Management - a pragmatic approach

Service Oriented Architecture or SOA has been one of the turning points of enterprise IT architecture where it provided the clarity and the order that was missing initially. Then it evolved through the SOA governance to become a well managed and governed IT ecosystem. Once the APIs started to dominate the enterprise architecture, API management has come to the forefront with SOA governance fading away. It didn't happen overnight and there are a lot more to organizations still trying to figure out what is best for them. 

This article discusses

  • What is SOA governance?
  • What is API Management?
  • How SOA governance and API Management live together?
Please find the link to the full article below.

https://medium.com/solutions-architecture-patterns/soa-governance-to-api-management-a-pragmatic-approach-4421a609d015?sk=de16c6ad82f320b4a23ef46de21ba9f8


Labels:

Comments

  1. donnaj edwardsFebruary 5, 2021 at 11:36 PM

    This is a really informative knowledge, Thanks for posting this informative Information. Apple Developer Login

    ReplyDelete
  2. E Square System and TechnologyMay 7, 2024 at 4:52 AM

    System integration services involve the process of connecting various disparate IT systems and software applications within an organization to ensure seamless communication and data sharing. This involves integrating hardware, software, networking technologies, and other components to create a cohesive and efficient system. System integration aims to streamline operations, improve productivity, enhance data accuracy, and facilitate better decision-making by enabling different systems to work together harmoniously. It often involves tasks such as data migration, application integration, API development, and customization to meet specific business needs. Overall, system integration services play a crucial role in optimizing organizational processes and leveraging technology to achieve strategic goals.

    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

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte...
6 comments
Read more