The Rationale Behind This Presentation
Traditional full-stack web frameworks (Laravel, Django, Rails and others) all adhere to a set of conventions that improve your workflow and productivity for certain tasks.
For a variety of reasons, most of which will not be discussed here, developers are willing to accept the limitations of these tools. It's a tradeoff between flexibility and development speed, and while frameworks will always force us to choose what's most important, what if we could build our application with smaller, more agile tools that reduced the impact of our choice?
What if you could build an application in many tiny pieces, where pieces of your architecture could be swapped out at a moment's notice? How would your team react if they were no longer tied to a single framework, and were instead empowered to use the best tool for the job at hand?
Presented here in the repo are several code examples that back up my Nodevember talk on this subject. Read through them, and feel free to ask any questions
Code
All code in this repository is released under the Beerware license. If you like it (or it helps you), give me credit, and buy me a beer (Half Acre, Metropolitan, 5 Rabbit, or Three Floyd's preferred).
Linked or included libraries are available under their own licenses.
Presentation
© 2014 Nicholas Young/Original Machine LLC. BY-NC-SA.
Dependencies
Any linked projects are released under their own licenses. Please see @OriginalMachine or @MachineFM for more details.