Scaling :core:models: what's the strategy when models grow exponentially? #1972
Unanswered
AndresMaca
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I want to know your position regarding what would happen when the models start to grow exponentially. For now, it makes sense to have them in :core:models, but what will happen when the app has 200+ screens and models that are not related to each other? I understand that we want to keep a core:models which will hold common stuff and its reused over several features but I would like to learn a bit more about your vision on what happen next. How would the modularization look in that scenario? I think that the same question might be asked for the network layer.
imho features: module is on track to scale up.
This was my weekend side project, and I highly recommend it to anybody who wants to learn how real-life apps are built. Take your time and don't rush on it. Google fan since Udacity in 2014 <3 Thanks for the effort in keeping this available for the community. And thank you very much for taking the time to reply.
Andres.
Beta Was this translation helpful? Give feedback.
All reactions