<?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 Alexander Chistyakov on Medium]]></title>
        <description><![CDATA[Stories by Alexander Chistyakov on Medium]]></description>
        <link>https://medium.com/@demeliorator?source=rss-4363e14514f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*UlSMQSp9MQKF3Qb5.</url>
            <title>Stories by Alexander Chistyakov on Medium</title>
            <link>https://medium.com/@demeliorator?source=rss-4363e14514f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:01:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@demeliorator/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[Chronicles of a modern witch-hunt: history of public allegations from one of Rutube’s top brass]]></title>
            <link>https://medium.com/@demeliorator/chronicles-of-a-modern-witch-hunt-history-of-public-allegations-from-one-of-rutubes-top-brass-352810d7eed9?source=rss-4363e14514f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/352810d7eed9</guid>
            <dc:creator><![CDATA[Alexander Chistyakov]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 15:55:41 GMT</pubDate>
            <atom:updated>2026-01-22T15:55:41.286Z</atom:updated>
            <content:encoded><![CDATA[<p>There was a heated debate last week in the Russian IT community. The headliner was Maxim Ulyanov, the head of a department in Rutube, Russia’s infamous YouTube clone. Maxim publicly accused two people of being “wolves” (a self-designation for people who embellish their CVs adding more experience than they really have, mostly associated with Anton Nazarov’s community). But the real problem wasn’t even that the allegations were false — it was what happened afterward.</p><h3>Prequel: first blood</h3><p>This is not the first time the Russian IT community has discussed Maxim and his war with “wolves”. An undisclosed Rutube employee was fired some time ago under odd and disturbing circumstances. As far as we understand, Maxim Ulyanov (the head of Rutube client development) has discovered that the employee in question thanked his mentor in public Telegram channels associated with that community. Big bosses arranged a meeting with that employee immediately and had a heated conversation along the lines of: “We know who you are, sign a voluntary resignation and go away or the consequences would be dire”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tPSJQHEJ3iuyfZrtJrJIJA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*4aJy6nM38058CPAwRlaZPg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*HdV2Vpx9Kybm9pN9d2YMlA.jpeg" /></figure><p>Under pressure, he signed a “voluntary resignation”. Ulyanov has publicly accused that dismissed employee of making up his CV in the corporate chat after his resignation.</p><p><strong>But what does the law say?</strong></p><p>Based on Article 80 of the Labor Code of the Russian Federation (№197-FZ), termination at the employee’s own initiative (“voluntary resignation”) constitutes a unilateral decision by the employee. The employee must personally submit a <strong>written resignation notice</strong> and assumes responsibility for compliance with statutory procedures. The employee retains the right to <strong>withdraw said resignation notice unilaterally at any point</strong> during the <strong>fourteen (14) calendar-day notice period</strong> prior to its expiration.</p><p><strong>Article 5.27 of the Code of Administrative Offenses of the Russian Federation:</strong> Where coercion to terminate employment is substantiated, the employer shall incur administrative liability in the form of a monetary penalty.</p><p>It’s worth saying that “coercion” can be both physical and psychological.</p><p><strong>Let me state that again: contract termination under coercion is a direct violation of the Labor Code of the Russian Federation.</strong></p><p>That first episode has shaken the IT community but everybody just calmed down by the end of the day. The only person remembered that on a daily basis was the fired guy: he was later diagnosed with cardiac arrhythmia after the incident. You might think case was closed once and for all, but...</p><p>Recently, Maxim has participated as a guest on a podcast. The host of that podcast asked Maxim about that “wolf” incident. His answer sounded conciliatory: “I’ve reconsidered that.”</p><p>But everything has its “48 hours later” moment…</p><h3>“Yappy” has nothing to do with “Rutube”</h3><p>48 hours after that podcast Maxim posted again on Telegram with yet another “disclosure”.</p><p>Were the previous 15 minutes of fame not enough? Is he on a holy quest for purging the unclean from the industry?</p><p>A Telegram post called <strong>“here we go again” </strong>grabs the reader from the start:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*3KgZLNcycMb8FVc4OT9FPw.png" /></figure><p><a href="https://t.me/m0rtymerr_channel/3216">Full Telegram post</a></p><p>He then analyzes the CV in detail. Ulyanov highlights inconsistencies accusing someone else of lying:</p><ul><li>“Infinite video scroll”? We don’t use that wording!</li><li>Next.js? We don’t have it in our toolchain!</li><li>Cypress? We don’t use that!</li><li>GrowthBook? Not in use!</li><li>Effector? We have publicly stated at conferences what tool we prefer!</li></ul><p>Maxim has drawn his conclusion in the following manner:</p><p><em>“As you can see that’s bullshit — not real experience”</em></p><p>The reasoning is simple: “I am a department head, I haven’t seen that person on our corporate portal so he is lying”. That Telegram post goes viral: personal information of the alleged “wolf”, his face, accusations of making up the CV. Needless to say, it’s severe reputational damage for a person who is trying to get a job.</p><h3><strong>The truth revealed</strong></h3><p>The person in question responded publicly within a few hours. His answers overwhelmed the community.</p><p>He has truly worked under the Rutube brand but not at Rutube directly but at Yappy — a short-video platform folded into the Rutube brand <a href="https://www.gazeta.ru/social/news/2025/11/28/27292837.shtml?utm_source=chatgpt.com">back in 2025</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kt4-KEOw4W0MBQEwZRWRVw.jpeg" /></figure><p>The Yappy dev team was merged with the Rutube dev team that led to layoffs (no surprise, nobody wants two or three people in the same role). That guy in question was laid off with compensation (a standard two-month severance package and “voluntary resignation”).</p><p>He put Rutube on his CV for the single simple reason: <strong>Yappy doesn’t even exist as a separate entity anymore, moreover, all Yappy open positions had been posted under the “Rutube” brand since 2024.</strong></p><p>That said, even potential employees were told that they <strong>were going to work for the Rutube brand</strong> right from the start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVAhsxUbUxzBP0a25ZH2FQ.png" /></figure><p><a href="https://hh.ru/vacancy/99321482?hhtmFrom=resume"><strong>Yappy archived Python/Go lead developer position</strong></a></p><p>It’s worth saying that <a href="https://companies.rbc.ru/trademark/422004/rutube/?ysclid=mkfui9tk4k995476485">Rutube itself does not even exist as a legal entity — it’s called “RUFORM” LLC legally</a>. This is the company that operates Rutube and represents that brand as a legal entity.</p><p>This situation is nothing new in IT. Big players own tens and even hundreds of affiliated legal entities. For example, SBER owns more than a hundred subsidiaries. A person could work on SBER products/services and be employed legally in “SberTech” LLC, “SBER AI Technologies” LLC and so on. Same in Yandex — experts work for the Yandex brand and can be employed in “Yandex.Technologies” LLC, “Market Platform” LLC or other subsidiaries. It’s a very common practice among SBER and Yandex alumni to put brand names rather than legal entity names in their CVs and in professional networking profiles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*GxqclgT49fe1fdpAcRpVag.png" /></figure><h3>You’re not in the System, so you must be lying — right?</h3><p>But Ulyanov did not back down anyway. He updated his post after the new information:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*KjmO37uy7R3fhZ778bhv5w.png" /></figure><p><a href="https://tgstat.ru/channel/@ulyanov_life/2025">Full Telegram post</a></p><p>Consider his reasoning a bit: legal entities just merged, organizational structure was completely unclear, people were moving between departments, some were laid off. In that chaos a department leader was unable to find a colleague from a newly added unit on the corporate portal — and boom! What was the conclusion then? That colleague must have been a liar!</p><p>Ulyanov deleted personal data after a huge community backlash but he repeatedly defended himself regardless.</p><h3><strong>The IT community fires back</strong></h3><p>Aleksey* Kuleshov, a well-known veteran developer who has worked at Intel, Deutsche Bank, Huawei, and Yandex, expressed his point of view publicly:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*eeZi6K1nTNnfdHBWtuYflQ.png" /></figure><p><a href="https://t.me/akuleshov7_live/359">Full Telegram post</a></p><p>Kuleshov’s key take:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*8IA0gG8Kuu7HAK8V6bQurw.png" /></figure><p>Deploy’s Ivan Botanov also makes a Telegram channel posting called <strong>“Wolfhounds at work”</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*YzZudlP53EpA8Wd7rSvXpw.png" /></figure><p><a href="https://t.me/dev_yttg/1653">Full Telegram post</a></p><p>Maxim stood his ground: no apologies, the CV was made up, he didn’t make any mistake:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*-a1PXE5FiICK_4sOQXDPqw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zm9FAGioBgTCEdNOIzSE2g.jpeg" /></figure><h3>Maxim deletes his posts and goes silent</h3><p>Someone (presumably Maxim) eventually deleted his posts. Who knows, did Rutube’s PR step in or maybe Maxim rethought everything finally…</p><p>But as he stated himself he did not change his point of view and just “got tired of arguments”. That explanation is convenient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*Ho2aRx5HRMpR71vc6U4d5w.jpeg" /></figure><p>Nothing online disappears completely. Telegram posts have been archived online, screenshots stored in private and public chats. The only public traces are deleted posts and excuses like “I didn’t call him a liar just pointed out that his experience is not described accurately”. We have a classic lose-lose situation, everyone took reputational damage:</p><ul><li>Yappy alumnus as a job seeker</li><li>Maxim Ulyanov as a manager</li><li>Rutube as a place to work</li></ul><h3>Systemic problem</h3><p>This is not a personal conflict story. Our beloved industry may have a systemic problem. <strong>Ulyanov is not an ordinary blogger next door, he is the head of a big department in a large company.</strong></p><p>Maxim’s public posts are a highly subjective opinion of a certain person with some public recognition in the Russian IT community. Without any formal criteria or proof, he decides that a random Internet person is a liar. HR ladies discover that and discard the candidate’s resume immediately. Don’t think they have spare time to do any research on these discussions.</p><p>And the victim of public shaming doesn’t have many options to defend themselves, everything they say would be treated as an excuse. But even the best defense won’t erase the initial negative effect. Apologies always sound softer than the initial claim. Not in this case, of course, because we did not see any at all.</p><p>Maybe we need to discuss the core of their argument separately for a moment. So, a person could be publicly shamed because they don’t pay enough attention to a legal company name after a merger? Not for falsifying recommendations, not for making up non-existent projects. Not for claiming to be a part of successful projects they were never part of. But only because “Rutube” and “Yappy, a whole subsidiary of Rutube, operated by RUFORM LLC” are two completely different things!</p><h3>Conclusion: with great power comes great responsibility</h3><p>This story got a lot of attention because methods exploited by Maxim were far off the scale of the problem.</p><p><strong>For those who hold power (job role, community of subscribers, public recognition):</strong></p><p>1.<strong> Always verify your information before making public claims.</strong> A single private email to the HR department would resolve everything in minutes.</p><p>2. <strong>Do not ever post personal data publicly.</strong> Person’s name and surname, photos, CV details — everything exposed can lead to harassment.</p><p>3.<strong> Know how to acknowledge your mistakes publicly.</strong> False public accusations demand public apologies. To delete posts silently is not the same as to apologize publicly in more explicit form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*NsrwGNHjSfstG6PNi40-bw.png" /></figure><p>4. Last but not least:<strong> don’t forget to mind your own business trying to catch “wolves”, maybe you are not a good hunter after all. </strong>Are you driven by rational logic or purely by your own ego?</p><p>Ulyanov finishes his publication asking the following existential question:</p><p><em>“Resume, as an artifact, is dead. What will save us: certification or AI?”</em></p><p>Maxim, maybe neither AI nor certification would be the savior. Maybe we should just start with something more human like doing fact-checking before declaring someone a liar in public.</p><p>Because when “absence on the corporate portal” is a crime as harmful as “lie in resume”, when public accusations are formulated without any corporate PR person involved, when silence is meant to be treated as an apology the problem is not in CV quality at all. The problem is people in power who exploit their authority to discredit others ignoring real industry challenges.</p><p>Maybe Maxim’s next steps would be asking HR department to fire Rutube board members because he does not know them in person. And let me ask you this, dear readers, what do you think? Do you think Maxim was right?</p><p>—</p><p>* Sorry Andrey, they forced me</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yk0OwnIuspSItvfH0VXUHQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=352810d7eed9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t be Nutanix]]></title>
            <link>https://medium.com/@demeliorator/dont-be-nutanix-84c0d270b4c8?source=rss-4363e14514f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/84c0d270b4c8</guid>
            <category><![CDATA[sjw]]></category>
            <category><![CDATA[nutanix]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Alexander Chistyakov]]></dc:creator>
            <pubDate>Mon, 27 Nov 2017 12:34:40 GMT</pubDate>
            <atom:updated>2017-11-27T12:34:40.418Z</atom:updated>
            <content:encoded><![CDATA[<p>Nutanix emerged as a new kid on the block and quickly became a major player (well, at least it pretended to be).</p><p>Maxim Shaposhnikov, regional technical director at Nutanix and his team did some amazing work selling licenses and appliances all around EMEA. Well, at least they talk about that, so let’s just believe them for the rest of my article.</p><p>Maxim has organised a vibrant community in form of a Telegram group chat (<a href="https://t.me/nutanix_russia">https://t.me/nutanix_russia</a>). Formally this chat is dedicated to promoting of Nutanix products. In fact Maxim promotes mostly his own person (which is not that bad per se):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vrGjoALdiwpRE02J0vnhA.png" /></figure><p>The stats bot was added to the chat only recently but it represents an everyday situation quite well. Maxim is a proud owner of a Tesla-manufactured car and his Tesla seems to be a hot topic in this chat (I believe 100 is a cap set to limit the number of search results, the total number should be far bigger than 100):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6XDxY1vi6KWTcz3L5YdxA.png" /></figure><p>Needless to say, Maxim is the only Tesla owner in this chat. An average Russian IT engineer can’t afford such a luxury car. So basically discussions revolve around Maxim’s high life in England, his cars, iPhones, ski tours to Alps and other things an average IT guy can only dream of.</p><p>One of Nutanix’ mottos (constantly promoted by Maxim) is: “We don’t pay kickbacks”. Sounds very cool, indeed. These guys seem to have high morale. Except when they don’t.</p><p>My friend Cate is not a full time volunteer but she helps various organisations and individuals in her spare time. Of course, she has a proven track record of helping homeless people and abandoned pets.</p><p>This time Cate was raising funds for abandoned puppies (<a href="https://vk.com/acate?w=wall-124646349_579">https://vk.com/acate?w=wall-124646349_579</a>), because every dog needed not only a home but some food too. Maxim generously donated £200 to that campaign. This donation was very timely and really helped a lot.</p><p>Coincidentally, Cate holds a position of a creator and an active moderator of a telecom-related group chat in Russia-originated Telegram messenger. Surprisingly this fact became an apple of discord. Maxim had joined that chat to promote Nutanix and quickly started to promote himself exactly in the same manner as in his own chat controlled by Nutanix employees. This was not a big problem until he started to address Mother Russia in derogatory terms. Since every community has rules Maxim got banned very quickly (we don’t have screenshots from that chat, because Maxim’s messages were deleted).</p><p>Immediately after this incident Maxim asked for refund and started to threaten to open a fraud case against Cate in his bank in England:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*hr3FF3d3hd0n7MxTtjCppg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*cHp1ctgqwgRe8OFYNz5I2w.jpeg" /></figure><p>Although Maxim has a formal right to withdraw his donation, <strong>this case is definitely not a fraud</strong>!</p><p>The moral question I would like to address is: if you don’t pay kickbacks (your customers are capitalists after all and it’s probably their responsibility to set up a decent due diligence process) does it allow you to withdraw your donation made to dogs? Dogs are neither customers nor capitalists. They are not even humans. They are, you know, dogs and have a very limited ability to defend themselves. And if your donation is big enough does it allow to call volunteers names? Or maybe even beat them? The answer is not so obvious, at least for a Nutanix C-level guy.</p><p>Frankly, I’ve never intended to buy Nutanix products (even if they would offer me a kickback, lol). I’ve always been on the other side of the ring (preferred open source products for a number of reasons). And now I have another reason for that (thank you, Maxim, for a great case of marketing!).</p><p>Cate’s credit card number is 4276 5500 1083 8772 if you would like to donate (remember that she has to return £200 in question to Maxim in a week). If you donate more than £200 in total we will transfer rest of funds to an animal shelter. We don’t pay kickbacks too. Sorry, you still won’t be permitted to call Russia a derogatory name in our chats (why do you need to do that in the first place?). Don’t be evil, don’t be Nutanix!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84c0d270b4c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Docker in Production: a cargo cult and the rise of Church of Metrics]]></title>
            <link>https://medium.com/@demeliorator/docker-in-production-a-cargo-cult-and-the-rise-of-church-of-metrics-b0472148d939?source=rss-4363e14514f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0472148d939</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Alexander Chistyakov]]></dc:creator>
            <pubDate>Sun, 26 Feb 2017 01:13:45 GMT</pubDate>
            <atom:updated>2018-01-03T07:04:36.590Z</atom:updated>
            <content:encoded><![CDATA[<p>The HFT Guy wrote <a href="https://thehftguy.com/2017/02/23/docker-in-production-an-update/">another horror story</a> about using Docker in production. I have never been to London and have (luckily) never worked in the high-frequency trading industry, so I’m probably not a right person to comment on this. But I wonder, is this guy even an engineer after all?</p><p>I ordered a vape mod box and an atomizer some time ago, so consider me a hipster. As a hipster, I know that “metrics” and “repeatability” are cornerstones of (Dev?)Ops engineering. Thus, when we choose a platform we usually not only perform a SWOT analysis but create a test lab and make some tests. And we tend to make the tests publicly available for others to review our results. This is how any physical experiment was conducted past several decades (I was taught that back in school at least).</p><p>That said, can you please review The HFT Guy’s article and find ANY meaningful experiment description or even its results? Because I can’t find anything alike. I know nothing about decision making in finance but choosing CentOS/RHEL because the engineer is “not aware of any serious companies than run on Ubuntu” does not seem right to me. I know lots of serious companies that run on Ubuntu, so what? Maybe we have different definitions of “serious”, but this metric is not practically measurable anyway. How do we suppose to call it, “seriousness”?</p><p>Choosing CentOS/RHEL because everybody in the market does it is a pure cargo cult. “Nobody ever got fired for buying Cisco(IBM, RedHat, whatever)” is a good decision making strategy at first sight, except I know a man who was actually fired for buying Cisco. And you can be next.</p><p>I really don’t know what to add. The whole thing is a pure FUD. This guy must be from a sales department. If you make decisions the same way he does, you probably own an overpriced vacuum cleaner and other magic stuff a talking head on a TV told you to buy. Join the Church of Metrics today and stop doing poorly reasoned things!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0472148d939" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why RPM packages are probably not for databases]]></title>
            <link>https://medium.com/@demeliorator/why-rpm-packages-are-probably-not-for-databases-dd22250c13fa?source=rss-4363e14514f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd22250c13fa</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Alexander Chistyakov]]></dc:creator>
            <pubDate>Sat, 18 Feb 2017 19:24:12 GMT</pubDate>
            <atom:updated>2018-01-03T07:11:16.915Z</atom:updated>
            <content:encoded><![CDATA[<p>Mikhail posted <a href="https://myopsblog.wordpress.com/2017/02/06/why-databases-is-not-for-containers/">some rants</a> on using Docker for running a DBMS, and I decided to share my own experience on putting a database in a Docker container. This won’t take too long.</p><p>Yes, I am using Docker for running various SQL and NoSQL database management systems. Before calling me a hipster, please take into consideration that I’m probably just an adrenaline junkie. But enough on that, let’s address questions raised by Mikhail because I’m an engineer even more than the hipster…err, the junkie.</p><p>So, let’s proceed in the same order Mikhail did:</p><h4><strong>1. Data insecurity</strong></h4><p>The recommended way to store persistent data in Docker containers is not to use a filesystem of a container to store anything. All persistent data should be stored on volumes located on a host. Moreover, the best practice is to put a read-only restriction on the container FS. And if you have a durable fsync(2) call as you usually do, Docker adds no extra source of data corruptions.</p><h4>2. Specific resource requirements</h4><p>Mikhail is totally right, mixing DBMS containers with service ones does not seem to be right. But it’s not Docker’s problem I think.</p><h4>3. Network problems</h4><p>Mikhail does not name a specific case of network problems, but I can make a wild guess. The default network model in Docker relies on NAT translation and NAT translation uses a connection tracking table in kernel space. But if you use any stateful firewall you already utilize the same mechanism.</p><h4>4. State in computing environment</h4><p>Managing stateful services is hard. Let’s subtract Docker from the equation, and guess what? Managing stateful services without Docker is still hard!</p><h4>5. They just don’t fit major Docker features</h4><p>Things are not always what they seem at first sight. From my point of view Docker is mainly a better packaging manager, say RPM. Is Docker on par with RPM abilities to distribute software? I’d say yes. And if you don’t want to use Docker with your database you should probably consider stopping using RPM packages as well.</p><h4>6. Extra isolation is critical at the database layer</h4><p>I don’t see any extra overhead in using Docker. Docker relies on cgroups and namespaces, and if you use systemd-based Linux distribution, your DBMS is in a separate cgroup already.</p><h4>7. Cloud platform incompatibility</h4><p>I just don’t get how Docker can prevent using cloud features, sorry. From my point of view using Docker is completely orthogonal to using cloud instances and does not interfere with any cloud feature at all.</p><h3>Conclusion</h3><p>You can probably put your RDBMS in a container. Or maybe not.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd22250c13fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My hamster thinks that communism will prevail]]></title>
            <link>https://medium.com/stonic/my-hamster-thinks-that-communism-will-prevail-30394579a2b2?source=rss-4363e14514f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/30394579a2b2</guid>
            <category><![CDATA[stonic]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ansible]]></category>
            <dc:creator><![CDATA[Alexander Chistyakov]]></dc:creator>
            <pubDate>Fri, 09 Dec 2016 15:12:07 GMT</pubDate>
            <atom:updated>2016-12-09T15:12:07.386Z</atom:updated>
            <content:encoded><![CDATA[<p>My colleague and partner Serge already opened a curtain, so you are probably familiar with the infamous <a href="https://blog.stonic.io/">Stonic</a> project. Serge has his own motivation and, while respecting it, I have my own challenges and opportunities to discuss.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*XVCa7QPf1_As1iw3XAqi3w.jpeg" /></figure><p>It started almost three years ago when <a href="https://twitter.com/mokevnin">Kirill Mokevnin</a> and I discussed CM tools in a hotel room in the City of Penza. I was not particularly familiar with Ansible that time and Kirill was a strong Ansible advocate already (and continues to be at present time AFAIK). Not only Kirill is an expert in open source tools and technologies but also a great speaker and a community manager, so I was convinced to start using Ansible immediately, and guess what? I got a playbook to rule my <a href="https://www.joyent.com/smartos">SmartOS</a> hypervisors (for all of those who are unaware of, SmartOS is a <a href="https://en.wikipedia.org/wiki/Solaris_%28operating_system%29">Solaris</a> descendant) in 40 minutes or so.</p><p>I spent a lot of time “programming in YAML” since then. I believe I and my colleagues made the biggest open source Ansible roles <a href="https://goo.gl/Ez5C67">repository</a> in Eastern Europe (well, well, in Saint-Petersburg, Russia). I even tried to fix a bug in Ansible once but introduced another bug (I am probably a good engineer but not a good communicator, so my commit ended up being reverted).</p><p>Fast-forward to present time, I got a project which uses AWS, <a href="https://www.terraform.io/">Terraform</a> and everything cloud. Of course, I proposed to use Ansible for that but my colleagues (who are Python programmers) asked me why not to use pure Python templating engine to create a different set of Terraform configs off a different set of YAML files. We made a PoC and it took 25 lines total to implement a templater. Yes, this is not a typo, 25 lines and we were done.</p><p>I understand that this example is a bit too radical, but why on Earth do I need a BigIP module if I have never seen any BigIPs? That’s even more radical, but RedHat is a large enterprise company that makes enterprise software, so I’d rather expect the total number of enterprise modules to grow. And this is where my hamster comes to play.</p><p>I’m not a fan of alternative history genre, just a researcher with a number of “what ifs” off the top of my head. What if humans were direct descendants of coalas, not apes? What if Soviet Union did not fail? Well, let’s experiment and build a parallel reality with coalas and SU… I believe, RedHat, Ansible and large enterprises exist even in a very distorted reality like that. And I still don’t like enterprise software even being taught I’m a coala (I’m a creationist after all).</p><p>Okay, let’s do it in small steps. What if Ansible was written in a Lisp dialect? What if this Lisp dialect was <a href="http://hylang.org/">Hy</a>? What if authors managed to reduce Ansible codebase somehow (using the magical powers of Lisp)?</p><p>I was not able to prevent the collapse of Soviet Union. And I don’t know Hy yet. But I will try at least.</p><h3>Get involved</h3><ul><li>Visit <a href="http://stonic.io/">Stonic Project website</a></li><li>Browse <a href="https://github.com/stonicio">Stonic repositories</a></li><li>Star&amp;fork <a href="https://github.com/stonicio/stonic">Stonic application repo</a></li><li>Follow <a href="https://twitter.com/StonicProject">Stonic on Twitter</a></li><li>Subscribe to <a href="https://telegram.me/stonicproject">Stonic on Telegram</a></li><li>Join <a href="https://telegram.me/stonicio">Stonic Community Chat on Telegram</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30394579a2b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stonic/my-hamster-thinks-that-communism-will-prevail-30394579a2b2">My hamster thinks that communism will prevail</a> was originally published in <a href="https://medium.com/stonic">Stonic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>