Friday 17 March 2017

IBM open sources the API Microgateway

I am thrilled to announce the The IBM API Microgateway is now open source and available on GitHub. The API Microgateway has two powerful features developers will love:

  • A Node.js extensible and dynamic API policy flow engine based on Swagger that provides built-in policy support for OAuth 2.0 and rate limiting
  • NGINX industry-proven reverse proxy capabilities combined with Node.js highly scalable event-driven architecture

Why use an API gateway?

API gateways play an integral role to protect, enrich, and control access to API services. They allow you to architect your application in a way that provides clear separation between your business logic and security logic. In the long run, this will reduce application errors and provide a common reuse layer across your application.

Diagram of an API gateway

The API Microgateway policy flow engine 

Developers can use policy constructs (if / switch) to create visual policy flows, transform payloads, and invoke backends. When you need to roll up your sleeves and apply your own logic, the JavaScript policy provides ultimate flexibility to enrich the payload. The API Microgateway provides developers a first-class framework for building your own gateway solution to meet your API needs.

Building a gateway solution

Our community-first approach

The IBM Gateway team has over 15 years of experience in building gateway solutions. Our gateway offerings range from DataPower, an enterprise-proven gateway solution with comprehensive built-in policies, to the lightweight, infinitely extensible, open source The API Microgateway. 

We are excited to contribute our gateway expertise back to the community. The Node.js community is one of the most active and vibrant developer communities, and we are confident that with the help of the Node.js community, we can further evolve The API Microgateway.

For more information, check out The API Microgateway on GitHub.

The post IBM open sources the API Microgateway appeared first on developerWorks Open.

Read the full article here by developerWorks Open

No comments: