text stringlengths 0 2.46k |
|---|
**Adam Stacoviak:** What is your day like with issues? How many hours a day, either directly in issues, or procrastinating, do you spend on issues? |
**Jerod Santo:** \[55:57\] Procrastinating... \[laughs\] Wow. What a call-out. |
**Eddie Zaneski:** Yeah. So - surprise, Kubernetes isn't my full-time job. |
**Adam Stacoviak:** Okay... |
**Jerod Santo:** Oh, I thought it was. |
**Eddie Zaneski:** No. I used to work on the EKS team at Amazon. So I would spend most of my days on Kubernetes, and now I do stuff with supply chain security, and some other projects, like sigstore. It's an OpenSSL project. |
**Jerod Santo:** Yeah. |
**Eddie Zaneski:** But yeah, so we have a bug triage once a month that we go through, where we'll go through as a group... And the idea behind this was that knowledge transfer, where we can talk through the history and the context that people don't have. And we invite lots of new people. So if you're listening and you ... |
**Adam Stacoviak:** You went from twice a week to every other week, to once a month, real quick. |
**Eddie Zaneski:** I have a Kubernetes meeting every Wednesday. So bug triage is once a month, and then our general SIG meeting is twice a month. |
**Adam Stacoviak:** Gotcha. Okay. |
**Eddie Zaneski:** And so join us for that. It's github.com/kubernetes/community, and then the SIG CLI folder right at the top, it has meetings... So it's all public agenda, and it's all recorded, so... 9am Pacific time. |
**Jerod Santo:** Cool. |
**Adam Stacoviak:** There you go. |
**Jerod Santo:** Well, thanks for talking to us, Eddie. |
**Eddie Zaneski:** Yeah, thanks for having me, y'all. |
**Jerod Santo:** This was fun. |
**Adam Stacoviak:** It was a blast. |
**Eddie Zaneski:** Let's play Zelda... |
**Jerod Santo:** Let's play Zelda. |
**Eddie Zaneski:** That was awesome, guys. |
**Jerod Santo:** Yeah, man... |
**Eddie Zaneski:** Thank you so much. |
**Jerod Santo:** That was fun. |
**Break**: \[57:16\] |
**Adam Stacoviak:** Where should we begin? |
**Jerod Santo:** Dapr. |
**Adam Stacoviak:** Dapr. Let's begin with Dapr. |
**Yaron Schneider:** Alright. |
**Adam Stacoviak:** Open source, CNCF, graduated... |
**Yaron Schneider:** No, not yet. |
**Adam Stacoviak:** Not yet. Okay. Sorry. |
**Yaron Schneider:** \[59:48\] It's incubating. We will graduate at some point, but we're not rushing it. We want to make sure we get the most out of the CNCF incubating stage. We are doing lots of things in the CNCF, integrating with other projects... We really want to make sure we have this core integration with all ... |
**Jerod Santo:** Okay. So yesterday you said you started Dapr at Microsoft...? |
**Yaron Schneider:** Microsoft, yes. That's correct. |
**Jerod Santo:** And you're working for them, and you built Dapr as an open source project... |
**Yaron Schneider:** Correct. |
**Jerod Santo:** And then -- well, first of all, what was it? And then tell that story. What was Dapr when you built it then, and what happened next? |
**Yaron Schneider:** Yeah, so in 2018, I was at Microsoft and I was working for the Azure CTO, called Mark Russinovich. That was an incubations team whose job was basically to look for bleeding edge technologies and come up with innovative open source technologies that could really give Microsoft a boost in the ecosyst... |
**Jerod Santo:** Okay. A core tool so developers can focus on their business logic and not distributed systems problems, is that what you said? |
**Yaron Schneider:** Yes. Yeah. |
**Jerod Santo:** What are the distributed systems problems, and how does Dapr deal with them? |
**Yaron Schneider:** So for example, as a developer you have to make sure that your application is first of all secure, and second of all reliable. And that usually translates into a lot of boilerplate code that you as a developer need to write on your own, to basically make your application more secure wherever it's r... |
And then you have to write state, you have to manage state at scale; you might be writing to Redis, or DynamoDB, or Cassandra, or Google Firebase. But if you have multiple services running the same data all at once, you're probably going to want something like first write wins, or last write twins. And you're gonna hav... |
**Jerod Santo:** Right. |
**Yaron Schneider:** And so Dapr really gives developers these APIs that give them all these Pub/Sub async eventing paradigms and service-to-service invocation and stateful management paradigm so they can focus on what matters most of them. |
**Jerod Santo:** So would you describe it as a framework, or a toolkit, or...? |
**Yaron Schneider:** Yeah, I think a framework is a good definition of it. It's an API that you call, so it doesn't compile into your code. It's a sidecar architecture. So there's a process running next to your application, you talk to it via HTTP or gRPC, which makes the app really inclusive, because if you're a devel... |
**Jerod Santo:** Okay. And so there's a bunch of client libraries probably for different languages that talk to Dapr? |
**Yaron Schneider:** Yeah, there are. They make the development experience nicer. But if you want to, you can just drop down into HTTP and gRPC directly. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.