Automattic / Automattic/mongoose

further isomorphic features

Open
#3,061 11 comments 0 reactions 0 assignees View on GitHub
new feature
Dominant language
JavaScript
Stars
27.5k
Forks
4k
Avg merge
2d 7h
Merged PRs (30d)
35

Description

Hi,
I love mongoose, I think it's brilliant and I'm really excited about the isomorphic direction.

I thought that the next logical evolution that will make mongoose even much more awesome is to add client features similar to ember-data, breeze or orbit - namely the ability to query from the client, and to cache results by id so they don't have to be re-requested.

Has this been considered and if so how much further along is it? I'm trying to scope the best client data-layer and breeze is great, but it assumes a .net server and its node/mongo implementation would force me to not use mongoose on the server which is a deal breaker for me. If I could use mongoose on the client for querying and caching it would be a dream come true.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified. Start by reviewing Mongoose's existing isomorphic direction and comparing the requested client-side querying and ID-based caching with ember-data, Breeze, and Orbit; done would require an agreed design and defined scope for those capabilities.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mongodb, nodejs
Domain
databases, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.