Skip to content
This repository has been archived by the owner on Jul 6, 2019. It is now read-only.

Scalability #16

Closed
mattfysh opened this issue Sep 5, 2013 · 2 comments
Closed

Scalability #16

mattfysh opened this issue Sep 5, 2013 · 2 comments

Comments

@mattfysh
Copy link

mattfysh commented Sep 5, 2013

Does it make sense to split the modules out into filters, services, directives, etc... how would that scale out for a large-scale JS app?

@tnajdek
Copy link
Owner

tnajdek commented Sep 5, 2013

Yes, for large-scale app I expect you would want to split filters, controllers etc. into separate files and use requireJS in development to get them into browser and for tests.

Now depending on how large your application really is you need to decide on what strategy you'll use for production. For most projects it would be use almond JS and build a single, minified version of a final delivery file (something I will include in future version of the project). However for really large applications where a combined, minified version would weight more than say 500K I would consider delivering your controllers and templates separately as needed.

Hope this helps a little, good luck with your project!

@mattfysh
Copy link
Author

mattfysh commented Sep 5, 2013

Thanks!

@mattfysh mattfysh closed this as completed Sep 5, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants