The document discusses building configurable web applications. It recommends making as many aspects of an application configurable as possible without changing code, such as hostnames, database names, timeouts and display settings. This allows applications to be deployed across multiple platforms and environments without redeploying code. The document also stresses the importance of writing debuggable and defensive code to make applications more stable and operable in different states.
As infrastructure, I’m responsible for building backend components as well as telling everyone else why their components don’t work. We’ll talk more about that during the presentation
It means a lot to me. I’m using the term configurable “loosely”
No big ideologies or frameworks here. If you want to go on vacation and/or work on cool stuff, give others the power to control your app so they don’t need to come to you.
Unique states used for debugging or bucket testing for example. We’ll definitely be sloped toward site availability in this talk but these are all important
Or maybe you’re a small company or startup or a manager who has engineers that are overworked and deadlines that are too tight.
Build info into your app and your process to let others manage it effectively. This is not a selfish endeavor; we all want to spend more time doing the fun things in programming like coding and design. Not triage.
You won’t get the bang for the buck if you don’t have this. You want have the power to quickly and reliably deploy fixes, configuration changes and even roll back. In the same vain as what Sebastian said yesterday, “You want to make deployments a non-event”. This is hard, as in order for them to truly be routine, you need extensive automated testing and such in place. But, the first thing you need is the mechanism to actually build the host.
We want to have a baseline as to how much you can handle. something like siege, ab, http_load
Twitter – don’t forget the API
Getting this on the table early is important. You’re doing this with wireframes, right? Once everyone knows at what points these things happen, discussions can begin as to what to do at those points and how to mitigate them
High value low cost: if something is a priority 3 but really expensive resource-wise to produce you might want to take that early on, especially if you are expecting increased traffic
Go over Defcon levels. Defcon levels also have business procedures as well (Notify XYZ of situation, etc.). Your priority list serves as the basis as to what levels and knobs to engage. Example Level 4 for News: Emmy awards, MJ tribute. Level 3 is where we plan on degradation of service based on expections, Level 2 is where we implement degradation of service
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Lets also talk about defensive code a bit
Lets also talk about defensive code a bit
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Flesh this out, talk about a db or web service that isn’t there. Yes, you can fetch it from the cache but you shouldn’t try to connect to it if it likely won’t be there
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
Application defaults, you shouldn’t hardcore ‘5’ in the SQL query to determine how many blog posts to fetch. Display settings you want those sorted by date, or maybe even what fields are displayed?
As infrastructure, I’m responsible for building backend components as well as telling everyone else why their components don’t work. We’ll talk more about that during the presentation
![Building configurable applications for the web ,[object Object],[object Object],[object Object],[object Object],Tom Melendez, Yahoo!](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)