NatLabRockies / NatLabRockies/api-umbrella

Create strategic partnership with other open-source API proxies

Open
#159 45 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
2.2k
Forks
373
PR merge metrics
No merged PRs in 30d

Description

There are several emerging, open-source API proxy solutions. It may prove fruitful to share coding efforts, ideas, and lessons between projects.

Clyde IO

Clyde IO is just getting started. It is being built with Node.js and uses Connect middleware for filters.

Kong

Kong seems to be well conceived and is well documented. It is primarily implemented in Lua with some Python. It has a plugin architecture to provide common features such as authentication, logging, etc.

Tyk

The Tyk API Gateway has a similar ambition to API Umbrella. Tyk is primarily written in Go, with sprinkles of JavaScript and Shell. Tyk implements a middleware model, that may offer a common path to share code between projects.

Task

  • Contact the Clyde IO lead developer
  • Contact the Kong lead developer(s)
  • Contact the Tyk lead developer
  • Consider common, or intersecting, features between Clyde IO, Kong, Tyk and API Umbrella
  • Identify features different between Clyde IO, Kong, Tyk, and API Umbrella
  • Discuss how to merge, or unify, the projects - or at least coordinate development resources

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Clyde IO, Kong, and Tyk project pages and the remaining unchecked tasks in this issue. Compare common and differing features, then use those findings to support discussion about coordinating or unifying development; no repository file or test is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, javascript, lua, node.js, python, shell
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.