text stringlengths 0 2.46k |
|---|
• A managed version of Dapper is important for enterprises, as it reduces the operational burden on infrastructure teams. |
• Diagrid offers a managed version of Dapper, which takes away the pain of managing the control plane. |
• A serverless version of Dapper is also being developed, allowing users to run Dapper outside of Kubernetes on any compute platform. |
• The decision to leave Microsoft and start Diagrid was driven by the desire to build a distributed systems platform through Dapper APIs. |
• A company replaced their in-house application platform with Dapper due to its standardization and ability to focus on business logic. |
• A small development team is using the company's services to manage Dapper and focus on other tasks. |
• The company donated Dapper to CNCF to gain vendor neutrality and attract new contributors. |
• This has led to increased contributor and end-user growth, making it easier to commercialize the project. |
• Dapr is licensed under Apache 2, allowing for flexibility in commercialization. |
• The company welcomes competition and notes that multiple companies are commercializing CNCF projects. |
• The speaker and their co-founder created the Dapr project and are core maintainers, giving them a good understanding of its technical aspects. |
• The company's name is Diagrid, not Dapr Inc., to avoid trademark issues and to avoid being tied to a single project. |
• Dapr is a polyglot framework that can be used from any language, similar to Spring for Java or Micro for Go. |
• Dapr may not be suitable for extremely low-latency applications or those requiring specific features from cloud services. |
• The Dapr project is still evolving, with new features being added, including workflows, cryptography APIs, and document store APIs. |
• The company has plans to add many more APIs in the future. |
• The Open Source Summit North America 2023 coverage is complete. |
• The podcast thanks GitHub for sponsoring the event. |
• Upcoming episodes include Apple coverage and WWDC discussion. |
• Next week's episode will focus on pass keys. |
• The show thanks its sponsors, including Fastly, Fly, and TypeSense. |
[0.00 --> 7.98] Welcome back friends this week on the change law we are back at the Linux Foundations open |
[7.98 --> 13.76] source summit North America 2023 in Vancouver Canada. |
[14.02 --> 17.06] We have another anthology for you. |
[17.24 --> 20.34] This one is taking you to the cloud native world. |
[20.44 --> 22.70] This is after all a cloud native world. |
[22.78 --> 26.16] We're just all trying to operate in it on today's show. |
[26.22 --> 27.38] We're talking to Jeffrey Sika. |
[27.38 --> 30.50] Jeffrey is part of the CNCF. |
[30.62 --> 33.32] He works on the developer experience and programs. |
[33.66 --> 34.40] Eddie Zaneski. |
[34.50 --> 39.48] He's on the Kubernetes SIG CLI team helping to maintain the Kubernetes CLI. |
[39.90 --> 45.40] And also Jaron Schneider, co-creator of Dapper and founder and CTO at Diagrid. |
[45.90 --> 46.76] But it's a big show. |
[46.84 --> 47.48] So let's get to it. |
[47.56 --> 51.52] A big thank you to our friends and partners at Fastly and Fly. |
[51.74 --> 54.82] This pod got to you fast because Fastly is fast globally. |
[54.82 --> 56.78] Check them out at Fastly.com. |
[56.78 --> 62.10] And our friends at Fly help us put our app in our database close to our users all over the world with no ops. |
[62.40 --> 64.50] Check them out at fly.io. |
[64.50 --> 80.28] I'm here with Tom Hu, dev advocate at Sentry on the CodeCov team. |
[80.64 --> 83.60] So, Tom, tell me about Sentry's acquisition of CodeCov. |
[83.88 --> 87.12] And in particular, how is this improving the Sentry platform? |
[87.12 --> 94.42] When I think about the acquisition, when I think about how does Sentry use CodeCov or conversely, how does CodeCov use Sentry? |
[94.64 --> 97.76] Like I think of CodeCov and I think of the time of deploying. |
[98.00 --> 100.16] When you're a software developer, you have your life to go. |
[100.22 --> 100.68] You write your code. |
[100.74 --> 101.30] You test your code. |
[101.38 --> 101.80] You deploy. |
[102.18 --> 103.44] And then your code goes into production. |
[103.44 --> 105.20] And then you sort of fix good bugs. |
[105.50 --> 108.84] And I sort of think of that split in time as like when you actually do that deploy. |
[109.52 --> 112.62] Now, where CodeCov is really useful is before deploy time. |
[112.92 --> 114.48] It's when you are developing your code. |
[114.64 --> 117.12] It's when you're saying, hey, like I want to make sure this is going to work. |
[117.38 --> 119.40] I want to make sure that I have as few bugs as possible. |
[119.78 --> 123.14] I want to make sure that I've thought of all the errors and all the edge cases and whatnot. |
[123.64 --> 125.74] And Sentry is the flip side of that. |
[125.74 --> 128.72] It says, hey, what happens when you hit production, right? |
[128.76 --> 131.58] When you have a bug and you need to understand what's happening in that bug. |
[131.82 --> 133.32] You need to understand the context around it. |
[133.38 --> 135.92] You need to understand where it's happening, what the stack trace looks like. |
[135.92 --> 139.14] What other local variables, you know, exist at that time. |
[139.14 --> 140.34] So that you can debug that. |
[140.64 --> 143.02] And hopefully you don't see that error case again. |
[143.26 --> 146.38] When I think of like, oh, what can Sentry do with CodeCov? |
[146.42 --> 147.70] Or what can CodeCov do with Sentry? |
[148.12 --> 150.86] It's sort of taking that entire spectrum of the developer lifecycle. |
[151.40 --> 156.78] Of, hey, what can we do to make sure that you ship the least buggy code that you can? |
[157.06 --> 161.70] And when you do come to a bug that is unexpected, you can fix it as quickly as possible, right? |
[161.86 --> 164.76] Because, you know, as developers, we want to write good code. |
[164.76 --> 167.86] We want to make sure that people can use the code that we've written. |
[168.18 --> 170.08] We want to make sure that they're happy with the product. |
[170.22 --> 171.04] They're happy with the software. |
[171.16 --> 172.68] And it works the way that we expect it to. |
[173.04 --> 182.12] If we can build a product, you know, the Sentry plus CodeCov thing to make sure that you are de-risking your code changes and de-risking your software, |
[182.58 --> 186.68] then, you know, we've hopefully done the developer community as service. |
[187.26 --> 190.18] So Tom, you say bring your tests and you'll handle the rest. |
[190.28 --> 190.94] Break it down for me. |
[190.94 --> 194.42] How does a team get started with CodeCov? |
[194.76 --> 199.10] You know, what you bring to the table is like testing and you bring your coverage reports. |
[199.60 --> 202.40] And what CodeCov does is we say, hey, give us your coverage reports. |
[202.70 --> 208.70] Give us access to your code base so that we can, you know, overlay code coverage on top of it and give us access to your CICD. |
[208.70 --> 216.80] And so with those things, what we do and what CodeCov is really powerful at is that it's not just, hey, like this is your code coverage number. |
[216.80 --> 223.70] It's, hey, here's a code coverage number and your viewer also knows and other parts of your organization know as well. |
[223.70 --> 227.68] So it's not just you dealing with code coverage and saying, I don't really know what to do with this. |
[228.04 --> 233.16] Because we take your code coverage, we analyze it, and we throw it back to you into your developer workflow. |
[233.72 --> 236.68] And by developer workflow, I mean your pull request, your merge request. |
[237.04 --> 241.48] And we give it to you as a comment so that you can see, oh, great, this was my code coverage change. |
[241.48 --> 245.46] But not only do you see this sort of information, but your viewer also sees it. |
[245.58 --> 248.52] And they can tell, oh, great, you've tested your code or you haven't tested your code. |
[248.98 --> 255.28] And we also give you a status check, which says, hey, like you've met whatever your team's decision on what your code coverage should be, |
[255.34 --> 257.78] or you haven't met that goal, whatever it happens to be. |
[258.06 --> 265.02] And so CodeCov is particularly powerful in making sure that code coverage is not just a thing that you're doing on your own island as a developer, |
[265.48 --> 268.78] but that your entire team can get involved with and can make decisions. |
[269.26 --> 270.18] Very cool. Thank you, Tom. |
[270.18 --> 277.28] So, hey, listeners, head to Sentry and check them out, Sentry.io, and use our code changelog. |
[277.52 --> 283.32] So the cool thing is, is our listeners, you get the team plan for free for three months. |
[283.82 --> 286.90] Not one month, not two months, three months. |
[287.32 --> 289.62] Yes, the team plan for free for three months. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.