Chapter 12. Going into production
This chapter covers
- Organizing your code to ease deployments
- Integrating testing frameworks using Velocity
- Estimating and testing load
- Understanding deployment options, from simple to highly available
- Using Meteor UP to deploy an application
- Using environment variables to configure the server
- Architecting highly available architectures
When all features are implemented and all bugs ironed out, it’s time to go into production. This chapter covers all the essentials of deploying a Meteor application. We won’t go into the specifics of server administration, but we’ll explore typical architectures and possible options in regard to small as well as scalable deployments, so you know what to do when your app becomes a success.
In an ideal world, you’ll already have thought about the “go-live” of your application even before you started writing a single line of code. If you haven’t, now is the time to revisit expectations and requirements. You’ll notice that your deployment options are greatly influenced by the requirements you have. But because most of the largest applications started small as well, we’ll begin by looking at the simplest deployment scenarios and introduce larger scale and the complexity it introduces as a second step.