<?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[Data on Kubernetes community - Medium]]></title>
        <description><![CDATA[The Dok.community is an openly governed and self-organizing group of curious and experienced operators and engineers concerned with running data-intensive workloads on Kubernetes. - Medium]]></description>
        <link>https://medium.com/data-on-kubernetes-community?source=rss----f78a8121817c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Data on Kubernetes community - Medium</title>
            <link>https://medium.com/data-on-kubernetes-community?source=rss----f78a8121817c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:32:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/data-on-kubernetes-community" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[SRE vs Data Engineer — Who Owns What?]]></title>
            <link>https://medium.com/data-on-kubernetes-community/sre-vs-data-engineer-who-owns-what-8599be4b6c6a?source=rss----f78a8121817c---4</link>
            <guid isPermaLink="false">https://medium.com/p/8599be4b6c6a</guid>
            <category><![CDATA[sre-vs-de]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[site-reliability-engineer]]></category>
            <dc:creator><![CDATA[Demetrios Brinkmann]]></dc:creator>
            <pubDate>Sat, 05 Sep 2020 22:11:07 GMT</pubDate>
            <atom:updated>2020-09-10T13:46:23.711Z</atom:updated>
            <content:encoded><![CDATA[<h3>SRE vs Data Engineer — Who Owns What?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eKwqs19IIcNLKu_gmNtJcA.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@lorenzocafaro?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Lorenzo</a> from <a href="https://www.pexels.com/photo/black-and-white-business-chart-computer-241544/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p><a href="https://app.slack.com/team/U01708SV22W"><strong>Demetrios</strong></a></p><p>One question that I have been pondering lately is where do the requirements of an SRE end and a data engineer begin and visa versa?</p><p><a href="https://app.slack.com/team/U016TGTDD38"><strong>bmath</strong></a></p><p>In my past experiences, the Data Ops team has been responsible for moving data from one database to another, and also some transformations of the data that are well understood. SREs generally stop when the database is online and get involved if there are access issues. I’d love to hear more about how others divide the labor though.</p><p><a href="https://app.slack.com/team/U018N6BFL49"><strong>Rick Vasquez</strong></a></p><p>This is a fun question because half the reason both of those job titles exist as opposed to a DBA is companies started assuming that databases just need to be running to deal with outages.In our experience the multi tech and multi discipline flexibility that comes with either an SRE or Data Engineer depends on the company and some have even coined a new position called DBRE. We have hundreds of enterprise class customers that we deal with in varying degrees, but the same holds true everywhere, without a true DBA/DBRE everyone is just hoping things go fine as opposed to making sure things will be fine.</p><p>At Percona we look at data engineers as master manipulators of the data regardless of technology it is persisted in and SRE for config/troubleshooting of the whole stack. Neither is actually in charge of properly tuning the database(regardless of tech) and usually companies get lucky that one of the 2 knows how if there is no DBA</p><p><a href="https://app.slack.com/team/U017UKAMUG1"><strong>Mike Semcheski</strong></a></p><p>As I see it, the traditional role of a DBA is to tune the run-time configuration of the database and perhaps some domain expertise around optimization.But the reality is its a full time job just to make sure the right databases are up and running, and that tenants have the resources they’ve paid for. This is more of an SRE position.And so there’s no point of even having a DBA in the traditional sense until you’re excellent at the SRE aspect — no point in tuning a database that isn’t running.</p><p>I’m not really sure about Data Engineer’s, though.</p><p>Perhaps DE’s are in charge of aggregating data from lots of sources and making sense of it all. To do this, they would need access to multiple databases and keep them running, and so it ends up being a little bit of SRE and a little bit of DBA?</p><p>And so if I had to say which of those three hats fits me best, I’d say SRE.</p><p><a href="https://app.slack.com/team/U016VHVS87R"><strong>dave-o</strong></a></p><p>Great question. I think the guys above pretty much nailed it down. Labeling things in IT is a jolly exercise. Sometimes new labels can help Marketing or HR departments categorize things and sometimes new labels can divert people away from stigmatized creepy labels like “The Data Processing Department”. I think the lines have been blurred between the “network guy”, “programmers”, “dba”, “pc support” etc. Most infrastructure guys/gals can at least write scripts and write some code while dba’s and software/data engineers are pretty well versed in the stacks. I think a lot of it boils down to what you like to do. Strictly speaking, under the hood engineers create stuff and DevOps/SREs generally integrate existing components and maintain stuff. My two pence. Now the difference between DevOps and SREs well, that’s anybody’s guess</p><p>… and the beat goes on.</p><p><a href="https://app.slack.com/team/U016VHVS87R"><strong>dave-o</strong></a></p><p>…and of course, Universities have no programs remotely related to anything.</p><p><a href="https://app.slack.com/team/U01708SV22W"><strong>Demetrios</strong></a></p><p>These are all super helpful answers! thank you all for helping me to understand this a bit more. I am going to touch on these topics in the meetup today so I now feel super prepared!</p><p><a href="https://app.slack.com/team/U017JC1B94L"><strong>Dean Stathos</strong></a></p><p>in my mind an SRE and DataOps person are just reincarnations of ye ‘ole Business Continuity and Business Analyst roles. One deals with ensuring infrastructure is up and running (within capacity and performance thresholds) and the other deals with the data that resides in that infrastructure to make sense of it and build value out of it. The roles haven’t changed from a business standpoint, but, the names have to reflect a new paradigm world in IT…one word — cloud…</p><p>If I may, I’d like to further my comment. SRE’s create and maintain the infrastructure within the capacity and performance thresholds defined in conjunction with the DataOps (and other internal end users) requirements. Sometimes, those lines do blur because a DataOps/BA doesn’t really know how to make those requirements and eventually lean on the SRE/BC person (or even HW/SW vendor) to help.</p><p>DataOps/BA roles research and define the tools used to help them make their job faster/better/stronger/etc… Once the tools are defined, they work with the infrastructure folks to see how those tools can be implemented within the corporate IT strategy in place — in many cases these days, public cloud has become the infrastructure strategy of choice.</p><p>Big Thanks to Rick, Brian, Dean, Mike and Dave for helping me see the differences here.</p><p><a href="https://join.slack.com/t/dokcommunity/shared_invite/zt-g3ui5r0g-jDKz5dhh2W1ayElqwKYYAg">Join us in slack</a> to talk about these kinds of themes and so much more! Also, feel free to drop into our <a href="https://go.dok.community/register">weekly Tuesday meetups</a> or catch the replays on <a href="https://www.youtube.com/channel/UCUnXJbHQ89R2uSfKsqQwGvQ?view_as=subscriber">youtube</a> or in <a href="https://anchor.fm/demetrios6">podcast land</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8599be4b6c6a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-on-kubernetes-community/sre-vs-data-engineer-who-owns-what-8599be4b6c6a">SRE vs Data Engineer — Who Owns What?</a> was originally published in <a href="https://medium.com/data-on-kubernetes-community">Data on Kubernetes community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Call for Collaboration: Announcing the Data On Kubernetes Community]]></title>
            <link>https://medium.com/data-on-kubernetes-community/a-call-for-collaboration-announcing-the-data-on-kubernetes-community-58399e3be624?source=rss----f78a8121817c---4</link>
            <guid isPermaLink="false">https://medium.com/p/58399e3be624</guid>
            <category><![CDATA[site-reliability-engineer]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Demetrios Brinkmann]]></dc:creator>
            <pubDate>Wed, 26 Aug 2020 16:20:40 GMT</pubDate>
            <atom:updated>2020-08-26T16:30:48.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*2I3A0koyQ_BufetJXjjYqw.png" /><figcaption>Data on k8s community logo made by community member Pete Coles</figcaption></figure><p>I’m happy to help announce the launch of a new community — the Data On Kubernetes Community. The Dok.community is an openly governed and self-organizing group of curious and experienced operators and engineers concerned with running data-intensive workloads on Kubernetes. DoKc takes inspiration from the CNCF and Apache foundations and aims like each of them to be open, vendor-neutral, and extremely inclusive.</p><p>Unlike each of these foundations, the purpose of DoKc is to openly develop, share, and discuss engineering and operation <em>patterns</em> as opposed to particular <em>projects</em>. While DoKc is an open-source community it is a community focused on knowledge generation and sharing as opposed to becoming a home for open source projects (and their trademarks).</p><p>DOKCs is for all those that are interested in using Kubernetes to serve and manage data in their organization. 2020 has emerged as the year that data really migrated onto Kubernetes with the common workloads including CI/CD, machine learning, ecommerce systems such as Magento, instrumentation and monitoring and others. Almost any up to date stateful workload has seen a rapid increase in usage on Kubernetes.</p><h3></h3><p>If you are interested in doing data services with #Kubernetes come join us as we make it happen. @DoKcommunity https://t.co/rlCz2UWNkg</p><p>In short, now that Kubernetes can handle high-value stateful workloads — it is all the more critical that the broader cloud native community share best practices. The potential of managing data on the same platform used to orchestrate is enormous and is just being uncovered. I am confident that the DOKC community will bring together practitioners and developers building Kubernetes and container attached storage and other related projects, thereby sparking more understanding and innovation.</p><p>Our founding sponsor MayaData; creators of the open-source project <a href="https://openebs.io/">OpenEBS</a> and the Kubernetes native chaos project <a href="https://litmuschaos.io/">Litmus</a> has interacted with thousands of companies and individuals running data workloads on Kubernetes. These experiences helped uncover the need for an independent community to discuss and investigate useful patterns for the use of Kubernetes as a data layer.</p><h3></h3><p>Meant to mention @DoKcommunity is so far a cool independent place to also have such discussions, compare notes, hear from folks like Arista and Optoro and others. I highly recommend it. We did help seed it btw however it is an independent space</p><p>Many others feel similarly — DataStax, Confluent, Arista, Yugabyte, Optoro, 2nd Quadrant, and others have volunteered to participate in upcoming conversations and investigations.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fanchor.fm%2Fdemetrios6%2Fembed&amp;display_name=Anchor+FM+Inc.&amp;url=https%3A%2F%2Fanchor.fm%2Fdemetrios6&amp;image=https%3A%2F%2Fd3t3ozftmdmh3i.cloudfront.net%2Fproduction%2Fpodcast_uploaded400%2F7515682%2F7515682-1595505306316-6dfe7be1e750c.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=anchor" width="400" height="102" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd63c4805fbe50a5384595c36d5b838d/href">https://medium.com/media/dd63c4805fbe50a5384595c36d5b838d/href</a></iframe><p>Please<a href="https://forms.gle/v8oQ743JENCaZdn77"> fill out this simple form</a> to get in touch with me about forming a part of the community.</p><p><strong>Relative links:</strong><br><a href="https://www.youtube.com/channel/UCUnXJbHQ89R2uSfKsqQwGvQ?view_as=subscriber">Youtube channel</a><br>The <a href="https://join.slack.com/t/dokcommunity/shared_invite/zt-g3ui5r0g-jDKz5dhh2W1ayElqwKYYAg">DoK.community Slack</a><br>Twitter: <a href="https://twitter.com/DoKcommunity">@DoKcommunity</a><br><a href="https://dok.community/">Website</a><br><a href="https://www.meetup.com/Data-on-Kubernetes-community/">Meetup.com page</a><br><a href="https://go.dok.community/register">Meetup registration</a></p><p>And I’ll leave you with these nuggets of wisdom!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUHkuPvVgICI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUHkuPvVgICI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUHkuPvVgICI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/367bb8a2bfe2c796a227510007dccab7/href">https://medium.com/media/367bb8a2bfe2c796a227510007dccab7/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58399e3be624" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-on-kubernetes-community/a-call-for-collaboration-announcing-the-data-on-kubernetes-community-58399e3be624">A Call for Collaboration: Announcing the Data On Kubernetes Community</a> was originally published in <a href="https://medium.com/data-on-kubernetes-community">Data on Kubernetes community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>