W dniu 31.08.2011 13:35, Alexander Sack pisze:
I wonder, once we have staging.v.l.o, do we really need edge anymore?
Perhaps not. We will see once we have both.
What problems does edge protect us from that we really care about? Maybe
we can avoid running 3 instead of two instances and have 3 instead of 2 code rollout stages?
What do you mean by "rollout stages"?
my understanding is that with staging and edge you have three rollout steps/stages:
- daily trunk
That's what staging is about
- edge testing
That's how we can evaluate non-invasive production changes instantly (faster than staging).
- production
That's what we released last month (although there are some voices that we may want to put more recent software there too).
i wondered about what risks the "edge" stage protects us from and if we can avoid that step as it comes with additional overhead on maintenance, process and time-to-production.
Edge is just a point on the roadmap. If staging is fast enough to scrap/deploy then we may just use staging all the time.
I guess I'm trying to say "stay tuned".
Thanks ZK