article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

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.

article thumbnail

8 Must Have Tools For Your Next App Build

YoungUpstarts

Docker containers support CI (continuous integration) and CD (continuous deployment) implementation. It allows developers to build their code collaboratively through image sharing while simplifying deployment to separate infrastructure. Docker Enterprise integrated the CI/CD pipeline into a secure software supply chain.

Java 127
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: A hierarchy of pitches

Startup Lessons Learned

Their idea was to build a next-generation autonomous robot, that could be used by defense and security agencies around the world. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

article thumbnail

John Doerr's 10 lean startup tips

Startup Lessons Learned

All cash in most secure possible instruments. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Everyone from the receptionist to engineers is selling. Offer equity instead of cash.

Lean 121
article thumbnail

Minimum Viable Product: a guide

Startup Lessons Learned

Most enterprise customers do NOT want frequent releases for two main reasons (1)They have heavy internal release processes: long QA cycle, security reviews, etc; and (2) It is costly to communicate and educate their own customers about a new set of features. Case Study: Continuous deployment makes releases n.

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Most of this was code that not scalable, not secure, and not particularly extensible. 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?

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

I remember once being asked in a Microsoft group interview (and dinner) about the ActiveX security model. I remember answering "What security model?" Turns out, I had been lecturing the creator of the ActiveX security model. Case Study: Continuous deployment makes releases n. At first, I thought I was doing well.