This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
We asked him a few questions to learn about continuous delivery, why it’s useful, and what engineers and management need to do to implement it. LSC: One of the biggest fears people have about a continuousdeployment environment is that it introduces more risk to engineering. Thus we reduce the risk of deployments.
Lessons Learned by Eric Ries Monday, June 15, 2009 Why ContinuousDeployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuousdeployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Lessons Learned by Eric Ries Monday, December 28, 2009 Continuousdeployment for mission-critical applications Having evangelized the concept of continuousdeployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.
Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuousdeployment system. Update: I havent used Heroku , but as Ryan points out in the comments it definitely belongs on this list as a compelling, get-up-and-running fast deployment platform.
Lessons Learned by Eric Ries Monday, February 16, 2009 Continuousdeployment with downloads One of my goals in writing posts about topics like continuousdeployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.
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.
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.
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?
It seems your cluster architecture is one of the key architectural constraints making continuousdeployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuousdeployment? Case Study: Continuousdeployment makes releases n.
I suggested that we change the underlying architecture of our UI system so that the artists would be able to build their own UI pieces themselves and then integrate them into the product without requiring new code every time. Case Study: Continuousdeployment makes releases n. The engineering team wasn’t happy either.
Eric, Is this post about Architecture? I define Architecture (capital A) as "the advocacy for human values in a process" (not little a architecture, over-arching structural approach, just design-in-the-large). Case Study: Continuousdeployment makes releases n. Not bad for an engineer.
Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.
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: Continuousdeployment makes releases n. I remember once being asked in a Microsoft group interview (and dinner) about the ActiveX security model.
Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. Case Study: Continuousdeployment makes releases n. But it goes beyond that, including techniques for improving the economics of product development.
We talk about taking advantages of the incredible agility offered by modern web architecture for extremely rapid deployment, etc. Labels: agile , continuousdeployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. Case Study: Continuousdeployment makes releases n.
I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. Case Study: Continuousdeployment makes releases n. Just change it.
We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. Labels: agile , continuousdeployment 1 comments: timothyfitz said. Case Study: Continuousdeployment makes releases n.
And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. Case Study: Continuousdeployment makes releases n. We owe a lot to this seminal document.
Government IT solutions can be iterative, they don't have to be designed down to the last detail by architecture astronauts before implementation. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
Open APIs and data-oriented architecture (aka "web 2.0"). Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica. The much-promised era of component reuse in software is finally upon us.
You dont need to invent a new architecture, and you dont need to even build your architecture up-front. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica. yeah, its awesome.
Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Even a great architecture becomes inflexible. Case Study: Continuousdeployment makes releases n. This is why agility is such a prized quality in product development.
The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. On the other, they already have a team fully engaged on making their product architecture better.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content