You are viewing a single comment's thread from:

RE: Dev Portal Update: Tutorials, Recipes, and Tweaks, Oh My!

in #devportal6 years ago (edited)

If you want to do a real cost-benefit here, you'll have to compare actual work on both sides, but then also weigh what you're getting.

I'm basically saying that the amount of work to build the same functionality currently in jussi, but in kong would be less simply because

  1. It's lua
  2. Plugin infrastructure exists for future improvements and extensions
  3. Multiplexing builtin.
  4. Reverse Proxy builtin
  5. Throttling builtin
  6. Authz/Authn builtin
  7. FaaS builtin
  8. Microservice awareness builtin
  9. You just get so much stuff for free you don't need to build anymore and you can just concentrate on building blockchain stuff

Also, it's not just better because the work would be less, but the benefits are greater

  1. Simplified infrastructure
  2. More flexibility design and implementation
  3. Maintained by another community (you just focus on you)

Whenever the question is "Should we reinvent the wheel?" the answer is almost always, "no".

Sort:  

You should totally write that plugin.

Actually, I had started a kong plugin, but it's not for this. It's for pricing out app access to private nodes. Another reason why I would really like "full-blown" kong support.

It's on my list. Just after "super suit."