diff options
Diffstat (limited to 'wiki/12factor')
| -rw-r--r-- | wiki/12factor/7-port-binding.md | 8 | ||||
| -rw-r--r-- | wiki/12factor/index.md | 4 |
2 files changed, 6 insertions, 6 deletions
diff --git a/wiki/12factor/7-port-binding.md b/wiki/12factor/7-port-binding.md index 2daf342..a756496 100644 --- a/wiki/12factor/7-port-binding.md +++ b/wiki/12factor/7-port-binding.md @@ -8,11 +8,11 @@ Factor 7 is over-specific: * It presupposes the existence of a front-end routing layer, without providing any insight into how to deploy, configure, provision, or manage one. -* It demands HTTP (by name) rather than a more flexible "any well-standardized - protocol", without explaining why. (Web apps can have non-HTTP internal +* It demands HTTP (by name) rather than a more flexible “any well-standardized + protocol,” without explaining why. (Web apps can have non-HTTP internal components.) -* It dismisses the value of "pre-existing" container ecosystems that don't +* It dismisses the value of “pre-existing” container ecosystems that don't work the way Heroku does. Have a giant, well-managed [Glassfish](http://glassfish.org) cluster that you deploy components to? TOO BAD, not Heroku-like enough for these guys even though many aspects run @@ -21,7 +21,7 @@ Factor 7 is over-specific: * It dismisses the value of unix-as-a-container. Unix domain sockets with controlled permissions? Psh, let's go through the network stack instead. SysV IPC? (Yeah, I know.) Network. Pipes? Network. There's an implicit - exception for "intra-process" communication, but it's never really + exception for “intra-process” communication, but it's never really identified or reasoned about. * Have you _seen_ the kinds of process control interfaces developers invent, diff --git a/wiki/12factor/index.md b/wiki/12factor/index.md index 9fa7e22..6e75732 100644 --- a/wiki/12factor/index.md +++ b/wiki/12factor/index.md @@ -1,7 +1,7 @@ # 12-Factor Apps Some folks over at [Heroku](http://heroku.com/) wrote up their perceived best -practices for building "software as a service"-style applications and called +practices for building “software as a service”-style applications and called it [The Twelve-Factor App](http://www.12factor.net). It's a good read, and has lots of good advice in it. @@ -15,5 +15,5 @@ I have a few thoughts on it. ----- At some point around sections 6 or 7, the goodness of the advice is overtaken -by the "be more like Heroku specifically"-ness of the advice, to the detriment +by the “be more like Heroku specifically”-ness of the advice, to the detriment of their point. |