When Is It Best To Use A NodeJS Based API Proxy over The Apigee Simple Proxy?

Not applicable

I wanted to better understand when a business should consider using the Apigee Simple Policy Proxy vs a NodeJS based proxy?

For future development is there more benefits with one over the other?

Are there any pros and cons for using one over the other?

Thanks so much!

1 1 386
1 REPLY 1

Hi @Stephen, Mostly NodeJS proxies are used when you have some complex logic in your APIs. As long as you are able to achieve your requirements with out of the box policies with Simple Proxy, you should stick to it.

Some common use cases include:

  • Build highly customized standalone APIs and backend services.
  • Build backend logic for API BaaS to leverage cloud data storage and management, user management, push notifications, and more.
  • Solve complex orchestration and mobile optimization problems using Apigee policies with the advantage of a scriptable target endpoint.
  • Build composite services and mashups.
  • Rapidly develop prototypes of new APIs using frameworks like express, usergrid or NPM modules that are readily available to do the job.

Please refer the best practices page of Apigee to gain more insight on API proxy development here.

http://docs.apigee.com/api-services/content/best-practices-api-proxy-design-and-development

Cheers!