canmove, Confirmed users
1,394
edits
ReleaseEngineering/Development Best Practices: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Development Best Practices (view source)
Revision as of 22:31, 20 November 2013
, 20 November 2013→Performance
| Line 92: | Line 92: | ||
= Performance = | = Performance = | ||
Systems don't really scale up very well anymore: you can't get substantially faster processors, faster disk, or faster network. So build your application to scale horizontally -- by adding more instances. | |||
This is easy for a webapp, as webapps must be designed from the start to run across multiple webheads. But it's important for a service, too. Multiple hosts, particularly if they are not in the same location, can achieve both scalability and availability. | |||
Multi-threading can help with performance on a single host, but is really only useful in IO-bound situations, where the threading model makes it easy to deal with blocking operations. | |||
= Configuration = | |||
Applications should read from a single config file, generally in a ConfigParser-compatible format. It's also OK to use YAML. JSON is frowned upon because some parsers are too picky (e.g., about trailing commas). | |||