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

What happened to the parse core built with Go? #27

Closed
jyoon17 opened this issue Jan 29, 2016 · 5 comments
Closed

What happened to the parse core built with Go? #27

jyoon17 opened this issue Jan 29, 2016 · 5 comments

Comments

@jyoon17
Copy link

jyoon17 commented Jan 29, 2016

In the past, you guys proudly announced that the core API server was rewritten in Go and I was really thrilled to see how you did it when I first heard the news. But now we have source code in Node.js out of nowhere..

Are you guys rewriting all the source code again?

@yuki-takeichi
Copy link
Contributor

This is "Parse-compatible" API server. I guess it's totally different from Parse internal.

@lacker
Copy link
Contributor

lacker commented Jan 29, 2016

The core API server is actually solving a lot of additional problems, because it's essentially massively multitenant. One server could handle a whole bunch of apps and deal with various operational edge cases. It's also entirely separated from cloud code / per-app javascript. Best practices for running your own server for a single app are pretty different. For someone running a single app, I don't think it would be the ideal fit to be running a go binary, plus separate custom js code in node.js. This setup seems far superior. And the code can be way, way simpler if it's just reimplementing a bunch of the Parse API rather than additionally porting a bunch of extra operational/logging stuff that only makes sense in a massively multi-app case.

@lacker lacker closed this as completed Jan 29, 2016
@AhmadBaracat
Copy link

@lacker It would be great if you can tell me which one were you using in production, the Node.js or the GO server? or where you using a GO server that initiates/spawns Node.js?

@nige123
Copy link

nige123 commented Jun 10, 2016

I'm interested in this too? @lacker could you please outline the relationship between Go and Node.js in your running setup?

@lacker
Copy link
Contributor

lacker commented Jun 10, 2016

Parse.com runs the go server in production. By now there are also a lot of people running Parse Server in production as well, but not on parse.com.

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

5 participants