Permalink
Browse files

Merge pull request #3 from pealco/patch-1

Typo fix. spearate -> separate
  • Loading branch information...
2 parents 504531e + 2c3b3ce commit 32dca29d11d4682eeb8478d95d5cba6f83bb5af0 @aaronsw aaronsw committed Jul 1, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 index.md
View
@@ -123,7 +123,7 @@ If you're building a network service (e.g. a web application), you should design
4. All backing services (like databases or in-memory caches) are treated as services. No distinction is made between local and third-party services; they're all accessed over the network.
-5. Code is deployed in three spearate stages: build (in which the software is compiled and built), release (in which it's combined with the configuration environment and put onto the appropriate servers), and run (in which it's executed). These stages should be completely isolated -- the server can't change its configuration at runtime, since the release stage has already been passed. And the release process can't edit the software, since the build stage has already passed.
+5. Code is deployed in three separate stages: build (in which the software is compiled and built), release (in which it's combined with the configuration environment and put onto the appropriate servers), and run (in which it's executed). These stages should be completely isolated -- the server can't change its configuration at runtime, since the release stage has already been passed. And the release process can't edit the software, since the build stage has already passed.
6. The application should execute as a series of stateless processes that share nothing -- any process should be able to be killed at any time. This means any state needs to be stored in one of the backing services.

0 comments on commit 32dca29

Please sign in to comment.