Wednesday, 25 April, 2018 UTC


Summary

For medium sized apps and above, monoliths are really bad - having one big software with many dependencies is just hard to reason about and often leads to spaghetti code.The ultimate solution is to develop small software: divide the whole stack into self-contained components that don't share files with others, each constitutes very few files (e.g. API, service, data access, test, etc.) so that it's very easy to reason about it.I will show you how to maintain the project structure by using feature by feature approach. Each feature will have controller, router, and service file.