Startup Lessons Learned
JUNE 15, 2009
Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Startup Lessons Learned
SEPTEMBER 30, 2008
If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? That means knowing whats written and whats not, what the architecture can and cant support, and how long it would take to build something new. Thats more than just drawing architecture diagrams, though.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JULY 29, 2009
Outside the world of hypothetical examples, its more important to make continual progress than to build the ultimate design. For example, at a previous virtual world company , we spent years developing an architecture to cope with millions of simultaneous users. That’s what Just-in-time Scalability is all about. One last thought.
Startup Lessons Learned
APRIL 26, 2009
Open APIs and data-oriented architecture (aka "web 2.0"). It allowed me to assess the market demand for that offline product before I had the final product baked. On-demand utility pricing for services (aka "cloud computing"). Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
OCTOBER 5, 2009
It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?
Startup Lessons Learned
NOVEMBER 13, 2008
It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
NOVEMBER 29, 2008
and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture? Case Study: Continuous deployment makes releases n. Using AdWords to assess demand for your new online. At the time, I was a die-heard Java zealot.
Expert insights. Personalized for you.
167 
Let's personalize your content