I’d like to share a simple and short case study about pragmatic approach to delivering new features to existing, very big software product. Let’s start with some background. There is an existing product, working nicely on production. We want to extend it with new features, fix bugs and experiment in A/B environment. This sounds very typical and I have already been working in such projects more that dozen times. Even though it is so typical and ever-present, I would say that I’ve rarely seen it working well.
Deployment is just a technical detail, not important for a business. Seriously? One may say business guys don’t think about deployments. I would say it is your role - as a dev - to make them stop thinking about it. If you doubt, let’s consider the following aspects. Doesn’t matter how lovely your application is. How many buzzwords you can use to describe it. It’s all about earning money.
Introduction In this short post we would like to share our experiences regarding large systems monitoring. The focus however will be put on cooperation between dev/devops and business. Why is this important? Why should we care? Is it worth it? Are there any obstacles or pitfalls? Let’s dive into what we think are best practices and see how they finally work out. Best practices distilled Present data in concise and clear manner, ideally aggregated.