<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rustem Bedretdinov on Medium]]></title>
        <description><![CDATA[Stories by Rustem Bedretdinov on Medium]]></description>
        <link>https://medium.com/@rustemb?source=rss-2eada2a83d19------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nBVgb7A9CMCTzfrq.</url>
            <title>Stories by Rustem Bedretdinov on Medium</title>
            <link>https://medium.com/@rustemb?source=rss-2eada2a83d19------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:36:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rustemb/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[High level notes on building highly available architecture]]></title>
            <link>https://medium.com/@rustemb/high-level-notes-on-building-highly-available-architecture-70295c8decc?source=rss-2eada2a83d19------2</link>
            <guid isPermaLink="false">https://medium.com/p/70295c8decc</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[high-availability]]></category>
            <dc:creator><![CDATA[Rustem Bedretdinov]]></dc:creator>
            <pubDate>Thu, 09 Aug 2018 12:41:02 GMT</pubDate>
            <atom:updated>2018-08-09T12:41:02.451Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RqTLlKEtlKjgCNW3Be1X-A.jpeg" /></figure><blockquote>Availability = possibility of the system to provide service to it’s users</blockquote><p><strong>Risks to availability:</strong></p><ol><li>Software bugs</li><li>Data corruption</li><li>Dependencies</li><li>Sudden growth of traffic x100–10000 times</li><li>Long rain effects</li></ol><p><strong>Trade offs:</strong></p><ol><li>Availability brings redundancy &amp; related risks</li><li>CAP theorem limitations</li></ol><p><strong>Things to consider:</strong></p><ol><li>Planning ahead (e.g. may by any means traffic suddenly increase — blog post, TV program). Analysis of potential SPOFs &amp; load forecasts</li><li>Monitoring &amp; monitoring of monitoring</li><li>Canary deployments</li><li>Failover</li><li>Multiple partitions/sites including active-active and geo-dns</li><li>Shard customers — serve different groups of customers within different applications. Or duplicate key controls as in plane</li><li>Reject input, which caused the crash</li><li>Jittering VM/containers configurations</li><li>Auto scaling in order to prevent sudden traffic growth</li><li>Caching as a way to minimize impact on increased traffic growth</li><li>Implement traffic throttling</li><li>Minimize recovery time</li><li>Implement chaos engineering like Netflix’s simian army</li><li>Processes and organization: plan and rehearse triaging and recovery</li><li>Reactive load balancing with nodes shuffling, parallel requests and a request cancellation (e.g. HA Proxy)</li><li>Continuous improvement — hard to plan everything ahead, team has to monitor what’s going on and quickly adapt to new challenges (they will happen anyway)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70295c8decc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Checklist for good design]]></title>
            <link>https://medium.com/@rustemb/checklist-for-good-design-f6b00e7fee6f?source=rss-2eada2a83d19------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6b00e7fee6f</guid>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <dc:creator><![CDATA[Rustem Bedretdinov]]></dc:creator>
            <pubDate>Tue, 29 May 2018 12:28:17 GMT</pubDate>
            <atom:updated>2018-05-29T12:28:17.692Z</atom:updated>
            <content:encoded><![CDATA[<p>Professional developers know, that the earlier you find the bug in your code, the easier it is to fix it. For example this picture demonstrates how cost of a bug fix varies through different phases of software development lifecycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*8Pa8umVeOC-YRqcBhqUUcQ.png" /><figcaption>Relative cost of a bugfix on different stages of SDLC (<a href="https://stackoverflow.com/questions/4130051/software-development-costs-pyramid">source</a>)</figcaption></figure><p>I’d like to share own checklist, which we use, when we review new design documents with our team. We use it for every major change, which we plan in the system to try to look at the same change from different angles and find the best suitable option.</p><p>Unfortunately, developers sometimes forget about some of these points (That happens to myself as well), so hopefully it’ll help you as well.</p><ol><li>Business:</li></ol><ul><li>SAAS — how does this change affects typical SAAS KPIs like Acquisition of new Clients, Retaining of Clients, Increase of average TCV per Client. Or otherwise, will we gain more money after this change?</li><li>CAPEX — does this change requires any investment? E.g. Hardware, hosting, Software License Costs. Do we need any special tools for this change?</li><li>OPEX — will it reduce costs of system ownership or will increase them? E.g. manual effort for maintenance &amp; support, license Annual Renewal Costs</li></ul><p>2. Scope</p><ul><li>Applications/Components — do we understand, which parts of our solution will be affected?</li><li>Databases — which databases will be affected by this change? Do we need to assume any critical migration strategies? What about data replications within the system?</li></ul><p>3. Architecture &amp; Design</p><ul><li>Technical Debts — are we decresing amount of technical debt, while doing this change?</li><li>Dependencies on 3rd parties — do we decrease number of 3rd party software, which we use in our software?</li><li>Correlation with strategy — is design, on which we work now, corresponds to overall technical strategy, which we have agreed on?</li><li>Customizations — do we need to consider any existing customizations, when we plan this design?</li><li>Reuse — aren’t we inventing bicycles? How do other people most efficiently solve this?</li></ul><p>4. Infrastructure &amp; Hardware</p><ul><li>Infrastructure blueprints — will we need to renew any infrastructure blueprints and existing asses management systems?</li><li>Number of servers/nodes — will we need more servers?</li><li>Load balancing — do we have any special load balancing requirements</li><li>External Connectivity — do we need to be concerned aboput securing external connections (both incoming and outcoming). Which security protocols (SSL, TLS v1.0, TLS v1.1, TLS v1.2) should be supported?</li></ul><p>5. NFR</p><ul><li>Testing — what’s the best way to test this change?</li><li>Security — do we have any specific requirements or risk related to security? How to address those? Are potential security breaches (XSS, Injections and etc) avoided and mitigated?</li><li>Performance — has potential negative performance degradation been identified and mitigated?</li><li>Deployment and configuration — are we changing the way how applications will be deployed and configured? Are we updating related instructions?</li><li>Documentation — should we consider updating different user guides and misc related documentation?</li></ul><p>6. Processes</p><ul><li>Processes and instructions — are we changing any processes and instructions in the scope of this change? Should we plan any trainings?</li><li>Compliance — won’t we break existing corporate standards and rules?</li></ul><p>7. Common:</p><ul><li>Clearness — am I explaining clearly, what I’m planning to implement here?</li><li>Easiness — have we selected the easiest and quickest option? Aren’t we overcomplicating?</li><li>Risks — have we identified all major risks and figured out their mitigation?</li><li>Requirements — Have I covered all major requirements?</li></ul><p>Have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6b00e7fee6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Idea as a glue and fuel of the business]]></title>
            <link>https://medium.com/@rustemb/idea-as-a-glue-and-fuel-of-the-business-9ad68767ecaa?source=rss-2eada2a83d19------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ad68767ecaa</guid>
            <category><![CDATA[legacy]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[crisis]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Rustem Bedretdinov]]></dc:creator>
            <pubDate>Tue, 20 Feb 2018 15:45:36 GMT</pubDate>
            <atom:updated>2018-02-20T15:51:20.439Z</atom:updated>
            <content:encoded><![CDATA[<p>Until now I have participated in 8 big projects for product transformation. Baseline of each product was different, on the other hand each of them was on fire. On one CSAT was terrible, on another — product was totally unstable, 3rd one has been written on a dinasaur programming language and they lost all their key developers and so on.</p><p>When these products have been handed over to my team, we did root cause analysis for each of these products. Real root cause is one. NO GOOD IDEA, WHY THIS PRODUCT IS IMPORTANT. No single goal, which may unite entire product team and make them spend sleepless nights improving it and come to the office next day.</p><p>You may say that it’s all about leadership problem. Yes it is. But in this case, what diversifies a good leader from a bad one?</p><p>Ability to inspire, unite people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IkG1sqiKhC1OYNx_xTqb7A.jpeg" /></figure><p>Here under the people we may understand different groups of them:<br>* Development team<br>* Sales<br>* Other departments of the company, somehow related with this product<br>* Existing customers<br>* Prospects<br>* Investors<br>* Our wifes and husbands</p><p>All of them need some glue to stick to this product to make it successful. If you have an specific, ambitious, but still doable goal, you may unite them.<br>This goal shouldn’t be static, it should evolve over the time. This idea is also connected with your market and business model.</p><p>E.g. Initially Steve Jobs was inspired by the idea of making a computer, which may be used by common people. He confronted IBM and was appealing to creative openminded people. That was his differentiator. When Apple company hired him again, he was inpired by the idea of rethinking the computer to make work with it pleasant. 3rd wave happened, at the era of iPhone, when we was reinventing the phone.</p><p>That’s all good, but what could be the goal, if you own a 5-bank branch in Central Europe? Or a small trade company in middle-East?</p><p>You may start something like this:<br>* Get #1 on your market (specify what is this market)<br>* Help 100000 people move to new houses through facilitating mortgage services</p><p>Of course these samples might be slightly exaggerated, but hope they explain the idea.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ad68767ecaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>