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

Suggestion: Make A Blueprint of Architecture of Parse-Server #4615

Closed
trylovetom opened this issue Mar 9, 2018 · 4 comments
Closed

Suggestion: Make A Blueprint of Architecture of Parse-Server #4615

trylovetom opened this issue Mar 9, 2018 · 4 comments

Comments

@trylovetom
Copy link
Contributor

parse-server is a very large project now. It might help to have a blueprint of architecture of parse-server in CONTRIBUTE.md for the new contributor.

Suggestion Context

  1. Concept of Architecture
  2. Detail of Architecture. something like Adapter interface or module description.
  3. Roadmap
@dplewis
Copy link
Member

dplewis commented Mar 14, 2018

There's the Development Guide in the Wiki. It could be overwhelming to new contributors.

We could have some kind of visual graph like in the PHP Class Diagram or Developer Roadmap

I usually follow this generic flow especially for queries. We can definitely expand on this for the detail of the architecture. We could leverage the test specs as they separated.

middleware -> router -> rest -> controller -> storageAdapter

As far as a Roadmap, sadly there isn't one. A previous discussion was opened Roadmap

I do have my own personal roadmap.

  • Unique Indexes
  • GeoPoint 2dsphere Indexes
  • Add indexes to Parse Dashboard
  • Ram Usage / MongoStats to Parse Dashboard
  • Make Dashboard usable on Mobile
  • LeftJoin on Pointer and Relation
  • IncludeAll Pointers
  • Sample (Random Object) Query
  • MySql Adapter update
  • Neo4J Adapter
  • Adapter Test Spec
  • New Adapter Guide
  • Let's Encrypt
  • Field Validation / Private Fields via Schema
  • .NET Live Queries

@flovilmart
Copy link
Contributor

flovilmart commented Mar 14, 2018 via email

@dplewis
Copy link
Member

dplewis commented Mar 14, 2018

@flovilmart Most them already have issues opened. They are just hidden in the leaves.

private fields via schema api #1547 (comment)
field validation via schema api #1547 (comment)
More database adapters #20
Live Query Subscribe to specific events #3841
LetsEncrypt #33
Randomly get objects from mongo #818
.NET Live Queries

@stale
Copy link

stale bot commented Sep 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

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