Sign in with Facebook
Adam Wiggins’s Followers
None yet.
Adam Wiggins
|
The Twelve-Factor App
—
published
2012
|
|
* Note: these are all the books on Goodreads for this author. To add more, click here.
“The twelve-factor developer resists the urge to use different backing services between development and production, even when adapters theoretically abstract away any differences in backing services. Differences between backing services mean that tiny incompatibilities crop up, causing code that worked and passed tests in development or staging to fail in production. These types of errors create friction that disincentivizes continuous deployment. The cost of this friction and the subsequent dampening of continuous deployment is extremely high when considered in aggregate over the lifetime of an application.”
― The Twelve-Factor App
― The Twelve-Factor App
“Sticky sessions are a violation of twelve-factor and should never be used or relied upon. Session state data is a good candidate for a datastore that offers time-expiration, such as Memcached or Redis.”
― The Twelve-Factor App
― The Twelve-Factor App
“Twelve-factor apps also do not rely on the implicit existence of any system tools. Examples include shelling out to ImageMagick or curl. While these tools may exist on many or even most systems, there is no guarantee that they will exist on all systems where the app may run in the future, or whether the version found on a future system will be compatible with the app. If the app needs to shell out to a system tool, that tool should be vendored into the app.”
― The Twelve-Factor App
― The Twelve-Factor App
Is this you? Let us know. If not, help out and invite Adam to Goodreads.
