It is an intermediary between API consumers (clients) and backend API providers (API servers). We’ll delve more into these in a moment but first, let’s explain the often overloaded term “gateway”… OverviewĪn API gateway externalizes, secures, and manages APIs. It will also require some major enhancements to the LoopBack framework, including LoopBack components and policies. Its behavior is completely “hard-wired.” In the future, we’ll release a commercial product, the StrongLoop API gateway, that will be dynamically configurable. The LoopBack Gateway is open source and is the “minimum viable product” (MVP) that covers key use cases piloted with our co-development partners. What’s LoopBack? It’s an open source Node.js framework for developing, managing and scaling APIs. So, we captured customers’ requirements and also determined that the Gateway would use both declarative JSON as well as Node API calls. It’s been quite a while from the time we added a “Gateway” box in our architectural diagram marked as a “work in progress.” Before starting development, we wanted to gather customer use cases to make sure it addressed real-world needs.
This morning, we released the open-source version of the LoopBack API Gateway. Read this announcement blog to learn more about the latest version. Note: Since the publication of this blog, the StrongLoop API Gateway was relaunched on August 5, 2015.
0 kommentar(er)
