www.subelsky.com
FEBRUARY 25, 2010
Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuous deployment system. This keeps us from having to hit our database too much. If a release goes out and suddenly there are new errors, thats a sign that the batch was bad and needs to be reverted.
The Next Web
AUGUST 6, 2013
Zappos could have gone off and built distribution centers, a large database of footwear, and inventory systems for shipping shoes. They didn’t validate their business model before investing so much in it and under-estimated the “last mile” problem. Contrast this to Zappos. Can it work for an enterprise software company?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
NOVEMBER 13, 2008
Wish I could figure out how to apply it to the average data warehousing project which has a single shareed database right at the heart of the entire solution. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JANUARY 4, 2009
Data storage is becoming a specialized function, delegated most often to relational databases. If you are storing all of your data in a relational database, and the load on that database exceeds its capacity, there is no automatic solution that allows you to simply add more hardware and scale up.
Startup Lessons Learned
SEPTEMBER 10, 2008
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Do you have a bug database?
Startup Lessons Learned
SEPTEMBER 30, 2008
Massive proprietary databases? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. I dont think so. Can the company dig into its tools when they fail and fix them?
Startup Lessons Learned
OCTOBER 20, 2008
*All* of the factors involved in delivering software are affected by starting with baseline requirements that are constrained to what the system should do and the process artifacts desired (say 5 forms reading and writing a database store). Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
41 
Let's personalize your content