Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using expressjs in api #53

Closed
oroce opened this issue Feb 10, 2013 · 1 comment
Closed

using expressjs in api #53

oroce opened this issue Feb 10, 2013 · 1 comment
Assignees

Comments

@oroce
Copy link
Contributor

oroce commented Feb 10, 2013

Is there any reason not to use expressjs in api?

It would be nice to use because:

  • easier read
  • easier to maintain
  • frontend could mount the api, so countly could be deployed without any proxy
@ghost ghost assigned osoner May 18, 2013
@ar2rsawseen
Copy link
Member

The main concern was and is performance. Due to high load of data our users have, api must be as efficient as possible. And some test show that express.js is quite inefficient: https://raygun.io/blog/2015/02/node-js-performance-node-js-vs-io-js/

Plus since plugins branch, plugin mechanism is quite deeply integrated with current api structure, so for now I don't see that we would rewrite api to express.js in near future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants