Podcasts about iops

Tiff and Dana address one of the most popular topics for Dental A-Team consultants: overhead! They talk about what it entails, where to start when looking to reduce it, critical questions to ask yourself about needs versus wants, and more. Episode resources: Subscribe to The Dental A-Team podcast Schedule a Practice Assessment Leave us a review Transcript: Tiff (00:00) Hello, Dental A Team listeners. Thank you for being here with us today. Thank you for listening. We say this every time, but we love what we do and we love bringing you so much valuable information. And the fact that Kiera can do all the podcasts she does blows my mind. ⁓ but she is a busy bee over there, and the fact that we get to do these as well is just really, really fun for us. It allows all of the consultants here on our team to really feel like we're giving back to you guys. So with that, I have Dana here with me today, and   Dana, gosh, we have been podcasting together for a really long time. I can't even put a number to it. And I remember, I don't know if you remember, but I remember I remember where I was sitting. I remember the thought process. And I remember it was me, you and Britt on a call on a Zoom link. And it was the first time marketing had said we want to do video with the podcast. And I was like, what? And video like was not, it was just like up and coming.   I didn't understand it. It was on Instagram. I was watching I was like, why am I watching you talk? Like the a podcast is to listen. Why am I watching you talk? And now I mean it's very normal and that's how I watch them. And I feel like I feel like it was like YouTube came back around, you know. But anyways, I remember that day vividly. ⁓ I don't remember what we were talking about, but I remember being like, I have to like do my hair. I'm gonna be seen.   DAT-Dana (01:23) Yeah. Yeah. I know it was   funny because we always could see each other, right, in those early days, but it was just like we weren't creating the video content for it. And I remember thinking exactly like who's gonna want to watch   Tiff (01:33) Yes.   DAT-Dana (01:35) us who's gonna want to watch us do this thing but then I see my kids literally like watching people play Minecraft and it's like their favorite thing and I'm like wouldn't it be more fun to actually go play? So I do feel like there is definitely this like niche of people like wanting to watch and like you know get a glimpse in of like the podcast world and just different worlds in general and so I agree with you. I remember the three of us just kind of being like who's gonna want to watch us talk to each other but hey we're so glad you're here.   Tiff (01:37) Yeah.   Yes.   It's true.   Yeah.   DAT-Dana (02:05) Yeah.   Tiff (02:06) Yes, I agree. And the three fur podcasts are hard. So hard when there's so many people virtually. And yeah, I r I remember the shock. I wish I could remember what the ⁓ podcast actually it was probably I bet you it was probably one that we did for Kiera. We probably it bosses day or something, yeah, 'cause if there are multiple of us. Anyways, that was that popped into my head this morning as I I always have to now have like prep for podcast time so I can like   DAT-Dana (02:12) Yeah.   Like Boss's Day or something like that. Yeah.   Tiff (02:35) just tame my hair or get my ring light just right. And I'm like, gosh, I remember the days that we did not have to do this. And then we have c new to Dental A Team consultants come on and I'm like, we're gonna podcast. And they're like stressed and I'm like, I get it. I just I get it. I saw them go talk yourself in the mirror for a bit first. You'll get used to it.   DAT-Dana (02:50) Yeah. Yeah.   I know   I remember in the early days I would always have to reframe my podcast because I'd see podcasting on my schedule and I'm like, ⁓ like I gotta get on. So then I just started reframing it. It was like time with Tiff, time with Britt, time with Kiera. And it's how I like kind of learn get over the like of the podcasting space. So I totally feel it when new consultants are like, I have my first podcast today.   Tiff (03:12) I love that.   Yeah,   yeah, and they all come to you, right? 'Cause I'll all schedule it and then they're like, Dana, what do I do? That's so cute. Yeah. I love the reframe. That actually like goes I think hand in hand with what we're talking about today. ⁓ but I think you can do that with anything and I have to remind myself, even like gosh, when I get up in the morning, I got up this morning and I went from for my walk and I was like, ⁓ this sucks and I was like, No, you get to be in the morning sun.   You get to move your body before anybody else in the house is awake. Like I think that's the part that's the hardest is like everybody else gets to sleep, you know? But you that reframe is so powerful. And we can look at a schedule and think I I look at my schedule and I'm like, shoot. This is so busy. Or gosh, I'm I'm like   So long today, and I have to reframe it often and be like, gosh, no, actually I get to do something really cool. And I get to wake up and go for a walk and I get to do these things or I get to go to an office and I get to be boots on the ground with other people. So I love that you mentioned that reframe, Dana. That was really smart. So today's reframe, which I love, I think this is one of the most popular conversations that we have. We get a couple of things here at Dental A Team. ⁓   We love everything that we get, but the most common, most popular things are systems, which we will help you with systems, I promise you. And there are thousands of podcasts I think that just Dana and I have done on systems and operations manual. So go look them up. We're not doing that today. And the second, which I actually really have grown to truly love, ⁓ is overhead cost reduction and and overhead analysis. And so many practice owners and leaders come to us and they're like, gosh.   what does overhead even mean? I know I had a conversation with a client last week that has been in the dental like consulting world for years and years and years. And w his question was what does that even what does it mean? Like overhead can mean so many different things to so many different people and so many different consulting companies. And for the sake of today's conversation and the sake of forever with Dental A Team know that when we say overhead, we are talking about top of the line   Whatever I always say if someone were to purchase your practice, what are the expenses they'd be taking over? Anything outside of that, your pay, your taxes, your debt, your debt will follow you typically, right? You can lump it into the loan, ⁓ but it's not overhead top of the line expense. So your debt, meaning your scanners, ⁓ your school debt, anything like that is outside of quote unquote overhead. So when we talk about overhead, it's top of the line and that had to that that   explanation, I think it can just vary. It can vary depending on who you're talking to. So today we wanted to reframe that, Dana Go. No, I love it.   DAT-Dana (06:08) and I don't want to interrupt you, but I think too just   just to be clear on overhead too, anything that you run through the business, right? Again, that's not something absolutely with your CPA, you structure it how you want. But understand that that's not an expense that somebody is going to take on when they take over the bracket.   Tiff (06:25) Yes, I love that. Thank you. Good clarification. so with this kind of reframe, every everybody's like reduce overhead, reduce overhead. And I totally agree. And a lot of a lot of companies, a lot of people, ⁓ a lot of strategists will come in and they're like, okay, what can we cut? And we for sure, like, we'll come in and look at what if there's space to make cuts, but our biggest piece is always we're not gonna spend a lot of time on it today because we've got a million other podcasts about it.   I think I just did one actually with Kristy not that long ago, but the first place we're gonna look is your collections. A lot of people will say, I need to over I need to produce. And I love the statement, you can't outproduce your problems. So if you're producing, producing, producing, producing, but you're still feeling like there's an issue. And if you're meeting the financial, like you're meeting your goal, your production goal, but you're still cash flow short, then there's an issue in your collections. And so look at your collections and Dana.   I would love to hear quick snippet, what are the areas that you tackle when it comes to overhead and it comes to collections? And then I want to talk about the reframes and the other pieces.   DAT-Dana (07:33) Yeah, so you're exactly right. The first thing I'm gonna look at is the collections number. I'll look at the total, like what is the total percentage and like what profit point do we need to get to when it comes to collections? And then the very next thing I'm gonna look at is your AR because honestly and truly I've been able to get practices out of cash flow crisis, out of really feeling that pinch simply by going after already produced   ⁓ monies. And so I think that those are usually the things that I look at. Okay, what are we collecting? What does our profit point need to be for healthy AR?   Right. And and obviously we're gonna talk about is that possible? How do we get your schedule to get you there? But then the very next thing I'm gonna look at is AR. Is there money that I can just quickly tackle that's already been produced that's gonna help the collections problem? So I'm looking at the total collections, collections percentage, and then what's sitting in AR, because if I can tackle that and make a really quick difference, ⁓ sure, we can budget things, we can line item your PL, we can we can chop where we need to, but those things are often the fastest, easiest, quickest fixes.   and like you said, you like outproducing the problem. If I can fix AR and then we can create systems that it doesn't happen again, oftentimes we don't even have to really touch production, right? Because we're already producing pretty well in a lot of these cases. So those are that's kind of where I start.   Tiff (08:46) Yeah.   Yeah, I love that. And it's something that makes such a massive difference. Knowing one, knowing your numbers, knowing what your numbers mean. So knowing your overhead, knowing your outgoing expenses is massive. And then looking to see, okay, well, if these are my outgoing expenses, what do I need to collect in order to profit? Right. And then if we're not collecting that, is it because production isn't where it needs to be? So what's our what's our bare minimum?   And is collections meeting that or is production meeting that so that collections can meet our bare minimum. If production is or is way above and our collections is just tanked, like I saw somebody the other day that was like 83% collections. They're like, we gotta produce more. And I Yeah, absolutely. If we want to maintain 83% collections and get your overhead in line, you for sure have to produce more. But also we can tackle your collections and get your collections up to that ninety-eight percent that it should be or above, and really not have to work   you harder as the provider work our numbers harder and get that collections up. It also kind of flows into Dana, I think the capacity that we just recorded a podcast. So probably the podcast ahead of this one I would assume is is about capacity. And I think that capacity conversation flows into this one really, really well. So all right, collections.   Go do it. We will harp on that for days, but go do it. If you need help with it, you're not sure, you don't know how to analyze it, you need help with your numbers, Hello@TheDentalATeam.com. We are honestly and truly here to help you. We will provide you as much information as we possibly can to get you on the right track. Now, something else that we like to do within that, and we talked about this on capacity, we talked about analyzing ⁓ fee schedules, right? But then we also need to analyze expenses. So when we're really looking at things and we're saying, okay.   Great, this is my overhead. I like to think, okay, does it have to be my overhead though? So a lot of people will look at staff cost, the employee cost. I actually I look at it, I kind of glaze that, you guys. I don't, I don't like to touch the staff cost unless it absolutely is extraordinary and there's maybe team members that are taking advantage or you're feeling like there's something culturally wrong in your practice, then I'm gonna say, okay, great.   Let's really take a look at this and make sure that we're being efficient with our time. We're not in overtime. We're not in those spaces. But I'm gonna kind of glaze at that unless there's a red flag somewhere else. And then I'm gonna look at those other expenses as well. And something that I really love to do is to analyze what do we need versus what we have. It reminds me of when Brody was little, we'd go to the store and he'd be like, Mom, is this a want or a need? Is it on your list? Is you have are you getting it because you just want it and it sounds exciting?   Or do we actually need this? And Dana, I love the conversation that you have around. I'm gonna say like analyze your vendors, analyze your contracts with vendors, but I love the conversation around ⁓ the wants versus needs when it comes to scanners, when it comes to mills. And I love I I miss the conversation actually. I miss the conversation of negotiate with your labs. And I miss that conversation because   I think that the mill has become such a bandwagon thing. It's been around for so long and it's such a bandwagon thing that everybody's that jumped into. But I love your your like evaluation of is it necessary? Is it actually going to save us the time and the money and get us the results that we want? And I would love, Dana, for you to talk through some of that and how you help your clients decide. Because I'm not against the mill, I'm not for it. I'm for it for the practices that it works.   And I'm for making sure that it's going to work and it's gonna do its due diligence. So what how is that conversation for you, Dana, when you talk to your practices about it   DAT-Dana (12:44) Yes. I love this conversation too, too. I   think first and foremost, I always want to know when when somebody wants to purchase something big like that. So whether it's a new scanner or whether it's a mill, like why.   Why do we want to purchase it? Is it because we have a scanner that we constantly use and we're constantly pulling and we never have it in the like appointment times that we need? So then we need to talk about adding another scanner. Is it that like we need another tool to show patients, but like could we just do IOPs a little bit more until we've got the budget set for the scanner? I'm not saying no to scanners. I'm not saying no to mills. I'm just saying, why do we want it? Is it the right time and is it going to do what you anticipate it's going to do as far as your budget goes?   Because I think we can talk about scanners and what's going to add so much more to my production. Okay, well, it is, but when are we going to use it? How often are we going to use it? Who's going to use it? How are we mapping it out to make sure that it really is putting more production on your schedule and it really is reducing your lab fees? Right. Scanner is a great tool for negotiating with a lab, but are you going to do that? Are you going to do the negotiations? Are you going to send them enough work to make it worth having the scanner?   Same thing with the mill. I'm always asking like why, right? And I know that kind of the mill is the hot spot or the mill is like the next big thing. And I think sometimes, you know, I hear a lot from doctors, well, it's gonna buy me back a lot of time. Well, it's only gonna buy you back time if you're going to let your assistant, right, help design and do the actual milling. If you're not gonna let that happen, then we're actually using more of your time than and sometimes it's not will you let them, it's do you have the capacity within your assistant team right now to be able to allow them.   Tiff (14:07) Yeah.   Mm-hmm.   DAT-Dana (14:21) to do those things because maybe we're short staffed in that area or maybe assistants are really hard to find. Well then maybe now's not the time to bring on the mill because it's actually going to use more of your time versus less of your time. And then you know all of these purchases typically come with either a large payout, right? Or a decent size loan that we're paying every single month. And so I like to kind of reverse engineer with my practices so they know cold hard facts how many crowns they have to do every single month.   to make that loan payment worth it or make that payout out of their emergency fund or their growth fund or wherever they're pulling that funds from. Hopefully not their emergency funds, but sometimes right, doctors get wild on us and it feels like an emergency to get that.   Mill. So knowing exactly how many crowns you have to do every single month. And then I'm saying, okay, let's go back through the last year. Let's see, did we even do as many? Because if we didn't do as many, then now's not the time. Let's get to that many crowns every single month, then take a look at the mill. Because so often we think, hey, the mill is going to save me on lab fees, but you have to do so many of them for it to save you on lab fees. And again, I'm not pro mill. I'm not like I'm neutral when it comes to mill. I think it's a great tool, but it's not the best tool for every   Tiff (15:25) Yeah.   Mm-hmm.   DAT-Dana (15:35) practice at that exact time. I think you really have to look   At and crunch things when you decide to make those purchases and really look at it as is it truly going to give your time back? Is it truly going to give you your lab fees back? Is it truly going to up your patient experience or up your diagnosis or whatever it is? Because that is when it makes it worth it. So I just like to like have the conversation, review the numbers together, and kind of say, hey, like this is the reality of the purchase. I, you know, I am.   Totally understand the like purchase in the feels, right? I get that. I've done it. I'm human. I think we've all been like, but this is gonna feel so good when I have it. But I think look at the numbers and make sure because these things can really hit your these these debt services can really hit your profit points if it's not set up correctly and you don't know kind of the benchmarks you have to hit to make it help with profit versus hurt.   Tiff (16:11) Yeah.   Yeah.   Absolutely. I think it's so beautiful. And a follow-up to that too is if you already have the mill, you already have the scanner, you already made the purchase or the laser, Dana, as you were talking, I was like, the lasers, the lasers. There's so many there's just so many really cool tools that dentistry has that makes us feel like we've got to jump on it to be the most progressive, to be the most exciting, to stay up with the times, to to not fall behind. And really they're just fun and exciting. It's like   ⁓ Canva and you know we only had Photoshop and then Canva came out and then we had, you know, all of these different opportunities. And it it can be easy to jump on board with them. So if we already have jumped on board, we didn't have this conversation, or maybe we did, and then gosh, we're just falling a little bit short. This is the overhead analysis as well. This all flows into that overhead analysis. So as you're looking at your overhead and you see those   those loans under on you have your bottom you have your top line and you have a bottom line. And at your bottom line, when you see those other loans in there and you're like, gosh, Def, Dana, I just I'm not using the scanner as much as I thought I did. I know both of us have I all of our consultants are really, really fantastic at having conversations like this that say, okay, great, why? Dana, you said something earlier, you said it asking more questions, right? Like I want to know, I want to know why you want it.   what it's gonna do for your practice and then reverse engineer it. And we are really great at pulling out the why for anything. So if you're not, if you bought it and you're not using it, we're gonna say, well, why aren't we using it? Is it because it's not the tool that we needed or we wanted and or we don't have the patient base for it or is it because we're not trained, we're not holding accountabilities. And ultimately, if this thing isn't working for your practice, it's not doing what you wanted it to or gosh, you just hate it. You don't like it. You don't want to use it.   This is a conversation with the company that you can have. You can call the company and say, Hey, what can I do? How can I how can I get out of this? I've had ⁓ I've had doctors that have had this conversation with them and they do have like a smaller buyout, right? They're like, Well, we'll buy it back from you, but you're gonna it's kind of like taking a car in and you you're you know, you're under.   So you you owe a little bit more on your car and then you owe on the car that you're buying. So it kind of sucks because you do have to pay that out, but could getting out of that contract early, sending the equipment back, save you in the long run because you haven't paid that total balance. Or a lot of doctors will call and they're like, yeah, absolutely. I have a doctor actually who's looking for one that might buy it from you.   And so you can you can sell this equipment as well if it's not working for you. So I don't ever want doctors to really just feel so stuck in the decisions that either they've made or that they want to make and you have that kind of decision paralysis. So as we're going through that looking at ⁓ cost control and overhead control.   Part of the conversation as well. So there's the projecting side and really looking at do I do I need this? What can it do? And then there's the evaluation side of is this working for me? And Dana, I think that same conversation when it comes to like marketing. Are is my marketing ROI coming in? Is it getting me what I what I thought it was going to? There's magazines investments, there's all of these like hottie-totty ⁓ marketing efforts that are coming around right now. They're trying to like really reinvent a lot of wheels.   And projecting and seeing, does this fit my avatar? Is this gonna work? Gosh, your telephone company, I know our like cable and internet. We don't even have cable, but it's the same company, right? And I'm like, why are we paying for cable and internet? And it just jumped like $90. And I'm like, what the heck? It's a call and a conversation with your vendors and looking at, okay, am I getting the most value for what I'm spending? And that I think Dana helps us to calm the storm.   Because what happens typically is we're like, okay, I gotta produce more in order to afford my life. And it's just like personal, right? I gotta work more in order to afford the lifestyle that I want. Well, maybe the lifestyle that you want can be had with less debt or less stuff, you know, and really evaluating your quote unquote lifestyle in the practice and out.   DAT-Dana (20:43) Yeah, I agree with you because like dental offices, do we have to spend money? Do we have expenses? Yes, absolutely. Let's make sure those expenses are doing what we need them to do and and we have an ROI on those expenses. And I do feel like just doctors highlighting like, don't forget those bottom of the line things because oftentimes it's like, hey, my payroll's in line, my rent's in line, my marketing is in line, everything's in line, but I don't have any profit at the end of the month. And I think don't forget to take a look at oftentimes I think there's an impression of doctors that like those below the   aligned things are like fixed expenses and oftentimes they are variable expenses that we can do something about it. We can make changes like you said, sell it or start using it, right? Or incorporating a way for it to help us produce or collect more. I think just don't forget those bottom of the line things and don't look at them as hey, those are fixed things, right? A lot of times those items aren't. We can either move the needle as far as using them or move the needle as far as offloading them.   Tiff (21:15) Uh-huh.   Yes.   DAT-Dana (21:42) Right. I just had a conversation with the practice. Like, why do we have two scanners? Right. Like, why do we need them? Walk me through it. If if you can walk me through why and it makes sense, totally keep your scanners, utilize them, have it help you. Right. But if we don't need them, then let's not have that sit there every month and pull from that profit that you so desperately need.   Tiff (21:45) Mm-hmm.   Yeah, I love that conversation and I think it's something that's a piece of value that the consulting team brings to our clients that I think is totally undervalued. I know I have clients that are like, Teff, I wanna buy this thing. And I'm like, Okay, cool. Like, tell me why. How are we gonna afford it? Great. I have a doctor that was like, I like this scanner better, but I bought this scanner before I knew that this scanner was better. And I was like, Awesome. Well it sounds you want that scanner. He's like, Yeah, I'm gonna get it. And I said, Cool, what are you gonna do with that scanner that you don't like?   Because that one is still being paid on. It's still in your office. And he's like, okay. So it's like we have this innate ability, right, to see things very, very cleanly. I had a conversation just last week with a client that was like, Tiff, what do I do? And it was like a personnel thing, right? I said, Listen, my job and the and the superpower that I have for you is to be very black and white in business. I'm not emotionally attached to what's going on in the practice. I I love you, I love the practice, I love the team.   And I I have emotions towards you, but I'm able to separate it out and say, hey, do this, don't do this, or these are the black and white opinions that I see. These are the pros and the cons that I can see. I'm not emotionally attached to one scanner is better than the other. I'm emotional, I'm not emotionally attached to the money that's coming in or going out. I am neutral and I'm able to say it is or it isn't. And so that value, that ROI is not always really easy to see.   in the numbers until you look backwards and say, gosh, actually I sold that scanner because of or I didn't buy that and gosh, I'm so happy. Or I was able to invest in my team because I could see my shortcomings or my accountability faults or the accountability that Dana was able to give me so that I could give my team like those spaces are just so   valuable in this overhead analysis is huge. And I know you and I do it often. I know the rest of the consulting team does. Gosh, Kristy, Kiera likes to say she's like a truffle hunting ⁓ little, you know, little piggy out there finding the dollars. And that's how she does it as well. And Nikki and Pam and all of you know, Diana, every one of us are out there looking for those dollars from that black and white kind of business mindset because it's easier for us as a pulled out   Peace, right? And Dana, I just think that is a space that doctors, I can't imagine making those kinds of decisions by myself, right? Even just as simple as purchasing a mill. Like because it's so it's like walk walking into Louis Vuitton with a credit card with no limits and expecting me to not leave with a purse, right? Because in my head it's paid for, it's done, it's it's good.   But then on the flip side, I've got expenses and other things and they've always got just gotta have that person who can be that sound mind.   DAT-Dana (24:58) Yeah. Yep. I agree with you.   Tiff (25:00) All right, Dana, so overhead cost analysis. ⁓ I would say, and I think Dana, add anything you can think of. My pro thought process is figure out your bottom line first of all. Figure out what are your costs, your fixed costs that aren't changing. If someone were to purchase your practice, then then look at what's left over. How much debt do you have? what do you want to be making? Are you paying yourself and are you paying yourself what you want to be making?   And are you saving money? So what do those buckets look like? That to me is your is your bare minimum. You have your bare minimum of this is what it takes to keep my practice open and my employees paid. And then you have your bare minimum of this is what I want my practice to look like. So I like to add that fluff in there. I know Dana does as well. We have our bare minimum and then we have our bare minimum. And our our second bare minimum is the number that I work from ⁓ and tack on a little bit extra. So overhead analysis, look at what your numbers are, look at what your   DAT-Dana (25:46) How many? Yeah.   Tiff (25:55) Collecting, always look at collections and then look at what your debt looks like and look at what your spending is. Is there anywhere in there that can be negotiated? Is there anywhere in there that maybe we need to start using a tool a little bit more to get it paid, paying for itself? Just like you want your team to pay for themselves, you want your equipment to pay for themselves as well. Dana, is there anything you can think of that I missed that I didn't add in there as an action item that they can scurry on home to do?   DAT-Dana (26:24) No, I think I think that those are great tools for them to really be able to slice and dice and look at those pieces.   Tiff (26:31) Awesome. All right, guys, go do the thing. Pull up your PLs, pull up month by month, pull up year to date, pull up last year's, and look at what your expenses truly are. And when you get to the point that you want some third-party perspective, some eyes on it, if you're a current client, you should be doing this with your consultant too. So do it. I want you to know how to do it and I want you to do it with your consultant as well. If you're not yet a consultant, you're ⁓ someone who is a listener and you want you're not a consultant, you're not a client.   You're a listener and you want help with this, please reach out. Hello@TheDentalATeam.com There's also a link on our website, TheDentalATeam.com, that you can schedule a consult with us and they'll help you run through a lot of that information as well. We are here to help. So let us know how we can best serve you and how we can help you in the short and the long run. Hello@TheDentalATeam.com. All right, guys, and we will catch you next time. Thanks so much.  

Send us Fan MailWhat's New in Cloud FinOps: May 2026 Monthly RecapIn this combined monthly recap for May 2026, Frank Contrepois and Stephen Old dive into a vast array of updates across AWS, Google Cloud, and Azure, with a special focus on the evolving landscape of AI FinOps, hybrid cloud challenges, and a barrage of storage news.The Expanding Scope of FinOps: From Data Centre to AIThe discussion opens by exploring the expansion of FinOps beyond the public cloud to encompass on-premise data centres, software, AI, and sustainability. A central theme is the application of the FinOps Open Cost and Usage Specification (FOCUS) to on-premise environments. Stephen shares firsthand experience transposing software data into FOCUS to create a converged platform, highlighting the fundamental data challenges, from ingesting contract data to managing the high velocity of cloud data.The conversation then shifts to the burgeoning role of AI, noting its inclusion alongside SaaS and professional services in the modern FinOps scope. This introduces new forecasting challenges, as traditional 18-month budget cycles clash with the rapid pace of weekly AI model releases.A critical point is also raised regarding sustainability. The hosts discuss Amazon's board rejecting a shareholder proposal for detailed climate disclosures, which poses a significant challenge for companies needing granular data for CSRD and SEC compliance.Major Cloud Updates: April 2026AI & FinOps Visibility:A major theme is the improvement in attributing AI spend. A game-changing update from AWS means Bedrock API calls now automatically record the IAM identity (user or role) of the caller directly into CUR 2.0 and Cost Explorer. This eliminates the complex need to reconcile CloudTrail logs to determine who is driving Bedrock costs.Similarly, Amazon Q is now embedded in the AWS Cost Explorer, allowing users to ask natural language questions about their spending (e.g., "Why did my RDS costs spike last month?"). This conversational analysis approach comes with a free tier of 50 queries per month.On the Google Cloud side, a new billing overview widget for Gemini and Vertex AI spend is now in preview. Google is also introducing a "FinOps Explainability Agent," an autonomous AI agent to investigate AI cost drivers, and "Spend Caps" (Private Preview) for services like AI Studio and Vertex AI, which provide crucial cost control by pausing API traffic when a budget is hit.For those managing GPU workloads, Amazon ECS managed instances now support NVIDIA GPU metrics in CloudWatch Container Insights, enabling real-time visibility into GPU utilisation and health to optimise expensive accelerated computing.Cost & Usage Reporting (CUR) Enhancements:There are hints of a potential enhancement to AWS CUR 2.0, which could see new columns added to directly link API calls with costs, revolutionising cost allocation. AWS has also introduced:Scheduled Email Delivery for Billing Dashboards: Securely send reports to stakeholders without console access.Billing Conductor Pass-Through Plan: Simplifies centralised billing for billing transfer users.Cost Optimization Hub CSV Downloads: Easily export savings recommendations.Find out how to leverage CUR for security: "Identifying security risks using AWS cost and usage report data"Compute & Database Innovations:AWS: Released a wave of 8th Generation Intel Instances (C8i, M8i, R8i and network-optimised versions) powered by custom 6th Gen Xeon processors. EC2 Capacity Manager also now supports tag-based dimensions, allowing for more granular capacity optimisation. Amazon Aurora Serverless now boasts up to 30% better performance and, crucially, scales down to zero, a cost-effective option for unpredictable agentic AI workloads.Google Cloud: At Google Cloud Next, they announced both ends of the performance spectrum. The 8th Generation TPUs (v8t for training, v8i for inference) offer massive scale and performance-per-dollar improvements. In a move to democratise access, Google also made fractional GPUs (1/2, 1/4, or 1/8) on the G4 series generally available, a game-changer for cost-effectively running smaller workloads. The GKE workload recommender is also now integrated into the FinOps Hub.Azure: Now supports NVIDIA's powerful H100 and H200 GPUs on Azure Red Hat OpenShift (ARO) for large-scale AI/HPC workloads. For database users, the GA of Premium SSD v2 for Azure Database for PostgreSQL promises significantly higher IOPS and better price-performance.A Deep Dive into Azure Storage:The episode covers an "overload" of Azure storage updates with significant FinOps implications:Minimum Billable Object Size: From 1st July 2026 for new accounts (and 2027 for all), objects smaller than 128KB in cool, cold, and archive tiers will be billed as if they are 128KB.Smart Tier for Azure Blob & ADLS (GA): To mitigate the above, this feature automatically tiers data based on access patterns but introduces a monitoring fee for objects over 128KB, creating a new optimisation puzzle.Azure NetApp Files (ANF) Ransomware Protection: Now GA and included as part of the service at no extra charge.Finally, the hosts tackle "The Big Silence on Memory Prices," noting that despite DDR memory prices soaring 300-400% from mid-2025 lows, the hyperscalers have remained silent, absorbing the cost and making it difficult for smaller providers to compete.Explore the official announcements:AI Bill of Materials Whitepaper: www.wiz.io/go/ai-security/ai-bill-of-materialsAWS Article on Amazon Q: https://aws.amazon.com/blogs/aws-cloud-financial-management/transforming-finops-with-the-latest-amazon-q-cost-capabilities/ 

We take a deep dive into Amazon S3 Files, AWS's exciting new managed file system backed by S3! We kick things off by exploring why S3 isn't a traditional file system, covering everything from the lack of true directories and atomic renames to immutable objects and POSIX access control differences. We then walk through the existing solutions people have used to bridge that gap, like S3FS FUSE, MountPoint for S3, FSx for Lustre, and Storage Gateway. From there, we get into the heart of the episode: how S3 Files works, how to set it up, and how it uses EFS under the hood as a caching layer. We share our own real-world benchmarking results comparing S3 Files against various EFS configurations across Lambda and Fargate, and we discuss a real customer project where we put S3 Files to the test. We also cover the important caveats like eventual consistency, the 60-second write-back delay, the lack of cross-account bucket support, and the cost model so you can make an informed decision.Resources mentionedEpisode 124: S3 PerformanceEpisode 95: Mounting S3 as a FilesystemAmazon S3 FAQs: S3 FilesfourTheorem S3 Files demo code on GitHubAmazon documentation: Understanding how synchronization worksSponsor Thanks to fourTheorem for powering AWS Bites. We help teams build cloud systems that are simple, scalable, and cost effective. Visit fourtheorem.com.Chapters00:00 Introduction: Why S3 is amazing but not a file system, and what S3 Files promises to solve01:47 Why S3 is not a file system: no true directories, immutable objects, no atomic renames, expensive listings, and POSIX differences05:23 Existing solutions for mounting S3 as a file system: S3FS FUSE, Python fsspec, Hadoop S3A, MountPoint, FSx for Lustre, File Cache, and Storage Gateway07:16 How S3 Files works: NFS-based access, EFS caching layer, streaming from S3, and supported compute services like EC2, ECS, EKS, and Lambda09:49 Setting up S3 Files: buckets, file system resources, import and expiration rules, mount targets, access points, VPC requirements, and NFS port configuration13:42 S3 Files performance numbers from AWS documentation: throughput, IOPS, latency figures, and why real-world benchmarking is recommended15:39 Benchmarking S3 Files vs EFS configurations on Lambda and Fargate: small and large file reads and writes, memory/CPU impact, and key findings19:48 Downsides and limitations: NFS only, no hard links, no atomic renames, eventual consistency, the 60-second write-back delay, and large-scale rename performance warnings23:05 Real-world project experience: a SaaS multi-tenant architecture, cross-account bucket limitation discovered, and how the team worked around it27:52 Cost breakdown: EFS-equivalent cache pricing, S3 storage costs, reads from cache vs. S3 directly, and how S3 access tiers still apply29:50 Final recap and take: when S3 Files shines, when to be cautious, mixed access pattern warnings, and an invitation to share your own experiences33:42 ClosingSend us your AWS questions Do you have any AWS questions you would like us to address? Leave a comment here or connect with us on X/Twitter, Bluesky, or LinkedIn: Eóin: Bluesky | LinkedIn Luciano: X/Twitter | Bluesky | LinkedIn

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!On the product side, everyone is getting Computer - Perplexity, Manus, Cursor, and so on. Meanwhile on the research side, agentic evals like TerminalBench and GDPVal are also assuming computer (Harbor). On both ends, the consolidating LLM OS stack has become a standard toolkit, and Daytona is one of a small set of AI Infra companies that are booming because of it.“The end of localhost” has been Ivan Burazin's obsession for more than a decade.Something that is all too familiar…Long before agents became the default way people talked about software development, Ivan was already chasing the idea that development should not depend on a fragile local machine. CodeAnywhere, one of the first browser-based IDEs, was an early attempt at that future: move the development environment into the cloud, make setup reproducible, and free developers from the endless “works on my machine” tax.The thesis was directionally right, but the market wasn't ready yet.However, agents changed that. They do not care about a laptop, desk setup, or favorite editor. They need a computer they can access through an API: something stateful enough to keep working, fast enough to spin up instantly, flexible enough to resize, isolated enough to be safe, and composable enough to run the messy real-world workflows that real software engineering actually requires.Daytona isn't just selling “sandboxes” in the narrow code-execution sense. It is the latest version of Ivan's original localhost thesis.In this episode, Daytona's CEO joins swyx to explain why AI agents need more than code execution boxes: they need composable computers, stateful sandboxes, instant startup, dynamic resources, and infrastructure that can survive workloads going from zero to 100,000 CPUs.We go deep on the new agent compute market: Daytona's hard pivot from human dev environments to AI sandboxes, the New Year's Eve MVP that customers begged for, why Daytona runs on bare metal with its own scheduler, how one customer runs almost 850,000 sandboxes a day, and why RL/eval workloads went from 0% to roughly 50% of usage in just months. Ivan also explains why agents need Windows and macOS machines, why CLI may matter more than MCP, why Kubernetes is painful for this workload, and why the future AI cloud may look more like Stripe than AWS.We discuss:* How Daytona grew out of CodeAnywhere, Shift, and the “end of localhost” thesis* Why Daytona pivoted from human dev environments to AI sandboxes* Why agents need composable computers instead of disposable code execution boxes* The New Year's Eve MVP that customers chased API keys for* Why Daytona chose bare metal, stateful snapshots, and its own scheduler* How Daytona spins up one sandbox in ~60ms and 50,000 sandboxes in ~75 seconds* Why Daytona's biggest customer runs ~850,000 sandboxes a day* How RL/eval workloads create zero-to-100,000 CPU spikes* Why RL workloads went from 0% to roughly 50% of Daytona usage* Why customers compare Daytona against EKS/GKS and say they're “never going back”* Why every AI agent may need a computer, including Windows and macOS environments* The Apple licensing constraints that make macOS sandboxes hard* Why CLI gives agents more power than MCP* How open source helps agents integrate Daytona* Why agent-generated PRs may break today's CI/CD assumptions* Why AI SaaS companies reselling tokens may face a cold shower* Why the AI cloud may look more like Stripe than AWSIvan Burazin* LinkedIn: https://www.linkedin.com/in/ivanburazin* X: https://x.com/ivanburazinDaytona* Website: https://www.daytona.io* X: https://x.com/daytonaioTimestamps* 00:00:00 Hook* 00:01:12 Introduction* 00:03:15 CodeAnywhere, Shift, and the end of localhost* 00:05:58 What Daytona is: composable computers for AI agents* 00:08:07 The pivot from dev environments to AI sandboxes* 00:10:17 The New Year's Eve MVP and customers begging for API keys* 00:12:56 Bare metal, stateful sandboxes, and Daytona's scheduler* 00:17:28 60ms startup, 50,000 sandboxes, and 850K daily runs* 00:21:53 Spiky RL/eval workloads and the new agent infra problem* 00:28:12 RL workloads, Kubernetes pain, and dynamic resizing* 00:33:31 Why every AI agent needs a computer* 00:38:48 macOS sandboxes and Apple's licensing problem* 00:44:28 Why CLI may matter more than MCP* 00:48:11 Open source, GitHub stars, and agent integration* 00:53:11 Git, CI/CD, and agent collaboration bottlenecks* 00:58:15 Founder life and building a 25-person infra company* 01:02:44 AI SaaS, token resale, and API-first business models* 01:06:10 GPU sandboxes, data centers, and compute growth* 01:09:48 Why the AI cloud may look more like Stripe than AWS* 01:11:26 Closing thoughtsTranscriptIntroduction: Daytona, CodeAnywhere, and the End of LocalhostSwyx [00:00:02]: Okay, we're in the studio with Ivan Burazin, CEO of Daytona. Welcome.Ivan [00:00:07]: Thanks for having me, man.Swyx [00:00:08]: Ivan, you and I go back.Ivan [00:00:10]: Way back.Swyx [00:00:11]: How I don't even know how, you found, did you reach out or, for Shift.Ivan [00:00:17]: I reached out to you. The reason was you - we were just - we were thinking about I was one of the co-founders of CodeAnywhere, the first browser-based IDE, and so we were thinking a long time of, localhost should die. And you had this article.Swyx [00:00:29]: End of localhost.Ivan [00:00:30]: Then I reached out to you because of that, and then we talked, and I was actually at a different job and learning about I was the head of, developer experience, and you were quite well-versed in that, and I actually reached out to you, among other people, how do we go about that? What are the key things and whatnot at this point in time? And you were nice enough to take the call, and I remember I was late on your call with you.Swyx [00:00:51]: I don't remember.Ivan [00:00:52]: I remember because I was with my then I'm thinking of a girlfriend or wife at that point in time, I'm not sure. It's the same person, so that's great, and I was late ‘cause we were, in, Italy on, vacation, and then I was late for something. I felt so bad, and you were so nice to be, good about.Swyx [00:01:10]: The reason I'm nice is because I'm also late to other people, so it's like, who's, who's without sin here, yeah, so I have to, for those who don't know, InfoBip Shift, there's this whole thing that, you did in the past, and, and that was basically one of the inspirations for me starting AI Engineer, which is like, I have to thank you for giving me that push to be like, “Oh, you can, you can build and sell conferences?”Ivan [00:01:34]: I remember you asked you asked me at the beginning to give me advisory shares, and I was so focused on what we were doing, I said no, and I should've took the advisory shares. So I'm sorry, dude. But anyway.Swyx [00:01:43]: We're not, we're not venture backed.Ivan [00:01:44]: No, it doesn't matter.Swyx [00:01:45]: It's Yeah, anyway, so I think what's impressive about you is that CodeAnywhere is the thing that you've been trying to build, and, you kind of put it on hold and then came back after InfoBip. Just give us the story, do you - the story and the origin story, going into Daytona.From CodeAnywhere and Shift to DaytonaIvan [00:02:05]: Sure. Like, really way back, me and my co-founder have been together. I say this, I've said this multiple times, it's like we were married and divorced and married. Some people actually ask me is my co-founder my partner. they thought it literally. It's not literally, but we have done multiple companies together, and to your point, we had this shift where we went from the CodeAnywhere to the conference called Shift, and then back to, Daytona. We originally started stacking servers, doing like virtualization in the early 2000s and, routers and doing basically all these things, at a foundational level, and that was a services company which we sold to focus on what my co-founder actually invented, which was the very first browser-based IDE, right, I say the first. Before us was actually Heroku. They did it for a very short time until they became Heroku. But outside of them, we were the only one, and it was called.Swyx [00:02:55]: There was Cloud9.Ivan [00:02:57]: Cloud9 came out slightly after us. There was Replit, which came out when we stopped doing it, Replit came out, and they have been successful since then, which is great. There was Nitrous.io. There was quite a few that existed at the time, but it was like too early. But the interesting part is that we, at that point in time, because there was no VS Code, there was no Kubernetes, and Docker had just started when we Or I'm not sure if it was even public at that point in time. And so we had to build everything to the whole stack ourselves and that was the key learning that we brought into and that we've been using in Daytona today. So it was super early. There's about 3 million people used CodeAnywhere. It was slightly, it was angel-backed more than venture-backed. We ended up paying everyone back because it didn't have that sort of scale. But, three years ago, we started something similar with Daytona, which is not what we are today, but it was automating dev environments for human engineers, the basically the underlying stack of CodeAnywhere. And then we did a hard pivot last January to sandboxes. And so here we are.Swyx [00:04:01]: Historic pivot, yeah, and, it's one of those things where, I had independently invested in CodeAnywhere, but also in E2B, and then both of you pivoted into the same thing, and I'm like, “F**k.”Ivan [00:04:12]: You invested, you invested in Daytona. You invested in Daytona. But you were the first If we had not got your check, we wouldn't have done it.Swyx [00:04:18]: No way.Ivan [00:04:19]: No, it was like, “We have to get him on board first,” and you were that kicker that we, that got us off the ground.Swyx [00:04:23]: No, because you were putting me on your pitch deck, man. I was like, “Man, this is like a good trip if I don't invest.”Ivan [00:04:29]: That's because it was your quote. It's like we.Swyx [00:04:30]: Yeah. It's the end of localhost.Ivan [00:04:31]: Did a bunch of research about end of localhost and who was interested in that,.Swyx [00:04:34]: No, that's like, I put, I wrote that blog post, and every single company in that field reached out to me, and then every VC who was receiving those pitches then also had to call me and, talk it, talk through it with me.Ivan [00:04:47]: It's finally happening though.Swyx [00:04:48]: It was really super interesting.Ivan [00:04:48]: It's finally happening.Swyx [00:04:49]: It's finally happening.Ivan [00:04:49]: Yeah, it's finally.Swyx [00:04:49]: It's finally happening, with maybe sort of non-human users. Yeah, so what is Daytona today? Let's get like a quick description. I'm wearing the shirt.What Daytona Is Today: Composable Computers for AI AgentsIvan [00:04:58]: You're wearing the shirt. Yes,.Swyx [00:04:59]: It says, I think your branding is very good. Like, it's very consistent. It runs AI code. Like, it cannot be simpler.Ivan [00:05:05]: Exactly, but we're gonna probably have to change that.Swyx [00:05:07]: Oh, s**t.Ivan [00:05:07]: It's also a subset of what we do. Unfortunately, we really love this, Run AI Code is super simple. People interpret it different ways. I think we've given out 5,000, 6,000 of these shirts. People wear them with pride because it doesn't really market about us.Swyx [00:05:21]: Yeah, Daytona's on the back.Ivan [00:05:22]: It markets the back. It markets to the person itself, so I think we did a really good job on that one. But it is also a subset of what we do, because people, when they think about Run AI Code, they just think about these small, let's call it isolates, code execution boxes that, you send some code, you get an output. Whereas what Daytona is today is essentially composable computers for AI agents. It is, the market calls them sandboxes which can be misleading.Swyx [00:05:44]: All these things. All these things on.Ivan [00:05:45]: Yeah, exactly, ‘cause it can be misleading ‘cause people usually think about sandboxes as a demo or a test environment versus a production-grade environment. But what Daytona does, if you think of the laptop that you have in front of you or the computer that's over there, or, my wife is an architect, so she has like a Windows with a 3D graphics card inside to do 3D rendering. Like, as humans, we have different computers or different compositions of computers. And our belief is strongly that agents today and going forward will need all these different compositions of computers to do different types of tasks. And so we offer that basically through an API.Swyx [00:06:19]: Yeah, to give people - I'm trying to sort of front-load all the aha moments or the wow moments so that people can, stay engaged and click like and subscribe. the market is exploding, right? Like, you have been reporting 74% month-on-month growth, and it also, it's just been growing for a while. Like, it's been going like this. And every single - It's not just you guys. It's every single.Ivan [00:06:41]: Everyone, yeah.Swyx [00:06:42]: Sort of, compute provider. I don't know if you agree with me saying compute provider or not.Ivan [00:06:48]: It's fine.Swyx [00:06:48]: Yeah. So like organically PLG-driven growth, but also enterprise is doing super well, I think I wanna rewind to January of last year when you did the pivot. Like, so you obviously called this market early, and you were positioned for it, and you are now one of the market leaders. But what was the insight that made you do the pivot?The Pivot: From Human Dev Environments to Agent SandboxesIvan [00:07:06]: The insight that made us do this pivot is the quarter before that, so end of 2024, when we had - Basically, we did a demo with - I don't I think we discussed this as well, Devin was not public. You actually gave me access to Devin at that time. So Devin.Swyx [00:07:25]: I did?Ivan [00:07:26]: Yeah, you gave me access.Swyx [00:07:26]: I don't think I was supposed.Ivan [00:07:27]: Yeah, exactly.Swyx [00:07:28]: Yeah, I.Ivan [00:07:28]: So it doesn't matter. You.Swyx [00:07:29]: Yeah. I gave like three friends access.Ivan [00:07:31]: Yeah, or it was a call and you showed it to me. It doesn't matter. but OpenDevin was available, which is now called OpenHands. And so we're like, “Oh, this seems to be a thing. This is not public. Let's take our for human automation of dev environments and take, OpenDevin and launch that as a SaaS.” And we did that. Not very many people signed up and used it, but a lot of people reached out that were building agents, and they were like, “Hey, my agent needs a compute sandbox runtime,” whatever you wanna call it. I forgot what it was called at that point. And then we were like, “Oh, amazing. This is a new market. Here is our infrastructure. Here's our product, and go.” And what we found really fast, soon, was that people did not like what we had built. It didn't work. And I remember talking to people at the beginning when we're doing this, the sandbox we're building for agents. People were like, “Oh, why is it different? It's the same thing. We have like EC2, we have VMs, we have all these things.” But we saw that everyone we gave it to, it was like 20, 30 people, they all said, “No.” Like, “This is not what we need. This sort of breaks.” And basically, me and my co-founder not knowing a lot about - ‘cause we're infra people. We're not AI people. So I basically took it upon myself to like watch every single podcast that exists, including all of, all of these and all that, and sort of get up to date, read all the blogs, like get, understand what's going on.Swyx [00:08:45]: Do you wanna shout out who else was useful, just in case people are also looking.Ivan [00:08:49]: Generally we -, I looked at There's a few of podcast, different segments and different types. So there's you guys, No Priors, Bill Gurley's was great while.Swyx [00:09:04]: VG2, yeah.Ivan [00:09:05]: Yeah, while it was around. So there's a few. 20VC is interesting from a different dynamic, and some are different dynamic. But there was, also Red Points.Swyx [00:09:14]: We're not really about the compute market.Ivan [00:09:15]: It was also already - Sorry?Swyx [00:09:16]: You're, you want - You're looking at the agent infra market.Ivan [00:09:19]: I was looking at the agent market and the AI market in general and sort of understanding who are the players, what the perception, and how that goes. And like obviously you complement this with like going to conferences, going to events, going to meetups, reading white papers, like doing all the things that you have to do to understand what's happening. And so when we figured, when we sort of had an idea of what we had to build, literally over the New Year's Eve, literally on New Year's Eve, I half vibe coded the first MVP, first minimal viable product of what Daytona is today. And I went to sleep at like 3:00 AM or something like that. I was doing - I just put my like baby daughter and wife to sleep and, Happy New Year's, and go back to just, doing this. And I sent it to my co-founder, my CTO, and he saw it in the morning. He's like, “This is absolute garbage.” “Do not show this to anybody at all, but the idea is good.” And so he took two weeks, and he rebuilt it.Swyx [00:10:09]: Did it like look like that? Listen, I - It was rough idea.Ivan [00:10:12]: Oh, not even, not even close. Like it was it was way worse. But it was like a very - It was a simplistic view of what it should be. Like, it worked, but it was not ideal. And so he went, we went down the whole, which is his job as CTO, to go, and he came back with this version. We then called all the people that had said like, “This is garbage,” a quarter ago. And we set up these calls, and we gave it to - We just demoed it to everyone. And all the calls went long, every single one. They were 15-minute calls, and they all went to like 25, 30 minutes or whatnot. And everyone said, “We need, we want access.” There was no login, just an API key, ‘cause it was just a beta or an alpha. And they said, “Oh, we want access.” And we're like, “Sure, yeah. Okay, thank you very much.” But after like the next day, if we'd not send it, every single one, like every call that we did, everyone came back, “Where is my API key?” Like everyone wanted it. We're like, “S**t.” Like this is it. Like I've never felt So one, the understanding to your point was like most people thought it was the same infrastructure for humans and agents. We understood a quarter ago it's not. We just didn't know what was the right primitive. And then when we came, and we can talk about what that is, and we gave it to these people, I've never seen, I've never experienced - I've done multiple companies in my life. I've never experienced this, that people literally call you if you do not give them access. Like they want access right now. And so it's like, okay, they don't want this. the thing that they want doesn't seem to exist, or they have not found it, and they really want what we want. And then when we understood that we're onto something, and then when you think about the size of the market, like the market for human engineers and enterprise is a very large market, so think GitLab or whatnot. But the market for every single agent that will exist ever in the future is just like, what is that market? How big is that? And we're like, “We are all in on this.” And so that is where we made sort of the cut between the old product and the new one.Bare Metal, Stateful Sandboxes, and the Lambda + EC2 ModelSwyx [00:12:02]: Yeah. But it wasn't composable at the time?Ivan [00:12:05]: It was very - It was basically just a Linux box that you could change, that you could define number of CPUs, disk, and RAM. Like that is what you could do, but you couldn't have multiple operating systems, you couldn't resize it on the fly, you couldn't add a GPU, you couldn't do like all the things. It was just the, just the first sort of variation of that, yeah.Swyx [00:12:22]: Was it bare metal from the start?Ivan [00:12:24]: It was bare metal from the start. And so the interesting thing that we thought about right away, so our.Swyx [00:12:29]: Which, give people the background, what is the normal path?Ivan [00:12:32]: Yeah, so, basically most providers run this on top of VMs. And also.Swyx [00:12:37]: Firecracker.Ivan [00:12:38]: Yeah, they run on Firecracker and VM. And so we also fire - We can get - We have multiple isolation layers and we can do that. But the common way to do it is that they, one, that the state of the machine, or the hard disk is not part of the sandbox itself. And the other thing is they're not meant to last forever. So most of them are preemptible, like they can There's a time that they can live. And so our thought was when we were going into this is, agents will be like humans in the sense of you don't want your laptop to be shut down until you're done with work. Like, and you want to close the lid and open the lid, it's the same state. So you - Agents would want that, like the pause and come back. They want those two things. But also agents really want speed, right? Can they get it? So when we thought about it's like we need something insanely fast, how to make it fast, how to make it long-running, and stateful. And so those two things, it's like combining a Lambda and an EC2, right? Those two things together. And so we didn't have an idea how others did it, ‘cause we didn't know too that there was a market around this. It was more like, okay, this is what we need, what they need. And we looked at Kubernetes, it wasn't wasn't good enough for that. We looked at Nomad, it didn't enable that. And so our history in rewriting our own scheduler at CodeAnywhere is basically what my CTO came up with. Like, he's like, “Oh, the learnings from there,” and he brought it. And the funny thing is, our third co-founder, when he saw it, he's like, “Dude, what is this? This is like 2008.” Like, we went back in time, and he's like, “Exactly.” And so the reason why Daytona is like super fast, and you see this on benchmarks, is we essentially, we run on bare metal. We have our own scheduler, we use the underlying, disk, CPU, and RAM of the underlying machine, which means your IOPS are insanely fast because there's no, there's no network between an EBS or something like that. But also the snapshot, the point in time, the templates, are also preloaded on the bare metal machines. So when you fire off a sandbox from a template or a snapshot, you're essentially directed to the bare metal machine where that snapshot is based on that NVMe drive, and then it literally just turns on that machine, and it's local. There's no network latency, anything on there. And so that is sort of the specificities that we, when we're thinking from first principles, what a computer would look like for an agent, that is what we came up with, and that's what we created.Benchmarks, 60ms Startup, and 50,000 SandboxesSwyx [00:15:02]: Yeah. I should maybe, I don't know if you endorse this, but there's someone that does compute SDK, you guys do very well on there, with like the TTI, right? I. is this a, is this a is this a relevant benchmark for you guys? I don't know.Ivan [00:15:16]: I don't know, and it changes every day. So today RKL is.Swyx [00:15:18]: I don't know what RKL is. Never heard of it.Ivan [00:15:20]: Yeah. RK, yeah, so it is there.Swyx [00:15:22]: You are, at least a third of the next tier of performance, and then, there's a lot of other better-known names that are very slow to start.Ivan [00:15:31]: Yeah. We've been the number one by far for a long time, and now there's different, there's different definitions also of sandboxes, different isolation patterns, different other things. So RKL runs it literally on the S3, the data, so it's very different, and they spin up a sandbox, spin up a container for that, so it's a different type of thing. So the definition of a sandbox is something that we can all, we all need to get along with. But yeah, we're insanely fast on getting these things, up and running. And so you can see even there that it's a zero point 0.10 to 0.11, so.Swyx [00:16:03]: Close enough. Yeah. what else do you need, right?Ivan [00:16:05]: Yeah. So the benchmarks itself, so, in this, in I don't think the benchmarks equate to market ownership or revenue or anything like that. and I've seen this with multiple benchmarks, not just in sandboxes, but in general benchmarks around.Swyx [00:16:20]: It's table stakes. It's just like.Ivan [00:16:21]: Exactly. But it doesn't hurt.Swyx [00:16:22]: Just roughly check.Ivan [00:16:22]: Like you definitely have to be up there and you have to be competing so that people know that, oh, this is definitely one of the top. Because this is only one dimension of what customers look for. There's other things like how many can you spin up consecutively? There's a feature set, there's support, there's like all different things that people look at, but you definitely have to be there, on the benchmarks.Swyx [00:16:40]: How many people do people spin up consecutively?Ivan [00:16:43]: So we have.Swyx [00:16:43]: Or concurrently, is the Concurrency, right?Ivan [00:16:45]: There's three metrics that we look at. And so one is like time to spin up one, and so our time to spin up one is 60 milliseconds with network latency. So request, spin up, reply, 60, the whole thing, 60 milliseconds. That is one. But if you wanna spin up 50,000 at once, we are now at about 75 seconds. So it takes about 75 seconds to spin up concurrently 50,000. Some others, there's public data around this, like take 2,000 seconds, which is 30 minutes. Like there's different variations of that. And then there is the so it is speed of one, speed of like multiple, and then how many can you consistently have up and running. And so we basically have right now no limit to how much we can add because we basically own our own metal. But the biggest customer of ours does like about 850,000 every single day is sort of where they're, where they're just shy of a million every single day that they're running, we do have a request for half a million concurrent, which is literally half a million CPUs somewhere running. So that's an interesting.Swyx [00:17:44]: They pay by like vCPU seconds.Ivan [00:17:47]: By seconds, yeah.Swyx [00:17:47]: Or whatever. Yeah. Okay, and so and then, and the other thing is, the sleeping and the resuming, ‘cause it's all the stateful resumption of all these things, how, what kind of workload are people putting through this, right? Like how is it Do we measure by gigabytes in memory, gigabytes in storage? I don't In like network attached storage. I, what are the costly ones of, out of all these features?Workload Economics: CPU, RAM, Network, and StorageIvan [00:18:15]: The most expensive thing are CPU.Swyx [00:18:18]: Okay. Yeah, of course.Ivan [00:18:18]: The second one, yeah Then it's RAM, then it's disk. We actually don't charge.Swyx [00:18:22]: Which is snapshotting, right?Ivan [00:18:23]: No, it's actually the, snapshotting's part of it, but basically the size of your hard disk, of your machine. So do you have 10 gigabytes, do you have 20, do you have 50, do you have whatever? And then the transference of that. Right now, currently we don't charge for, network at all at Polychron.Swyx [00:18:37]: Oh, you gotta, yeah, you gotta fix.Ivan [00:18:38]: Yeah. It is very much a it's a larger and larger part of our bill, so we're working around, that part there. Obviously, that is the least, expensive, so the hard disk is the least expensive, so it's basically CPU, RAM, for us network, ‘cause we don't charge the customer, and then hard disk, is how it's split up. But there's also different types of workloads, so we basically split it up into two types of workloads in Daytona. One is what we call background agents or long-running agents. and the other is, basically RLs and evals, which I put sort of together. And so they have very different patterns of usage, and if you look at the usage of a background And I'll just name names of companies, not specifically.Background Agents vs. RL/Evals: Two Usage ShapesSwyx [00:19:21]: Yeah, open, all hands.Ivan [00:19:23]: Yeah. So like a background agent's a Cognition, a Lovable, a like all these things are Harvey. These are all long-running, background agents. And so if you look at their usage patterns, their usage patterns are similar to human, which is like follow the sun. Basically, the usage patterns of that is like noon is probably the highest, and the midnight is the lowest, and then weekends are lower. weekday is higher.Swyx [00:19:42]: Yeah, that's a fun question. How global is it? Is it very US-centric or?Ivan [00:19:46]: The US is a large part, but we have currently, we have Asia, Europe, and the US regions.Swyx [00:19:52]: So it's quite global.Ivan [00:19:53]: Yeah, it's quite global. We have it all over. It's interesting that our I talked to you a bit about this. Our number one city by user.Swyx [00:20:01]: Hmm.Ivan [00:20:02]: Is Singapore.Swyx [00:20:04]: Oh, wow. Amazing.Ivan [00:20:05]: Which is an interesting one, right? Not by revenue, just by just like by individual head count.Swyx [00:20:09]: Really?Ivan [00:20:09]: Just like an interesting thing.Swyx [00:20:10]: Singapore is, Singapore is weirdly high in the adoption charts of AI for the population. It's like an, seven, eight million population. And it's like keeps showing up.Ivan [00:20:20]: No, it's quite interesting. We were quite shocked, and I was like, “Oh, this is interesting.” And also one that's up there.Swyx [00:20:24]: There's a reason I'm doing AI using Singapore. it's because I'm from there.Ivan [00:20:27]: We're there. We're gonna, we're gonna be there as well. and it's interesting that Japan is in the top or like Tokyo's in the top, which is in all the tech cycles it has never been. It has never been, so it's quite interesting that they're.Swyx [00:20:39]: I think the Japanese just love AI. Yeah. It's that, and then it's Brazil. That's it.Ivan [00:20:44]: Brazil has always been in.Swyx [00:20:45]: I think.Ivan [00:20:46]: Even when I look, if you look at like GitHub's data and ask historically with CodeAnywhere, it was always like US, Western Europe, and then you'd have like India, Brazil, China, like that would be there. But like Singapore was not in, specifically Japan was never in sort of that top, that top.Swyx [00:21:01]: Yeah. Weird pockets.Ivan [00:21:01]: Weird. Yeah, so it's very global.Swyx [00:21:02]: Okay, so actually that, but that's helps you to distribute your load through, all time?Ivan [00:21:08]: The interesting thing is like we have those kind of loads, but if you look at the researcher loads, they're quite different. So what they are is like if you give them concurrency of 10,000 or 50,000 or 100,000 CPUs at ARMb, when they fire off a run, it's just 100%. And then it just runs, and then it stops. So it's very, the usage pattern is squares basically, right? And it's also not follow the sun, because people will fire it off at midnight before they go to sleep but then wake up and so it's very unpredictable, so you don't know where that is. So the shapes of the usage are quite different than we have had before. And also what's interesting is when it's sort of a follow the sun, even if you have a high growth company, you can sort of predict your usage patterns and have enough capacity for that, because it's sort of, it grows in a, in a way you can project. When you have companies doing sort of like evals and RL, they're super spiky. So they're gonna come in, it's like, “We're gonna use nothing, then can we have 100,000?” Right? And then go back down. And then 100,000, go back down. So it's very different, right? And.Swyx [00:22:09]: Do you want to lock them into commits so.Ivan [00:22:11]: Yeah, we do.Swyx [00:22:12]: Yeah, okay.Ivan [00:22:12]: We so we have to lock them into some sort of commits to have that capacity, because we have to have, basically we have to have the capacity for peak. Right? And so right now, Daytona's mean utilization is 15%, 1-5.Swyx [00:22:25]: Oh my God.Ivan [00:22:26]: So it's very low.Swyx [00:22:27]: Because it's very spiky.Ivan [00:22:27]: It's very spiky, but we get up to 90%. so we have these things. And so what we're, what we're looking at right now as a company is similar to Cloudflare where you can like geo move things around, but that works really well for basically the background agent where it's follow the sun. But this, it's not. Like it's a very different shape. Obviously with scale you figure these things out, but that's an interesting new problem that we have, as a compute provider in the agent space. And when we were doing the conference recently, and so we talked to like Nikita from Neon and.Swyx [00:22:57]: I should bring it up.Ivan [00:22:58]: Parag from Parallel and whatnot, everyone has the same problem. Whereas the usage is super spiky, and this is something that has not happened before, that you have these types of like it was always, it the amplitudes were not this high, right? So it's quite interesting use case and problem solve.Compute Conference and Spiky Agent InfrastructureSwyx [00:23:12]: Yeah, I don't know if we're gonna bring this up again, but let's just talk about the conference, you had like 1,000 something people at the Warriors game, at the Sorry, where is it? What's.Ivan [00:23:22]: Chase Center.Swyx [00:23:23]: Chase Center.Ivan [00:23:23]: Chase Center.Swyx [00:23:24]: I went. It was, it was very impressive. Obviously, you can, how to throw a conference, what did you learn? you put, you pulled together all these impressive names.Ivan [00:23:33]: What I.Swyx [00:23:34]: What were you looking for?Ivan [00:23:35]: My thesis behind the Compute Conference was let's bring together people that are building infrastructure for AI agents. Because when I think of what we're building, it is the agent is the primary user, what are the ergonomics and usage patterns of agents, and so we can do that. And what I found, this was a theory, it wasn't proven, is that we all have these problems, as I touched onto. And I was, as I was talking on stage, it was like we all have the same underlying infra problems, which is this spiky workloads, unpredictable workloads that we've never had before, in human, compute or human infrastructure. And it's, again, it's the same when I was talking to Parag or when I was talking.Swyx [00:24:20]: Lynn. Nikita.Ivan [00:24:21]: Lynn, Nikita. Lynn especially, I was talking to her the other day as well. Like the It is a very interesting type of problem to solve because I can touch on Cloudflare because there's a lot of like talk about that recently as to how they solve that, which is they have a bunch of geos, and basically, as users work in different places, and depending on your tier, they can move you around the geos. And so that how, that's how they get the higher utilization. But you can sort of predict these, and it's If it's something in You'll rarely get a spike that is 10 orders of magnitude. Like you'll get a like let's say one of your customers has some like an exponential curve. What is that to I'm using Cloudflare as an example. 10%, 20%, whatever it is. I don't, I don't have this data, I'm just assessing. It's surely not 10x, right? It's surely not something there. And so how do you go out and solve this problem? And we're all solving this in different ways. So we have.Swyx [00:25:11]: She also has the same thing.Ivan [00:25:12]: Yeah, I know specifically that like Neon had that issue as well. Like how are we solving these spiky loads and things like that ‘cause we talked about it. And so the interesting thing for me to actually internalize was, yes, everyone that's building for agents first is going through this, and we're all solving similar problems, which is quite.Swyx [00:25:28]: Let me let me double-click on this. Okay. So for example, Neon, I happen to know that they're very sort of S3 oriented, right? so they're just like fully bet on S3. And you get to benefit from S3's distribution and infrastructure. So I would imagine that Neon doesn't have to care, whereas Lynn maybe has to care a bit more because obviously she's doing GPU inference. And, for listeners, we did an episode with her, one and a half years ago. And you have to care. But like, right?Ivan [00:25:54]: Parag cares for sure, and Nikita.Swyx [00:25:58]: And Parag is C of, Parallel.Ivan [00:25:59]: Parallel, yeah.Swyx [00:26:00]: Former CTO of Twitter.Ivan [00:26:01]: Twitter, yeah.Swyx [00:26:02]: They are the search.Ivan [00:26:03]: Yeah, they're search, yeah.Swyx [00:26:03]: I You and I know but the listeners don't know.Ivan [00:26:08]: Yeah, we can put it down in the screen, and so ‘cause we, when we were talking.Swyx [00:26:11]: I'll put it up on the, on the screen.Ivan [00:26:12]: Yeah, right.Swyx [00:26:12]: People can look it up if they need.Ivan [00:26:14]: Look it up. And, yes, but they still have CPU and RAM, allocation that you have to have up and running. And so CPU and RAM, you have to allocate that and have that ready. And so there's basically two ways to do it. One is you either over-provision and you can handle the bursts, or two, you basically have, I don't know if this is a term, just-in-time compute, which is like as your load becomes, as your usage comes in, you can fire off requests for VMs or bare metals at other cloud providers and then get them up and running.Swyx [00:26:43]: This is if you go above 100%, right?Ivan [00:26:45]: Yeah, this is.Swyx [00:26:46]: Like your overflow.Ivan [00:26:46]: If your overflow, like spillage or whatever you do.Swyx [00:26:48]: You probably lose money on it, but it doesn't matter, right?Ivan [00:26:50]: It, not Well, you might, you might not That is a more cost-effective way to do it but it's a slower way to do it. Because basically what you have to do is you have to like queue your requests, spin up these just-in-time compute, get it all ready, provision it, and then get your workload there. And so if the time isn't important that much, that's fine, and you can do that. But if your customer, and especially for, let's say, the RL training runs, the reason why a lot of people come to us is because GPUs are more expensive than CPUs, right? So you want your GPU running at, what, 100% the entire time. And so when you're running runs on CPUs, when the when the CPU cycle is like down and spinning up the next one, you want that to be instantaneous so that your GPU doesn't go down, right? And if you then have to like go out and provision machines, you're essentially telling the GPU that it has to wait, and that's incurring our cost. So there's things that you have to try to solve for there.RL Workloads, Declarative Images, and Kubernetes ReplacementSwyx [00:27:43]: Yeah, let's talk about the different workload, right? You said that, what was it? A few months ago, you had zero RL workload and now it's 50%.Ivan [00:27:52]: It will be this one, 50%, yeah.Swyx [00:27:54]: Let's talk about how different it is, right? Like I imagine, for example, a lot less dynamic code generation of like arbitrary code. Like here, it's probably all the same code. You're just doing parallel runs or something, I don't know.Ivan [00:28:05]: Yeah. So you'll have multiple Depends on the like for each run, you'll have a snapshot. And they, for the most part, they actually do use our declarative image builder, which is like, “Oh, we, the agent wants these dependencies, these env vars.”Swyx [00:28:17]: These ones, yeah.Ivan [00:28:18]: Yeah, the declarative image builder, it.Swyx [00:28:20]: Which is a very modal like thing that they.Ivan [00:28:22]: Yeah. And so we build it on the fly and then we propagate that snapshot, and you can spin up as many sandboxes as you want against that snapshot. And then if you have to do changes, the model can, or like it could be also be automated. It's like, “Oh, now for the next run, we need to install these things or remove these things or whatever to get, a task done,” and then it goes off and runs that. So yes, that is something that it seems that they prefer. The number one reason I found, or should I say, let's take a step back. What we are competing against in that environment is essentially managed Kubernetes. So EKS, GKE, whatever. That is what the vast majority run on. And anyone that has tried Daytona versus GKE, EKS is like, “I'm never going back.” That has always been. There's a few reasons. One is the ergonomics. So if you have, if you're using Kubernetes to spin that up, you have to essentially manage the interface interactions with that. Daytona, although as a compute provider, it's more akin to a Twilio and Stripe from a consumption perspective than it is an AWS. Like you have an API, an SDK, it's quite like easy and seamless to get these things up and running, that's one. The other is the speed to which we spin up, which we mentioned earlier, which is much faster, and the scale to which we can go to. We haven't got into features, but an interesting feature is that it's very hard to OOM, or out of memory, our sandboxes, because we can dynamically on the fly.Swyx [00:29:48]: Resize.Ivan [00:29:49]: Resize, which is like impossible on almost any other thing. There are some technologies that enable you to do that, but it's like a very hard thing. And so we actually saw this when, the Terminal Revenge team is, brought us actually. So thank you, Alex and the team, that brought us into this whole space.Swyx [00:30:05]: It's just very rare that, a framework would just say, “Guys, just use Daytona.”Ivan [00:30:11]: Yeah, I think it says it somewhere. Yeah.Swyx [00:30:13]: Yeah. I was like, “What is this?”Ivan [00:30:15]: There's all, there's multiple there, but they also mention a few other places. and so Daytona specifically-We have, the, just jumping on themes here We, I don't know where it says Data Center.Swyx [00:30:27]: I, there.Ivan [00:30:27]: Doesn't matter.Swyx [00:30:28]: There's a very strong recommendation, which is, very unusual. Which is, it's.Ivan [00:30:33]: We do not pay them for this, just.Swyx [00:30:34]: I know, yeah. They just like you.Ivan [00:30:35]: Yeah, they like us. yeah, and also a thing, so, Data Center has multiple isolation sets underneath. The customer doesn't have to know what they are. But basically we have Docker, which is a container, that's hardened with Sysbox. So it's Docker's, isolation that is a security equivalent to a VM, but it's still a container. And that is the default, and they, especially in these training workloads, really like that as an interface to be able to use just a basic Docker container, and we enable Docker and Docker. Which for these RL runs, if you need to do a Docker compose or Kubernetes, you can spin up a K3S inside of these things, which unlocks a huge amount of workloads that you can do that you cannot do on other providers. So just on that part is much more interesting. And so we went that, through that. We showed them that we could do that, and they enjoyed that quite a bit. They being the general venture people.Swyx [00:31:28]: Those people, yeah.Ivan [00:31:29]: And Harbor people.Swyx [00:31:29]: Harbor people, do are they, are they a company yet?Ivan [00:31:33]: As far, I do not know.Customer Pull, Slack Connect, and the Computer Use BetSwyx [00:31:35]: Okay. All right. Yeah. It's like super obvious that like, there's a lot of excitement and success around these things, okay, so yeah, tell us more, right? Like, this is an exploding workload, Harbor adopted you, which helped speed things along. But what are you learning as this new workload comes online?Ivan [00:31:53]: There's a couple things that we learned, which we chat about in the beginning. We, and this has led our story, as we mentioned, we like talked to a lot of customers along the way, and we add more features and more tool sets as we talk to customers. And it's interesting that And I think it's that the ecosystem is so small and/or the models get smarter, where when we see one user come with a request, we know it goes on a roadmap if like three to five customers come with the same request in that week. It's like very bizarre. It happens so many times, which is.Swyx [00:32:27]: Because they're all friends.Ivan [00:32:28]: Sorry?Swyx [00:32:28]: They all, they're all friends. They're all in the same group chat.Ivan [00:32:30]: Yeah, probably, yeah. ‘Cause and they're like, “Oh, can you do this?” And I'm like, “Okay, this is interesting. We'll put it on a feature request.” And then the next one's like, “Oh, can you do this?” “Okay.” It's all the same, right? It's always the same. And so what we try to do, and I personally try to do, I try to be on as many call, quote-unquote “sales calls” I can. I'm in every Slack channel. We literally have about 1,000 Slack Connect channels, something like that. It's an interesting, there's so many interesting things you find out when you have all the Slack channels. You can also see where people, transfer between companies. You see leave Slack channel, enter Slack channel. It's an interesting thing. Also, just I digress, I feel that Slack Connect is literally LinkedIn what it should be. You have a list.Swyx [00:33:08]: LinkedIn charges you to, use your own connections, but Slack doesn't, right? Slack is like, do it for free. It's more lock-in. It's great.Ivan [00:33:15]: Yeah. It's amazing. Yeah. It's one of the reasons.Swyx [00:33:17]: You're gonna pay Slack for life.Ivan [00:33:18]: Exactly. You're there for life. So that's interesting. And so one of the things, the newer things we were talking about earlier is we made a big bet and put a lot of investment on computer use. that is not seen publicly the light of day. We haven't GA'd that yet, but we have.Swyx [00:33:32]: Is there a thing I can pull up?Ivan [00:33:33]: There is computer use there. It's right up a bit.Swyx [00:33:36]: Oh, yeah. Okay.Ivan [00:33:38]: What we have, what we talked about and what we've seen publicly is there's this theme now about, the human emulator where And Elon from XAI has talked about this publicly, and if you think about the models today, they're actually quite sophisticated and they can do a lot of work, but they still don't have access to all the tools. Like, I'm a strong believer that the most efficient way for an agent to work is essentially headless or through, terminal or whatnot. But if we, if we look at knowledge work in general, there's about 100 million knowledge workers in the US, about a billion in the world, and knowledge workers, and the salaries of them aggregate to 10 trillion in the US 50 trillion worldwide.Swyx [00:34:24]: Wow.Ivan [00:34:25]: Something like that. And if we look at, the five most important sectors of that, so like healthcare and government and financial services and whatnot, that's about 56% of that. So let's say it's about half of that. So in the US it's about 25 trillion, and most of them, most of that work is actually still locked into legacy apps inside of Windows, which is not going anywhere for a very long time. Like, people just won't invest in that. How much of it? our assumption is the following: if, in the RPA market, which is similar market, well, not the same 25% of, these white collar, workers', work is automated. If an agent is more sophisticated, can go through more runs, figure stuff out, let's say it's, 40%, right? And so if you take 40% of that, you get to essentially, $10 trillion a year.Swyx [00:35:17]: That's a TAM.Ivan [00:35:18]: That is a that is a TAM. So that's the TAM of the models, right? That's not our, essentially ours. But you get to that size, and to be able to do that, you essentially have to give agents these computers with the legacy. So computer use, either Mac or Windows or Linux. Linux we also obviously have and others have. But Windows specifically is something very new, and the only option right now is an EC2 with, Windows or on Azure. Both of them take anywhere from three to five minutes to spin up. We've created an actual sandbox, so it's a second instead of milliseconds, but you have, point in time snapshots, you have, forking, you have all the things that you have from a sandbox, but essentially enables you to hopefully unlock all this value. And so that's been our big push and bet, but we've sort of, kept our ear to the ground. What is sort of the next things in the market?RPA Returns: Why Agents Still Need ComputersSwyx [00:36:06]: Yeah, knowledge work, and building, and sort of RPA, the next wave of RPA. I got very excited about RPA kind of during COVID times. The UI path was IPO-ing. And it was, a very hot Isn't it, Eastern European?Ivan [00:36:20]: It is, Romanian.Swyx [00:36:21]: Romanian?Yeah, it might be the only Romanian, big unicorn okay, yeah. This I don't I don't, I don't have like a I think there's, I think there's a stage being set for the resurgence of RPA, ‘cause everyone understands that, yeah, no one wants to deal with these shitty apps and no one's gonna rewrite them. Like, you just have to do, a remote operation and programmatic operation of them.Ivan [00:36:45]: If you wanna unlock it, my own setup was basically the following. So I was doing a board deck recently, last month, whatever, and I'm like, “Okay, let's just, let's just do automated.” So, all our data's in, ClickHouse and PostHog and QuickBooks, where everyone else's is, and I'm basically, connected that all to, my Cloud code, like go off and go Cloud code whatever. Go off and, here's the integrations, go do that. It pulled out the first report, which was great. It connected to Brex and all these things, pulled it, which was great, and then I say, “Okay, now pull out this, and this,” and I kept getting, really well McKinsey-style design reports, but the data said partial data. all the missing data, partial data. Like, it can't access all the things, and I got so frustrated, and so I got, I got, my Mac Mini virtual sandbox with OpenClaw. I gave it its own account in our company, and then I went to all these services and created a read-only account, so literally like an intern in your company. And so I would say, “Now go and do this report,” and it would get the same, or like, “I can't via the MCP or the API or whatever. I can't get all the information.” I'm like, “Go log in.” And it will log into the website, then go in, export the data. It'll export the data and do the thing end to end. So even for things that have today APIs, not all of it is exposed, and I to get value, I get immense value right now, but it has to be a computer usage, unfortunately, and so I spend a bunch of tokens just on that, but I get the job done. And so if even a startup like ours, and using all the hottest tools, still needs a computer agent what hope does, Goldman have to have a headless, right?Swyx [00:38:22]: Yeah, what a - Why isn't Microsoft doing this?Ivan [00:38:27]: I'm pretty sure, Satya had a post yesterday.Swyx [00:38:29]: Oh, okay. I see.Ivan [00:38:29]: Which was like, “Every agent needs a computer.”Swyx [00:38:31]: I see, I see.Ivan [00:38:32]: So they have launched something recently.Swyx [00:38:34]: Yeah, they have Microsoft Power Automate, I'm sure, I'm sure, they're gonna have their version.macOS Sandboxes, Apple Constraints, and the Windows OpportunityIvan [00:38:39]: Version of that, yeah.Swyx [00:38:39]: You're gonna try to do yours, and it - I always know there's always demand for Mac, but I know it's, tricky to host, macOS sandboxes.Ivan [00:38:49]: We will have macOS sandboxes fairly soon. The problem with macOS, OS sandboxes is, I'm deep in this, I don't know how much interesting is.Swyx [00:38:55]: No, it's.Ivan [00:38:56]: MacOS has this problem.Swyx [00:38:57]: It's a licensing thing, right?Ivan [00:38:58]: Licensing thing. So one, you're allowed to run only two parallel VMs per machine, so that's one. Two, you can only license to a different user every 24 hours. So if you come in and theoretically, if I wanna charge you per second and I charge you one second, I have to have it idle for the rest of the day. I can't have anyone else doing that. So the pricing will be different in the sense that I will have to - we would have to charge for 24 hours, and that's not even, that's not even the most difficult thing. But the, thing above that is, from a security perspective, they enable you to do memory snapshot, pause, resume, but only on the same physical drive, physical machine. And so what you can do in, Windows world or Linux world is that I can move in the background, your snapshot from one to the other and manage load, right? Here, if you wanna do that, you essentially have to have your.Swyx [00:39:49]: Yeah, snapshots. Yeah.Ivan [00:39:50]: Your.Swyx [00:39:51]: It's like.Ivan [00:39:51]: Physical machine.Swyx [00:39:52]: You can't break it up.Ivan [00:39:53]: You can't, you can't move things around that, and all of that is, that part is, from a security standpoint, if it is written. Like, I understand the security aspect of that, but it disables you from doing these agentic, like really scalable agentic workloads.Swyx [00:40:08]: You need to do a vibe-coded, clean room implementation on macOS that you can then - That's like Clean OS or something. I don't know.Ivan [00:40:17]: So. We have.Swyx [00:40:18]: ‘cause like Linux was originally like a clean room rewrite of Unix.Ivan [00:40:21]: Okay. Yeah.Swyx [00:40:21]: Or something like that, right? Like same thing to macOS. Someone needs to do it.Ivan [00:40:25]: Someone will do that, and someone will have some long-running agents for a few days to figure this stuff out. But yeah. So definitely we - we're really close to offering something ‘cause people do want it, but the pricing will be different, and the feature set will be sort of stringent.Swyx [00:40:38]: Yeah, nobody's gonna use this. like, the labs, the labs will because they want to automate macOS.Ivan [00:40:42]: They have to do RL. They have to do RL again. But even if you The - So the point is with the RL part, if you, if you do RL on macOS, then the next iteration of the model comes out, it will be able to use these tools significantly. Then you actually need to run those, that somewhere. So you're gonna have to have that, later on. And from, if anyone at Apple is listening, I very much feel that they are shooting themselves in the foot of the scale of the revenue of compute or licensing they could get if they would just enable a concurrency model similar to what you can get on a Windows and a, and Linux.Swyx [00:41:17]: Yeah. Yeah. And I'm sure they've heard this before. They just don't care. Yeah, it's And maybe they will change their mind with the new CEO.Ivan [00:41:24]: Yeah. We'll see.Swyx [00:41:25]: We'll see.Ivan [00:41:25]: High hopes.Swyx [00:41:26]: High hopes.Ivan [00:41:26]: High hopes.Swyx [00:41:27]: Okay. But I, it's very clear the market opportunity is huge in Windows, and you can go for a long time on just Windows, but your customers are gonna want both. and I think, it is interesting to me that, this is the sort of God application of agents, right? Like, I don't It was - How big was OpenClaw for you guys? Like, was it, was there, a significant bump.OpenClaw, Agent Labs, and the B2B2C Sandbox MarketIvan [00:41:54]: Not for us because we.Swyx [00:41:54]: Because you already.Ivan [00:41:55]: We're kind of positioned differently. Whereas although it's completely PLG and we have individual developers that use it, most of the users that use Daytona are sort of a B2B2C. Sort of it's either B2B or B2B2C. So, in the researcher world, it's B2B, so you're selling to, labs and neo labs and things like that. But on the long-running agents, it's mostly, from a scale revenue perspective, it's mostly B2B2C, where you have a app layer agent that uses you at a big scale.Swyx [00:42:26]: Like a Manus. Yeah.Ivan [00:42:28]: Like a Manus Lovable type of thing.Swyx [00:42:31]: Yeah. I think that's the question of, well how, um-Uh, yeah, B2B to C is basically to me what I've been calling an agent lab, which is kind of like you're not in a model lab, but you're making a very good wrapper that is a platform that other people can sign up so they don't have to code those things. Yeah, it sound, it sounds like a much better market than the direct OpenClaw market.Ivan [00:42:56]: I've like - We I've done multiple things. So the CodeAnywhere's part of our career path R in the calendar, was very much an end user developer product. And so that is great. It You can get a lot of developer love, and I feel that we do as a company have a bunch of developer love. But it's a different type, where it's people building these things. Again, it's more akin to a Twilio because you don't really run - As a person, you wouldn't run Twilio. I don't know how many people remember. It was like ask your developer billboard and whatnot. And people really love Twilio, but they only used it inside of like, “Oh, I'm building this app or service for thing.” And so we're very much directly to that. And you also know that I used to work for a competitor for Twilio, so it's kind of ingrained, in my DNA.Swyx [00:43:35]: People don't know InfoBip is that big.Ivan [00:43:38]: Yeah, it's.Swyx [00:43:39]: Because.Ivan [00:43:40]: It's a billion euro.Swyx [00:43:40]: They're all American. They're like, “Whatever's in Europe doesn't matter to me.” But like it's the, it's the same size or bigger? Same size?Ivan [00:43:46]: It's about half the size.Swyx [00:43:47]: Half the size?Ivan [00:43:48]: Yeah, about half the size.Swyx [00:43:48]: It's like, yeah.Ivan [00:43:48]: Still huge. Multiple billions a year. Yes.Swyx [00:43:51]: That's crazy.Ivan [00:43:51]: Exactly, and so that - These are like really interesting and large revenue-generating, very sticky businesses. Whereas when you're selling to the - When your focus is the end developer, it is a very hard sell because they're very price sensitive, very price conscious, very around that. And there's very It's very hard to scale. Your cap is the number of people that are willing to spin up - First of all, wanna spin that up, and then spin up multiple of these. Whereas if you're in the enterprise one, like we know everyone's talking about like how many tokens they're spending, I'm spending. Like a lot of companies today are like, “If this is our company, spend as much as you can.” Like basically that is where we're going. And so if you think about that paradigm, where you're selling to companies that say, “Spend as much as you can to generate, productivity,” versus, “Oh, I'm a single person. I have this much budget, and I'm doing this thing because it's fun or it's helping me out or whatever.” Like it is a different, it's a different go-to-market, I think, strategy.MCP, CLIs, and Sandboxes as the Agent RuntimeSwyx [00:44:50]: Yeah, there's a lot of discussion. I'm just kind of going through like the mental list of things that are in your favor, which is, for example, MCP versus CLI. Like obviously you want CLI. It's been very good for you. I feel like it's maybe a drop in the bucket or maybe it's huge. I'm just checking whether it's like these are big trends.Ivan [00:45:10]: Those things you - work well in our favor, to your point just because every.Swyx [00:45:13]: They're kind of drop in the bucket, right?Ivan [00:45:15]: I think it's like sort of all the things come together. And so there's so many things that impact that. To your point, like OpenClaw wasn't huge for us, but like having the agent SDK, from Anthropic, so or Cloud Claude Code was very interesting. The reason why it was interesting is that a lot of, let's call them app I don't know what to call them, app layer agent companies, essentially they are like, “Oh, I can create this new app, this new agent. All I need, I just use Claude Code, and I throw it into a sandbox, and then I have my interface to the human to that.” And so that enabled so many more companies to actually offer this, and then they would pull on sandbox. So that was, that was interesting. And to your point, like MCP, versus the CLI, the MCP is an interface against an API, whereas the CLI is like you can actually go do things. Like this is it. The difference between integrations and actually running scripts or data or analysis against a thing. So being able to use a CLI very well enables the agent to do more things, and it's because that people will invoke a sandbox, they'll run it in the CLI, and but it'll do anal-analysis on that data and then give you an actual result versus just, pulling data from an API source.Swyx [00:46:29]: Yeah, it's a layer of indirection basically, it's the same thing as agentic search versus RAG, which where you're.Ivan [00:46:34]: Exactly, yeah.Swyx [00:46:34]: Just like you just win whenever people put more agents into their workflow. And so like it doesn't really matter, but I'm just kinda teasing out like what else have people heard about that like it's sort of, “Oh yeah, this is another sandbox use case. Oh yeah, that's another one.” Am I, am I missing any big ones?Ivan [00:46:51]: The thing, the thing that people, which is the computer use stuff, which I think is probably the most interesting one, is, and to your point, we've talked to so many people over the last year. It's like, “Oh, like why do you need a sandbox? Why do you need this? Why this?” And to your point, it's like, “Oh, I need sandbox for this. I need sandbox for that. I need sandbox-” It's like, “Oh, I need it for every single thing.” And so basically what I, what I - and it sounds like a broken record, it's like you use a laptop every single day, right? And you are n of one. It's just you. But now imagine how And by the way, the laptop, the computer PC market, the PC market is about equal to the cloud market in total. So it's about 150, 180 billion a year. Something like that. It's about roughly the three cloud hyperscalers is about equal to like Apple, HP, Lenovo, whatever, It's a little bit less, but it's sort of like that. And now imagine And that's just like, so how big is the addressable market? What, how many people are there in the world now? What's the last data?Swyx [00:47:45]: Let's call it eight billion.Ivan [00:47:46]: Eight billion. And so let's say you can have two computer, like you have one personal and one business, whatever. Like so it's double that, right? and so that's 16 billion, right? How many agents are gonna be running in two years, in 10 years, in 100 years? Like And for every single task, they will need one of these. And so how big is that? That market is essentially quote unquote “infinite”. You will get to the point, and Dylan Patel was at the conference talking about, from SemiAnalysis, that talks usually about GPUs, was also talking about how CPUs will now be a bottleneck because it will be the constraint. You won't be able to grow, or we won't be able to have enough of these because there won't be enough CPUs to basically do.Swyx [00:48:23]: Yeah. Well, I actually had a really good podcast with Doug Oliphant, who, which was his president at SemiAnalysis, where they've basically been like, yeah, it's been a GPU shortage first, but then it's cascaded down to memory and now to CPUs.Ivan [00:48:35]: CPU, yeah.Swyx [00:48:35]: It-What's next? So networking. So, networking actually has been in shortage for a while if you're looking at, just GPU networking. But, yeah, it's really crazy the amount of computer use that's going on, yeah, cool. I, other questions are, just the one very big part is the open sourceness which you didn't have to do, your competitors don't do, like it's not, a lot of people are worried about keeping their projects open source because some competitor can just slot fork it. I don't know if there's any reflections on just being an open source company.Open Source, Trust, and Enterprise ProcurementIvan [00:49:15]: Yeah. There's a bunch. So we the original product that we did was open source.Swyx [00:49:19]: Yeah. CodeAnywhere.Ivan [00:49:20]: So doing that was actually very good for us. There's basically a saying of, What's the saying? Like, companies that are, that are doing really well, measure themselves against, free cashflow, that are kinda okay, it's EBITDA, then, it's, it goes all the way down.Swyx [00:49:36]: The worst is like GitHub stars.Ivan [00:49:37]: GitHub stars. GitHub stars are the worst, yeah. So you go all the way down to GitHub stars. And so our original one was GitHub stars. That's what we talked about, we're at the point we're talking about revenue, so we're we've gone up the stack on that. And so we started.Swyx [00:49:47]: No, profit.Ivan [00:49:48]: Yeah. We haven't, we're, we'll get there. We'll get there. But basically at that point we did stars and GitHub and it was useful, and the original variation that we did, it we split the core into its own repo and it was Apache 2.0, so very, permissive. And then we basically would bundl

Modernizing SQL Server for the cloud doesn't have to be complex. In this episode, we break down what Azure SQL Managed Instance is and show how the upgraded Next‑gen General Purpose tier delivers faster performance, higher storage, and easier scaling using Azure's latest storage technology. You'll also see a quick Azure Portal demo with the new IOPS slider and in‑place performance scaling. Chapters 00:00 - Introduction 00:38 - Overview of Azure SQL & SQL Managed Instance 03:30 - Service tiers in Azure SQL Managed Instance 04:14 - Storage architecture upgrade (Elastic SAN, performance gains) 04:48 - Why Next‑gen General Purpose? Azure Portal demo 07:36 - In-place IOPS scaling demo 12:33 - Summary and wrap-up Recommended resources Learn Docs Azure Product page Connect Scott Hanselman | Twitter/X: @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Modernizing SQL Server for the cloud doesn't have to be complex. In this episode, we break down what Azure SQL Managed Instance is and show how the upgraded Next‑gen General Purpose tier delivers faster performance, higher storage, and easier scaling using Azure's latest storage technology. You'll also see a quick Azure Portal demo with the new IOPS slider and in‑place performance scaling. Chapters 00:00 - Introduction 00:38 - Overview of Azure SQL & SQL Managed Instance 03:30 - Service tiers in Azure SQL Managed Instance 04:14 - Storage architecture upgrade (Elastic SAN, performance gains) 04:48 - Why Next‑gen General Purpose? Azure Portal demo 07:36 - In-place IOPS scaling demo 12:33 - Summary and wrap-up Recommended resources Learn Docs Azure Product page Connect Scott Hanselman | Twitter/X: @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Running Oracle Database@AWS is most effective when you have full visibility and control over your environment.   In this episode, hosts Lois Houston and Nikita Abraham are joined by Rashmi Panda, who explains how to monitor performance, track key metrics, and catch issues before they become problems. Later, Samvit Mishra shares key best practices for securing, optimizing, and maintaining a resilient Oracle Database@AWS deployment.   Oracle Database@AWS Architect Professional: https://mylearn.oracle.com/ou/course/oracle-databaseaws-architect-professional/155574 Oracle University Learning Community: https://education.oracle.com/ou-community LinkedIn: https://www.linkedin.com/showcase/oracle-university/ X: https://x.com/Oracle_Edu   Special thanks to Arijit Ghosh, Anna Hulkower, Kris-Ann Nansen, Radhika Banka, and the OU Studio Team for helping us create this episode. ------------------------------------------------------ Episode Transcript: 00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:26 Nikita: Welcome to the Oracle University Podcast! I'm Nikita Abraham, Team Lead: Editorial Services with Oracle University, and with me is Lois Houston, Director of Communications and Adoption with Customer Success Services  Lois: Hello again! Last week's discussion was all about how Oracle Database@AWS stays secure and available. Today, we're joined by two experts from Oracle University. First, we'll hear from Rashmi Panda, Senior Principal Database Instructor, who will tell you how to monitor and log Oracle Database@AWS so your environment stays healthy and reliable. Nikita: And then we're bringing in Samvit Mishra, Senior Manager, CSS OU Cloud Delivery, who will break down the best practices that help you secure and strengthen your Oracle Database@AWS deployment. Let's start with you, Rashmi. Is there a service that allows you to monitor the different AWS resources in real time? Rashmi: Amazon CloudWatch is the cloud-native AWS monitoring service that can monitor the different AWS resources in real time. It allows you to collect the resource metrics and create customized dashboards, and even take action when certain criteria is met. Integration of Oracle Database@AWS with Amazon CloudWatch enables monitoring the metrics of the different database resources that are provisioned in Oracle Database@AWS. Amazon CloudWatch collects raw data and processes it to produce near real-time metrics data. Metrics collected for the resources are retained for 15 months. This facilitates analyzing the historical data to understand and compare the performance, trends, and utilization of the database service resources at different time intervals. You can set up alarms that continuously monitor the resource metrics for breach of user-defined thresholds and configure alert notification or take automated action in response to that metric threshold being reached. 02:19 Lois: What monitoring features stand out the most in Amazon CloudWatch? Rashmi: With Amazon CloudWatch, you can monitor Exadata VM Cluster, container database, and Autonomous database resources in Oracle Database@AWS. Oracle Database@AWS reports metrics data specific to the resource in AWS/ODB namespace of Amazon CloudWatch. Metrics can be collected only when the database resource is an available state in Oracle Database@AWS. Each of the resource types have their own metrics defined in AWS/ODB namespace, for which the metrics data get collected.  02:54 Nikita: Rashmi, can you take us through a few metrics? Rashmi: At Exadata database VM Cluster, there is CPU utilization, memory utilization, swap space storage file system utilization metric. Then there is load average on the server, what is the node status, and the number of allocated CPUs, et cetera. Then for container database, there is CPU utilization, storage utilization, block changes, parse count, execute count, user calls, which are important elements that can provide metrics data on database load. And for Autonomous Database metrics data include DB time, CPU utilization, logins, IOPS and IO throughput, RedoSize, parse, execute, transaction count, and few others. 03:32 Nikita: Once you've collected these metrics and analyzed database performance, what tools or services can you use to automate responses or handle specific events in your Oracle Database@AWS environment? Rashmi: Then there is Amazon EventBridge, which can monitor events from AWS services and respond automatically with certain actions that may be defined. You can monitor events from Oracle Database@AWS in EventBridge, which sends events data continuously to EventBridge at real time. Eventbridge forwards these events data to target AWS Lambda and Amazon Simple Notification Service to perform any actions on occurrence of certain events. Oracle Database@AWS events are structured messages that indicate changes in the life cycle of the database service resource. Eventbridge can filter events based on your defined rules, process them, and deliver to one or more targets. Event Bus is the router that receives the events, optionally transform them, and then delivers the events to the targets. Events from Oracle Database@AWS can be generated by two means: they can be generated from Oracle Database@AWS in AWS, and they can also be generated directly from OCI and received by EventBridge in AWS. You can monitor Exadata Database and Autonomous Database resource events. Ensure that the Exadata infrastructure status is an available state. You can configure how the events are handled for these resources. You can define rules in EventBridge to filter the events of interest and the target, who is going to receive and process those events. You can filter events based on a pattern depending on the event type, and apply this pattern using Amazon EventBridge put-rule API, with the default event bus to route only those matching events to targets. 05:13 Lois: And what about events that AWS itself generates? Rashmi: Events that are generated in AWS for the Oracle Database@AWS resources are delivered to the default event bus of your AWS account. These events that are generated in AWS for Oracle Database@AWS resources include lifecycle changes of the ODB network. The different network events are successful creation or failure of the creation of the ODB network, and successful deletion or failure in deletion of the ODB network. When you subscribe to Oracle Database@AWS, then an event bus with prefix aws.partner/odb is created in your AWS account. All events generated in OCI for the Oracle Database@AWS resources are then received in this event bus. When you are creating filter pattern using Amazon EventBridge put-rule API, you must set the event bus name to this event bus. Make sure you do not delete this event bus. Events generated in OCI and received into event bus are extensive. They include events of Oracle Exadata infrastructure, VM Cluster, container, and pluggable databases. 06:14 Lois: If you want to look back at what's happened in your environment, like who made the changes or accessed resources, what's the best AWS service for logging and auditing all that activity? Rashmi: Amazon CloudTrail is a logging service in AWS that records the different actions taken by a user or roles, or an AWS service. Oracle Database@AWS is integrated with Amazon Cloud Trail. This enables logging of all the different events on Oracle Database@AWS resources.  Amazon Cloud Trail captures all the API calls to Oracle Database@AWS as events. These API calls include calls from the Oracle Database@AWS console, and code calls to Oracle Database@AWS API operations. These log files are delivered to Amazon S3 bucket that you specify. These logs determine the identity of the caller who made the call request to Oracle Database@AWS, their IP from which the call originated, the time of the call, and some additional details.  CloudTrail event history stores immutable record of the past 90 days of management events in an AWS region. You can view, search, and download these records from CloudTrail Event History. You can access CloudTrail when you create an AWS account that automatically gives you the access to CloudTrail. Event history. If you would like to retain the logs for a longer period of time beyond 90 days, you can create CloudTrail trails or CloudTrail Lake event data store.  Management events in AWS provide information about management operations that are performed on the resources in your AWS account. Management operations are also called control plane operations. Thus, the control plane operations in Oracle Database@AWS are logged as management events in CloudTrail logs.  07:59 Are you a MyLearn subscriber? If so, you're automatically a member of the Oracle University Learning Community! Join millions of learners, attend exclusive live events, and connect directly with Oracle subject matter experts. Enjoy the latest news, join challenges, and share your ideas. Don't miss out! Become an active member today by visiting mylearn.oracle.com. 08:25 Nikita: Welcome back! Samvit, let's talk best practices. What should teams keep in mind when they're setting up and securing their Oracle Database@AWS environment?  Samvit: Use IAM roles and policies with least privilege to manage Oracle Database@AWS resources. This ensures only authorized users can provision or modify DB resources, reducing the risk of accidental or malicious changes.  Oracle Data Safe monitors database activity, user risk, and sensitive data, while AWS CloudTrail records all AWS API calls. Together, they give full visibility across the database and cloud layers. Autonomous Database supports Oracle Database Vault for enforcing separation of duties. Exadata Database Service can integrate with Audit Vault and Database Firewall to prevent privileged users from bypassing security controls. Enable multifactor authentication for AWS IAM users managing Oracle Database@AWS. This adds a strong second layer of protection against stolen credentials.  Always deploy your Oracle Database@AWS in private subnets without public IPs. Use AWS security groups and NACLs to strictly limit inbound and outbound traffic, allowing access only from trusted applications. Exadata Database Service supports integration with Oracle Vault for key lifecycle management. And in case of Autonomous Database, the transparent data encryption keys are automatically managed. But you can bring your own keys with OCI Vault. Key rotation ensures compliance and reduces risk of key compromise. Oracle Database@AWS enforces encrypted connections by default. Ensure clients connect with TLS 1.2 or 1.3 to protect data in transit from interception or tampering.  Use Oracle Data Safe's user assessment features to detect dormant users or excessive privileges. Disable unused accounts and rightsize permissions to reduce insider threats and security gap. Export database audit logs to Oracle Data Safe Audit Vault or AWS S3 with object lock for immutability. This prevents lock tampering and ensures audit evidence is preserved for compliance.  11:25 Lois: OK, that covers security. Do you have any tips for making sure your Oracle Database@AWS setup is reliable and resilient? Samvit: Start with clear recovery objectives. Define how much downtime and data loss each workload can tolerate. These targets drive your HADR architecture and backup strategy.  Implement business continuity measures to deliver maximum uptime for your databases. As a best practice, you must configure disaster recovery environment for your critical databases so that, in the event of any disaster affecting the primary database, applications can be immediately failed over to the DR environment, ensuring least application downtime and zero or minimal data loss. With Oracle Database@AWS, you can automate the creation and management of DR environment for your database services using different deployment capabilities. You can opt to configure either cross-availability zone DR in the same region or configure cross-region DR. Since cross-availability zone can only provide site failure protection, you must also configure a cross-region DR to protect against regional failure. A DR plan is only effective if tested. Regular failover and switchover drills validate that people, processes, and systems can recover as designed.  For Exadata Database, Autonomous Recovery Service provides automated backup validation, recovery guarantees, and protection against accidental data loss or corruption.  Oracle-managed backups are fully managed by OCI. When you create your Oracle Exadata Database, you can enable automatic backups by choosing Enable Automatic Backups in the OCI Console. When you do that, you can select Amazon S3 or OCI Object Storage or Autonomous Recovery Service as the backup destination. Don't just take backups. You also need to test them. Regularly restore backups into non-production environment to validate integrity and recovery time.  Plan beyond just the database. Map application and middleware dependencies to ensure end-to-end business resilience. A database failover is useless if dependent apps can't reconnect. 14:09 Nikita: Another area of interest is performance and cost. What practices help teams balance the two? Samvit: Autonomous Database automatically scales CPU and storage as workloads grow. This ensures performance during peaks while avoiding overprovisioning. So you should enable ADB auto-scaling.  Monitor CPU, memory, and IO metrics with AWS CloudWatch to rightsize your compute. Scale up or down based on actual utilization instead of static provisioning. Autonomous databases continuously evaluate and creates indexes automatically. This improves query performance without requiring manual tuning.  Use connection pooling in your applications to optimize database connections. Minimizing round-trip reduces latency and improves throughput. Apply AWS tags to database and related resources for cost allocation and chargeback. Tagging also helps with governance and cost visibility.  Choose between bring your own license and license-included models for Oracle Database@AWS. The right model depends on your existing license portfolio and cost strategy. Not all workloads need long backup retention. Adjust retention policies based on business needs to balance compliance with storage costs.  Exadata Database supports Oracle multitenant with pluggable databases. Consolidating databases reduces infrastructure footprint and licensing costs. Performance tuning isn't just technical. Align metrics with business KPIs. correlating DB performance to user experience and revenue impact helps prioritize optimizations.  16:20 Lois: Before we wrap up, Samvit, let's look at operational efficiency. What advice do you have for making day-to-day operations more efficient? Samvit: Use infrastructure as code tools like Terraform or AWS CloudFormation to automate provisioning. This ensures consistent, repeatable deployments with minimal manual errors.  For Autonomous Database, enable auto-start/stop to optimize costs by running databases only when needed. This is ideal for dev test or seasonal workloads. Exadata Database Service provides fleet maintenance to patch multiple systems consistently. This reduces downtime and simplifies lifecycle management.  Integrate AWS CloudWatch for performance monitoring and EventBridge for event-driven automation. This helps detect issues early and trigger automated workflows. Oracle Data Safe provides ready-to-use audit and compliance reports. Use these to streamline governance and reduce the effort of manual compliance tracking.  For Autonomous databases, Performance Hub simplifies monitoring while Exadata users benefit from AWR and ASH reports. Together, they give deep insights into performance trends. Automated tagging policies and change management workflows help maintain governance. They ensure resources are tracked properly and changes are auditable.  Monitor storage consumption and growth patterns using AWS CloudWatch and the ADB Console. Proactive tracking helps avoid capacity issues and unexpected costs. Send CloudTrail logs into EventBridge to trigger automated incident responses. This shortens response time and builds operational resilience.  18:36 Nikita: Samvit and Rashmi, thanks for spending time with us today. Your insights always help bring the bigger picture into focus. Lois: They definitely do. And if you'd like to go deeper into everything we covered, head over to mylearn.oracle.com and look up the Oracle Database@AWS Architect Professional course. Until next time, this is Lois Houston… Nikita: And Nikita Abraham, signing off! 19:03 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

https://eveningiop.comDiscover how evening Intensive Outpatient Programs offer flexible, effective addiction treatment for busy professionals, students, and caregivers. Learn why virtual therapy works, how telehealth eliminates barriers, and what makes evening IOPs a practical solution for recovery without disrupting your daily life. Addiction Resource Center LLC. City: Yuba City Address: 1002 Live Oak Blvd. Website: https://sayarc.com

Discover how telehealth intensive outpatient programs are breaking down barriers to addiction recovery. Learn why remote care works just as well as in-person treatment and how working professionals, students, and caregivers can access structured support without sacrificing their daily responsibilities. Learn more at https://eveningiop.com Addiction Resource Center LLC. City: Yuba City Address: 1002 Live Oak Blvd. Website: https://sayarc.com

There was a time when I knew a lot about the various storage technologies available for a database. It was important when designing a server around the various requirements for size and performance balanced against the limitations of hardware. The rapid growth of solid state storage and the adoption of storage area networks have changed the game for many of us. We no longer care or think about storage. It's just a service that we consume in our databases, and while we might demand more IOPS capacity, we often don't worry too much about how that's provided to our systems. Read the rest of Storage Enhancements

In this episode, I chat with Richard Crowley from PlanetScale about their new offering: PlanetScale Metal.We dive deep into the performance and reliability trade-offs of EBS vs. locally attached NVMe storage,and how Metal delivers game-changing speed for MySQL workloads.Links:Database School: https://databaseschool.comPlanetScale: https://planetscale.comPlanetScale Metal: https://planetscale.com/blog/announcing-metalFollow Richard:Twitter: https://twitter.com/rcrowleyWebsite: https://rcrowley.orgFollow Aaron:Twitter: https://twitter.com/aarondfrancisLinkedIn: https://www.linkedin.com/in/aarondfrancisWebsite: https://aaronfrancis.com — find articles, podcasts, courses, and more.Chapters:00:00 - Intro: What is PlanetScale Metal?00:39 - Meet Richard Crowley01:33 - What is Vitess and how does it work?03:00 - Where PlanetScale fits into the picture09:03 - Why EBS is the default and its trade-offs13:03 - How PlanetScale handles durability without EBS16:03 - The engineering work behind PlanetScale Metal22:00 - Deep dive into backups, restores, and availability math25:03 - How PlanetScale replaces instances safely27:11 - Performance gains with Metal: Latency and IOPS explained32:03 - Database workloads that truly benefit from Metal39:10 - The myth of the infinite cloud41:08 - How PlanetScale plans for capacity43:02 - Multi-tenant vs. PlanetScale Managed44:02 - Who should use Metal and when?46:05 - Pricing trade-offs and when Metal becomes cheaper48:27 - Scaling vertically vs. sharding49:57 - What's next for PlanetScale Metal?53:32 - Where to learn more

In the armed forces and struggling with alcohol addiction? Here's how the Addiction Resource Center's intensive outpatient programs (IOPs) can help you. Visit https://sayarc.com/tricare-approved-iop/ for details. Addiction Resource Center LLC. City: Yuba City Address: 1002 Live Oak Blvd. Website: https://sayarc.com

Yuba City's Addiction Resource Center offers TRICARE-approved, career-safe treatment programs specifically designed for active-duty military personnel, addressing unique challenges like combat-related PTSD and substance use disorders in a confidential, specialized setting. Visit https://sayarc.com/tricare-approved-iop/ to learn more. Addiction Resource Center LLC. City: Yuba City Address: 1002 Live Oak Blvd. Website: https://sayarc.com

Active-duty personnel and veterans can now access specialized addiction treatment through Addiction Resource Center's TRICARE-approved IOP in Yuba City. Visit https://sayarc.com/tricare-approved-iop/ for details. Addiction Resource Center LLC. City: Yuba City Address: 1002 Live Oak Blvd. Website: https://sayarc.com

Today, we have Sam Lambert back on the show! Sam is the CEO of PlanetScale, and if you follow him on X, you know he's one of the sharpest voices in the database space—cutting through the hype with deep experience and a no-nonsense approach. In this episode, we dive into PlanetScale's new Metal offering, which has been battle-tested with PlanetScale's high-scale cloud business partners and is now GA. Sam also shares why staying profitable is crucial—not just for the business but for the stability and reliability it guarantees for customers. While many cloud infrastructure companies chase the next hype cycle, Sam prefers to keep it boring—delivering rock-solid performance with no surprises Finally, we close with Sam's thoughts on other happenings in the database space -- Aurora DSQL, Aurora Limitless, MySQL benchmarks, and multi-region strong consistency. Tune in for a deep dive into databases, cloud infrastructure, and what it takes to build a sustainable, high-performance tech company. Timestamps 01:34 Start 06:42 PlanetScale Metal 11:15 The problem with separation of storage and compute 15:02 EBS Tax 17:32 How does Vitess handle durability 22:58 Metal recommended for all PlanetScale users? 27:20 The hidden expense of IOPS for cloud databases 37:41 Timeline of creating PlanetScale Metal 41:32 Focus on profitability 47:52 Removal of hobby plan 57:45 Deprecation of PlanetScale Boost 01:00:24 DSQL 01:01:51 Aurora Limitless 01:04:15 AWS as a partner 01:07:00 The spectacle of AWS re:Invent 01:12:22 Benchmarks and benchmarketing 01:15:51 AWS Databases + multi-region strong consistency

Send us a textJanuary 2025 FinOps news.Instances/Computehttps://cloud.google.com/blog/products/compute/announcing-smaller-machine-types-for-a3-high-vms - The A3 Ultra machine type is available in the following region and zone: St. Ghislain, Belgium, Europe - europe-west1-bhttps://cloud.google.com/blog/products/compute/first-google-axion-processor-c4a-now-ga-with-titanium-ssd - Google Axion Processor-based C4A VMs with Titanium SSD are now generally available. Part of our general-purpose machine family, these instances come with up to 6 TiB of Titanium SSD disks. Titanium SSD is our latest generation of Local SSD. It uses Titanium I/O offload processing and offers enhanced SSD security, performance, and management.Compute Engine - Generally available: Managed instance groups (MIGs) let you create pools of suspended and stopped virtual machine (VM) instances. You can manually suspend and stop VMs in a MIG to save on costs, or use suspended and stopped pools to speed up scale out operations of your MIG. For more information, see About suspending and stopping VMs in a MIG.Data/DBs/AIAzure OpenAI provisioned reservations (June - but not sure we mentioned it)With the introduction of 1-month and 1-year Provisioned Reservations, businesses that commit to using Azure OpenAI on a scale can enjoy substantial discounts compared to the standard pay-as-you-go pricing. You can manage these reservations in Cost analysis in the same way as any other reservation.For further details on how to purchase and manage these reservations, please refer to the article below: Save costs with Microsoft Azure OpenAI Service Provisioned Reservations  Storagehttps://aws.amazon.com/about-aws/whats-new/2025/01/amazon-s3-metadata-generally-available Generally available: Azure NetApp Files now supports minimum volume size of 50 GiB.Generally Available: Azure Files provisioned v2 billing model for HDD (Standard) - (Added to Roadmap 8th Jan 2025 - but released in October 24) The provisioned v2 model for Azure Files HDD (standard) pairs predictability of total cost of ownership with flexibility, allowing you to create a file share that meets your exact storage and performance requirements. Provisioned v2 shares enable independent provisioning of storage, IOPS, and throughput. In addition to predictable pricing and flexible provisioning, provisioned v2 also enables increased scale and performance, up to 256 TiB, 50,000 IOPS, and 5 GiB/sec of throughput; and per share monitoring. Provisioned v2 is generally available in a subset of regions. For the current list of available regions, see provisioned v2 availability.Visibility (Billing conductor - Tags - cost categories)New fields for cost allocation (Enterprise Agreement customers)You can use different le

AWS Morning Brief for the week of December 2, with Corey Quinn. Links:Amazon CloudWatch adds context to observability data in service consoles, accelerating analysisAmazon Cognito introduces Managed Login to support rich branding for end user journeysAmazon Cognito now supports passwordless authentication for low-friction and secure loginsAmazon Connect Email is now generally availableAmazon EBS announces Time-based Copy for EBS SnapshotsAmazon EC2 Auto Scaling introduces highly responsive scaling policiesAmazon EC2 Capacity Blocks now supports instant start times and extensionsAmazon ECR announces 10x increase in repository limit to 100,000Amazon EFS now supports up to 2.5 million IOPS per file systemAmazon S3 now supports enforcement of conditional write operations for S3 general purpose bucketsApplication Signals provides OTEL support via X-Ray OTLP endpoint for tracesAWS delivers enhanced root cause insights to help explain cost anomaliesEnhanced Pricing Calculator now supports discounts and purchase commitments (in preview)AWS PrivateLink now supports cross-region connectivityAnnouncing the new AWS User Notifications SDKAnnouncing new feature tiers: Essentials and Plus for Amazon CognitoAnnouncing Savings Plans Purchase AnalyzerData Exports for FOCUS 1.0 is now in general availabilityIntroducing a new experience for AWS Systems ManagerIntroducing generative AI troubleshooting for Apache Spark in AWS Glue (preview)Understanding how certain database parameters impact scaling in Amazon Aurora Serverless v2Analyzing your AWS Cost Explorer data with Amazon Q Developer: Now Generally AvailableYour guide to AWS for Advertising & Marketing at re:Invent 2024AWS IoT Services alignment with US Cyber Trust MarkStreamlining AWS Organizations Cleanup StrategiesSponsorWiz: wiz.io/lastweek

Tiff and Dana discuss the importance of coding accuracy in dental practices. That includes universal codes everyone can understand, how to stay up-to-date on resources, the best way to know team members are getting paid for all their work, different codes across specialties, and more. Episode resources: Reach out to Tiff and Dana Tune Into DAT's Monthly Webinar Practice Momentum Group Consulting Subscribe to The Dental A-Team podcast Become Dental A-Team Platinum! Review the podcast Transcript: The Dental A Team (00:01.11) Hello Dental A Team listeners, we are back at you today. I have the one and only Miss Dana here with me to podcast. I love pulling Dana in. I love pulling all the consultants in, but I truly love pulling in Dana. think I shouted you out this morning. do. Wednesday core value shout out in our.   I know that we've done some podcasts on that. So if you're not already doing a core value shout out every day or every week, please by all means go listen to those podcasts because it's freaking incredible and Dana you truly are the epitome of ease within our company and for your clients and I just think you need to publicly shout it from the rooftops be Just recognized for that aspect of your personality. You truly do make life easier I know a lot of your clients feel the same way you are   so good at finding the easiest path for the systems implementation for whatever it is that needs to be done for us as a company. So Dana, welcome today. I'm so excited to have you here with me. Thank you for joining me on this beautiful Wednesday. I don't know what day this is gonna air, but it's a Wednesday today. And it's absolutely gorgeous here in Arizona. How are you, Dana?   Dana (01:08.193) doing good, Tim, doing good. love days like today.   The Dental A Team (01:11.629) I do too, I do too. It's starting to get fallish in Arizona, which means 85 degrees instead of the 105 that we had last week, least up in Phoenix. I know you get a little bit more fall down where you're at, but I'll take the 85 over the 105 for sure. Today, Dina, I wanted to pick your brain.   I've got some information today I wanna share with the doctors. It's also for billing departments, for treatment coordinators, for whomever wants to listen to this. But I really wanted us to shout out our doctors for really, really just knowing everything about their businesses. I know that you guys are all here listening. I know you're watching, whatever it might be, to really learn more about the business side and about what the team is doing to help support your practice. So I wanna shout you out for that. And I just think it's a really incredible tool.   and resource to have to truly know what it is that's going on, the inner workings behind the scenes of your practice, aside from just the dentistry that you're performing. So shout out to you guys for being here, for listening. Team members, if your doctor's not listening yet, please share it with them. Dana, today I really wanted to pick your brain and go over some coding information. I know it sounds super boring, you guys, but stick with us. We've got some great tips and tricks and some tools, especially for you doctors who are out there to really   focus in and pay attention to the things that are being input into the system and sent off to insurance companies, or if you're fee for service, you still need to be insanely accurate within your system and making sure that we're using the right tools. So doctors, again, this one's for you as well. Billing representatives, treatment coordinators, front office representatives, office managers, whoever you might be, whoever might be touching a ledger or an account or a code in general dental assistance, hi, Genes, you guys.   This is all gonna be really great information for all of you. Coding with Accuracy happens to be a book, by the way, you can purchase that. But honestly, coding with accuracy is incredibly important and valuable to your system, not only for the billing portion to ensure that we're accurately sending things off to insurance companies, accurately getting paid, but realistically to show super accurately what you've actually done with your patients to your patients. That way, if anything were to ever come about and anyone needed to look into it or   The Dental A Team (03:28.327) your patients had questions and they asked for the account, it makes sense to the next person who's looking at it. And you can say, yes, I did that, that was me. I did that filling, I did that crown, I did that crown seat, I did those pieces. I know a lot of practices, and Dana, I think you've probably seen this too, a lot of practices will overuse, in my opinion, an office visit or a palliative treatment, to certain codes like that and unspecified, because they're just not sure.   what to use. And so they throw one of those, especially office visits, and I'm like, what is this office visit? How many, this patient's been in for 20 office visits. They're like, most of those are crown seats or like if a filling needed to be adjusted or like, and I'm like, wow, so we don't have any documentation right here that we ever sat any of these crowns.   That's an issue. looking at those pieces and making sure that we're super accurate with what we're calling things is something I really, really want to talk about today, Dana. Have you noticed that as well? I know you see a lot of clients, you do a lot of virtual clients, but you see a lot of ledgers, you get a lot of things sent to you, and you have been traveling a ton this year in office to practices as well. So what are you seeing when you're out there when it comes to coding and just kind of like randomness that you're seeing thrown around?   Dana (04:40.983) Yeah, I agree with you on just like the miscellaneous codes. I delivery. What did we deliver? Because we need to know exactly what we delivered today. And then a lot of just like 999 things and sometimes a 999 code you absolutely   The Dental A Team (04:47.133) Yeah.   Dana (04:55.967) can utilize it, should be utilizing it, but oftentimes too, it's like, no, there's actually a code for that. Like we don't have to send a 999 with documentation and notes, there's a code specific for that. So making sure that offices really are up to date, also to like when things change because they do change occasionally. And so just having somebody who knows those things in and out has resources to spot check and that we are billing what we're doing and coding exactly what we're doing.   The Dental A Team (05:25.511) Yeah, I totally agree. The 999 code, I love that one. It is thrown in there for everything and I am guilty of the 999 code because I'm like, don't know what he's even talking about. 999, that sucker. And I'll explain, I'll say exactly what he just said to me. I have no idea what he said, but I've got this. So I'm surely, surely guilty of that one. I do love the staying up to date and doctors, I really want you to know and understand within dentistry.   There's not, like we have a course for billing that will review billing for you and will go over the basics of billing, what it needs to look like, how to send a claim, how to input an EOB and a payment and all of those pieces. But there's really not a good school for billing where it's like, gosh, I'm gonna send them to a billing school and now they've got this accredited school has shown them this kind of like medical billing, right? You can go to medical billing school and now you're a medical biller.   to be a dental biller, you just needed someone ahead of you to show you how to do it. So within this world, it's just super important, like Dana said, that we stay on top of it as best we can. So making sure that we're getting ADA emails sent to us and that we're watching for any codes that change, because they will let us know. Whatever your state's dental association is, I know here it's the AZDA, the California Dental Association.   Whatever it is, make sure that you're signed up for those auto emails, because that's going to be the best resource. And then as those yearly conventions come around that we all love to go to, that we hate taking boring classes, look for any updates. I wouldn't say you've got to hit the billing courses yourself, or you have to send your billing rep to the billing courses. Sometimes they're a bust. Sometimes they're super insurance prone or driven. I don't love that. But if there's anything that's like coding updates or   New laws things like that. It's always a good idea. So I do want to preface it with that Just know always staying up to date just getting those resources sent to you is going to be super super important And now aside from that there are things like coding with confidence coding with accuracy All of those different books that you can get I believe coding with confidence you can order from Amazon or ADA I think both of them have it. I think it probably comes from the ADA when you do it from Amazon, whatever you choose   The Dental A Team (07:37.7) It's a fantastic book and having that resource, there's a companion book that goes with it as well. I always had that resource with me. It was literally in a drawer behind my desk and as soon as I had something pop up for an implant or gosh, when we were doing over dentures and there's just so many parts and pieces and little things that need to be accurately coded.   There's no way I'm gonna remember all of these things or intuitively know it. So I would pull those books out constantly and I would go through it with my doctor and I'd say, okay, does this describe, is this what you're saying? Is this describing it? Because even just for regular dentures, there's different codes that can be used. And if you use one that's a maxillary but you're doing a mandibular denture, you're not gonna get paid, right? And even if you put upper denture in the thing and you did a mandibular code, they're still not gonna pay it because it doesn't match.   So just making sure that those codes are super accurate. Now from a doctor's standpoint, why is this important? Super important because you need to be paid, right? So my owner doctors, you need to be sure that your practice is being paid, that you're being paid for what you're doing, your hygiene team's being paid for what they're doing, and that if, again, anything were ever to have been and come about, somebody looking at the ledger, looking at the account, looking at the chart, can accurately and confidently see exactly what you performed. So not only do you need to get paid,   you need to cover your tail. For my associate doctors and even my hygienist who might be listening, you really, really wanna watch your production and your collections, because typically, especially my associates, you guys are gonna be paid off of that in some form or fashion. So making sure that the coding is correct and that it accurately, actually reflects what you've done is key. Otherwise, you might get paid for a filling when you did an onlay.   Right, and the billing representative, has, or he has no idea, they were not chair side with you. So if it's not fixed chair side, or if you, gosh, Dina, how many times have you seen this one, where chair side, you know, we were scheduled for an MO, chair side, doctor's like, this went into the distal, we've gotta update that. So we update it, we tell the patient, we're like, got another service added, get the treatment plan going, lay them back, finish the filling, and then they go up front, and then they get paid on an MO.   The Dental A Team (09:51.99) because the MOD was never switched out and the appointment went before it was set complete. again, the billing representative, he's not chair side. They have no idea that that billing changed. The dental assistant needed to update and change it. So making sure that that's accurate in there. Now, Dina, I know you have a lot of practices and a lot of associates. You've got a lot of big practices that have a lot of associates. How do you make sure at the end of the day, at the end of the month, at the end of everything, that these guys are knowing exactly what their   being paid on? Like how do you make sure that they know with confidence that they're getting paid for everything that they did?   Dana (10:28.329) Yeah, I have them usually daily check their provider production and check their individual provider day sheet just to make sure that everything was accounted for. If there were changes, if something was walked out inaccurately, catching that from the very beginning is super important because honestly, like you pointed out, the difference in some of these codes is hundreds of dollars worth of production. And that can be even within implant parts, even with indentures, like a difference in that   that coding can majorly impact production. So making sure that everything is accounted for, everything that they did is on there and everything is walked out and ready to submit. So that whether it's insurance based or we've got to call a patient and say, hey, you know, we under collected that service did change, we had added. whether it is patient portion that we've got to update or insurance portion, just making sure that we're catching that. And I like to do it daily because   Claims are submitted daily. We're reaching out to patients and we don't want a patient to go till the end of the month before we're like, hey, by the way, you missed a thing, right? So I like my, especially my associates and hygiene to just look and make sure everything's accounted for each and every day.   The Dental A Team (11:34.98) Yeah. Yes.   The Dental A Team (11:47.01) Yeah, I agree. think that's perfect because pulling that sheet, especially like Dentrix and Eagle Soft and OpenDone, like all of these programs have a super easy sheet to print at the end of the day or even like print screen and then just look at it. So we're not using all the paper all the time. I've definitely had it where a doctor will come back like a week later and be like, we didn't actually do a buildup because we just, you you treat and plan a crown and we should plan a buildup just in case, or you have your doctors who treat and plan only a crown and then add a buildup.   if we needed a buildup and so vice versa. A week later, we're like, I didn't build up on that crown. I'm like, well, bro, she gone, she lost. There's no way, it's so uncomfortable to call a patient and be like, by the way, we forgot to charge you for that billing that's underneath the crown that's to build the tooth back up because of the K. And now I'm in this whole conversation of like, why didn't this just get done the first time? So I totally agree. I think that's brilliant. And doctors also, looking ahead at your schedule,   Dana (12:21.687) It was true.   The Dental A Team (12:43.172) Prepping your schedule in conjunction with that is gonna be huge. We get really comfortable. Our dental assistants are incredible. I was a dental assistant near and dear to my heart. It's my favorite position. If I were ever to like quit everything in life and go back to in-office dentistry, it would have to be as a dental assistant. I would not do anything else. It's my favorite space. But you guys, I messed up sometimes. Like it happens. I would get forgetful.   Like how many times did I forget to grab the bond? And I'm like, you can't do a filling without a bond. How did you forget that? And then expecting me to change it every single time in the chart or make sure that it was accurate ahead of time. Things flip through the cracks. So we've gotta have checks and balances. We can't just rely on one person to get it right every single time. So your dental assistants prepping the charts, prepping your schedule for the next day is huge, but I really wanna implore that you guys, you doctors,   You are looking at your schedules as well. You know what's coming up and you know that it's accurate. I had a dentist that worked in our practice. He's fantastic. He's gone to all of this oral surgery, like extracurricular. He's just, it's insane. I watch his videos on Instagram and I'm like, that's so gross. I always must do him. Like I remember the first time I did a bone flap with you and I was like, what? I can't do this, but he's so good. He did all of these like perio surgeries, oral surgeries. He did so many things in our practice and holy cow.   A GP girl over here, learning how to code for all of these extensive procedures that he was doing. He was doing, you know, he's doing the blood draws before it was even a thing. I am like, are we allowed to do that? Like I'm in my practice, like what the heck? This is crazy. And now I'm having to code things that to me are like outlandish.   and I'm sitting there Googling things. Like, this doesn't make sense. So I'm pulling out my little code book and like, gosh, it is in here. This is a dental thing. We can do this, but there's no way those added procedures would have been accurately coded if I didn't take those extra steps to ensure it. And if he didn't, bless his heart, come to me every day.   The Dental A Team (14:47.322) with a list of the things that needed to be added to tomorrow that wasn't accurate or things that we missed today. He would double check his treatment plans just because they were so extensive. And honestly, there were times, like he did GP work in our practice as well. So there were times too where he would catch a filling surface was missed or an onlay surface was missed. And I'm like, dang, not only are, you know, did we miss something on your giant surgery over here that I literally cannot assist with, cause I will pass out.   But we also miss like a surface on an online, like, goodness gracious, right? But he is my example because he was so diligent about making sure that the charting was accurate. Like, of course he wanted to get paid for the things he was doing, but he's like, I need to make sure that whatever it is that I'm doing, it's all here. It's all accounted for. And when he went to go do all of the accrediting with the oral surgery boards and implant boards and like, he's got all this crazy stuff behind him now. He needed all of those things. He called me from Texas years later.   And I was like, remember that patient that we did that thing? And I'm like, my gosh, yeah. So I'm like looking for this patient. He's like, I need all of their notes and I need all of their ledger and I need everything to submit to the implant board. And I was like, my gosh, thank goodness we went through and did all of those things. So you guys, it doesn't matter what you're doing. You don't have to be doing crazy dentistry or crazy oral surgery within your practice. Those minor things need to get caught as well. And Dana, earlier you mentioned like the 999 code.   And I know we have to go in or have the auto updates done and make sure that the codes are being updated. But I did notice there are more and more systems that even have as simple as broken appointment code already in there, Crown Seat Code, Denture Seat Code, all of these pieces. So when you're working with practices and you're seeing this, or they ask us, we'll get text messages from office managers that are like, this is what he said, what do I code that as?   I don't know, right? But what are you doing? How are you helping them to figure out, this is probably not a pallet over 999 or what an office visit, this is probably X, Y, or Z.   Dana (16:52.117) Yeah, I mean, I'll be honest, if a lot of times I am pulling like a coding with confidence, or I'm googling things and, I'm trying to piece it together or I'm asking, you know, okay, well, like, walk with what does that look like? Walk me through like, can you explain the process to me? So maybe I can find it in here or send me a picture of the part that maybe I can look it up. But it's really just doing due diligence and combing through the codes that are available. And then determining   The Dental A Team (16:58.797) Yeah.   The Dental A Team (17:10.987) Yes.   Dana (17:20.083) If there is a specific code for that procedure and if there's not, then yeah, you do a 999 code with lots of documentation, IOPs, all the things, so that once it gets to insurance, they can determine if it's something that they're covering.   The Dental A Team (17:35.266) I agree, yeah, I love that. I do love Google, I have Googled so many times. I've been in office trying to help them come up with cheat sheets, which is the next little topic here, but that I'm like, what is this? Or give me a picture of this so that I can put it on their cheat sheet. And doctors who are doing things like implants or dentures even, crowns, anything you're doing, having those cheat sheets is super helpful.   I have a lot of my practices throw those into their operations manual. So with the crown setup or whatever, it'll also have the steps and the codes that would be used. We have to update it when they update, but have all of those available there side by side with it. So it'll be like, crown seed, and it'll be the setup, and then it'll be all of the codes. The ones that get wild are our implants, right? Our All-On-X denture cases. Those ones get wildly insane.   dentures, right, start to finish because what happens is in the treatment planning mode, let's use denture, right, as a treatment planner, right, so I'm a dental assistant and the doctor says we need to do a full denture. Cool, maxillary denture. And then I'm like, treatment coordinator, here you go. And they're like, cool. And then they schedule a denture. There's like 16 steps sometimes to a denture.   Right, so having that and being able to break it down and break it apart shows that all the steps and processes were done and then having a cheat sheet that goes along with it helps not only your treatment coordinator and your scheduler, but it helps your biller and your dental assistant, even your hygienist. I've had so many hygienists come to me and say, what step are we on? And I'm like, well, I'm not sure, let's look. Like, let's look at our checklist and see where we're at. So even within that denture, having the denture treatment plan for pricing.   Dana (18:56.011) Yes.   The Dental A Team (19:24.294) Obviously, right, any extractions, any bone grafts that need to be done. If you're doing a temporary denture before the final is done, if you're doing, gosh, if you're doing a scan and a final delivery, like they're getting much faster. But before, remember, we had to have a wax rim, we had to have teeth and wax, we had to have the color shade, we had to have a try-in, then we had to have a realign. Like all of these pieces needed to be segregated out in there so that we treatment plan.   the one thing, but we have those steps readily available so that it can be scheduled correctly and in order. And then having those cheat sheets with those codes lined up is super helpful. I have a practice in Wisconsin that was just getting so confused on the implant process and an ortho process. And I was like, easy peasy, let's just like section this out. And now every single time they've got it laminated and they just pull it out. They're like, I've got my implant sheet. I've got my ortho sheet or whatever. So I always have them add that as well. So Dana.   Wrap it up for us. So we've got coding, checking, all the pieces. What could an office do, a doctor do to ensure maybe even adding it to their operations manual? What's the process they should make sure that is being followed and updated yearly within all of these pieces that we've talked about today?   Dana (20:42.627) Yeah, I think it's added to your yearly calendars that you make sure that you do know the updates you have the codes every year and just like we get Insurance fee schedules and we do all of our insurance updates just add that to that list one So add and make sure we've got do we have the resource for it? And do we know what they are? I think to any time that you are adding a new service just checking and double-checking that you know what the codes are So if you're bringing in a CBC team, make sure that those codes are in there and you've got fees attached to them   and all of those pieces. I love your cheat sheet idea as far as especially where there's a there's a lot of nitty-gritty things that need to get built out for specific things like ortho-like implants making sure that you've got cheat sheets and you make it really really easy and then make sure you've got a very clear communication system for when treatment changes so that it gets changed all the way okay and then I think daily having people look at them and just one   Final tip I guess in in with your cheat sheets oftentimes we call things things that like are not in the code, right? The description of the code is not that and then we're constantly like, what are they actually? What do they actually call right? A lot of your systems will allow you to add notes to like those procedure codes put in what you call it in the office so that it's easy to find it will still put the actual code definition on your piece going on your claims go out, but if you call something something specific   just update it in your system so it's easy for the team to buy.   The Dental A Team (22:12.623) That was brilliant. I know my dentist had like five different terms for a hater bar and I never, was like, I don't know what you're talking about. And the Ribon, he would call the, you know, the Perio procedure by the name of the material he needed. And I was like, so, and he only do this once every, I don't know, 10 years. Like this procedure is never done. He's like, we've got to do a Ribon. Where's the Ribon? I'm like, I don't even remember what this is.   I don't know what that says. So yes, I agree. I love that idea, the descriptions and making sure too then I would transfer. We do this in our Google Drive, you guys. Whatever you might call it, also probably put that on your cheat sheet, maybe in parentheses. Like this is what it is. These are the five different terms that any of our doctors may call it so that it is easy to find and easy to figure out. I think that's brilliant. Awesome, thank you for wrapping us, Dana. I think this was insanely beneficial for all of our doctors out there and our team members again.   Doctors, if you're here listening, congrats. I think that's so huge. It's really important for you to know and understand these things. Share it with your team, because they can use these pieces too, especially anyone who's doing your billing and your practice. And then team members who are out there whose doctors haven't heard this one yet, share it with them. Make sure that they understand what they're getting into as well, and that they're supporting you in your position as a team member to be super accurate, because you're depending on them.   to get things right so that you can do your job. So share it with them. Make sure you guys are all up to date and as always, reach out for any questions you might have. Hello@TheDentalATeam.com. We are not code masters, but you guys, we are solution masters and we will find the answers or find the way and we can help you with just about anything you can think of. Hello@TheDentalATeam.com. We can't wait to catch you next time.  

Michael shares insights into Addiction, trauma, attachment, and EFT. Women in particular have a tendency to take care of everyone else around them first, while putting their own self care and wellness on the back burner. This podcast is designed to give you actionable advice and tools to help you power up your own wellness journey, and live the best life possible!I am your host, Amy Zellmer. I am editor-in-chief of Midwest YOGA Magazine and author of The Chair Yoga Pocket Guide. Additionally I am passionate about yoga, photography, wellness, and all things glittery! You can find out more about me at www.creatingwellnessfromwithin.comFollow me on: Instagram, Facebook, LinkedIn, and Twitter         Today's guest is: Michael BarnettHe is a licensed psychotherapist with over 30 years of clinical experience, and an ICEEFT certified trainer in Emotionally Focused Therapy (EFT). He founded the Atlanta Center for EFT in 2007 and is the cofounder and codirector of the EFT Center of Los Angeles. Prior to beginning private practice in 1993, Michael worked for 8 years in inpatient, dual diagnosis units, and IOPs for addictive disorders.  He began his training in EFT in 2005. Since 2008 Michael has facilitated over 100 EFT certification trainings, workshops and speaking engagements throughout North America and abroad. Throughout his career Michael has worked ardently toward integrating traditional and experiential processes in his approach to working with addictive disorders. He contributed to the existing EFT canon through tailoring EFT to effectively treat couples struggling with trauma and addiction. In 2017, he completed a 3-year research project implementing EFT into the treatment regimen of an inpatient addiction facility in Atlanta. Michael presented with Dr. Gabor Mate on working with addiction from a trauma-informed, attachment perspective at the 2017 EFT Summit. Michael is the author of the Emotionally Focused Therapy Workbook for Addiction: How to Heal the Loneliness and Shame that Trigger Addictive Behaviors. www.michaelbarnettlpc.com Consider supporting the podcast for $5 though BuyMeACoffeeSupport the show

Did you know that with the Accelerated Logs feature in Azure Database for MySQL Business Critical service tier, the service provides 100% improvement in throughput? Additionally, you can automatically scale IOPS up to 80k and storage up to 32TB based on your workload needs. Siddhant (Sidd) Sawant joins Scott Hanselman to walk through the benefits of this tier and highlight its superior performance. Chapters 00:00 - Introduction 00:55 - Updates to Azure DB for MySQL 04:53 - Demo of Accelerated Logs 08:28 - Discussion 10:52 - Wrap-up Recommended resources Advancements in the Business Critical service tier for Azure Database for MySQL - Flexible Server Microsoft Azure innovation powers leading price-performance for MySQL database in the cloud New advancements in Azure Database for MySQL - Flexible Server Business Critical service tier (YouTube) Azure Database for MySQL - Flexible Server service tiers Create a Pay-as-You-Go account (Azure) Create a free account (Azure) Connect Scott Hanselman | Twitter/X: @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Did you know that with the Accelerated Logs feature in Azure Database for MySQL Business Critical service tier, the service provides 100% improvement in throughput? Additionally, you can automatically scale IOPS up to 80k and storage up to 32TB based on your workload needs. Siddhant (Sidd) Sawant joins Scott Hanselman to walk through the benefits of this tier and highlight its superior performance. Chapters 00:00 - Introduction 00:55 - Updates to Azure DB for MySQL 04:53 - Demo of Accelerated Logs 08:28 - Discussion 10:52 - Wrap-up Recommended resources Advancements in the Business Critical service tier for Azure Database for MySQL - Flexible Server Microsoft Azure innovation powers leading price-performance for MySQL database in the cloud New advancements in Azure Database for MySQL - Flexible Server Business Critical service tier (YouTube) Azure Database for MySQL - Flexible Server service tiers Create a Pay-as-You-Go account (Azure) Create a free account (Azure) Connect Scott Hanselman | Twitter/X: @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Did you know that with the Accelerated Logs feature in Azure Database for MySQL Business Critical service tier, the service provides 100% improvement in throughput? Additionally, you can automatically scale IOPS up to 80k and storage up to 32TB based on your workload needs. Siddhant (Sidd) Sawant joins Scott Hanselman to walk through the benefits of this tier and highlight its superior performance. Chapters 00:00 - Introduction 00:55 - Updates to Azure DB for MySQL 04:53 - Demo of Accelerated Logs 08:28 - Discussion 10:52 - Wrap-up Recommended resources Advancements in the Business Critical service tier for Azure Database for MySQL - Flexible Server Microsoft Azure innovation powers leading price-performance for MySQL database in the cloud New advancements in Azure Database for MySQL - Flexible Server Business Critical service tier (YouTube) Azure Database for MySQL - Flexible Server service tiers Create a Pay-as-You-Go account (Azure) Create a free account (Azure) Connect Scott Hanselman | Twitter/X: @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Did you know that with the Accelerated Logs feature in Azure Database for MySQL Business Critical service tier, the service provides 100% improvement in throughput? Additionally, you can automatically scale IOPS up to 80k and storage up to 32TB based on your workload needs. Siddhant (Sidd) Sawant joins Scott Hanselman to walk through the benefits of this tier and highlight its superior performance. Chapters 00:00 - Introduction 00:55 - Updates to Azure DB for MySQL 04:53 - Demo of Accelerated Logs 08:28 - Discussion 10:52 - Wrap-up Recommended resources Advancements in the Business Critical service tier for Azure Database for MySQL - Flexible Server Microsoft Azure innovation powers leading price-performance for MySQL database in the cloud New advancements in Azure Database for MySQL - Flexible Server Business Critical service tier (YouTube) Azure Database for MySQL - Flexible Server service tiers Create a Pay-as-You-Go account (Azure) Create a free account (Azure) Connect Scott Hanselman | Twitter/X: @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Welcome to episode 263 of the Cloud Pod Podcast – where the forecast is always cloudy! This week we're diving into the world of Snowflake, including announcements from their latest conference and details about their recent breach. Seriously – MFA is important! Plus we look at updates to Terraform, Claude 3, and OCI pushing the IOPS limits and much more. Join us!  Titles we almost went with this week: Snowflake Announces State-of-the-Art way for hackers to Talk to your Data Ticketmaster gets a snow job – MFA matters!  The CloudPod wouldn't use Oracle even for a million IOPS Azure finally wakes up to hibernation support JJB No one ever called a Bastion Host Premium until Today – JPB MK I look forward to connecting Kinesis to Pub Sub to Event Hub in the most rube        goldberg eventing architecture ever Hashicorp shows you the way 10 ways to say I want you Matt (I'm not bias with the name) Can we just hibernate ourselves on AI announcements Sus is how i feel about the new Susscanner from AWS OCI has enough power to run Oracle databases with 1 MIllion IOPS OCI wants 1 Million IOPS (dr evil voice) Monday, Tuesday, Hashidays… General News  Terraform AWS Cloud Control API provider is now generally available  The AWS Cloud Control Provider (AWSCC), built around the AWS Cloud Control API and designed to bring new services to Terraform faster, is now generally available.  The 1.0 release represents a step in their effort to provide launch-day support of AWS services.   This service was put into tech preview in 2021.  Glad it’s finally here; although we thought this effort was abandoned, honestly.  Interesting that you can mix HCL Terraform and AWSCC, but specify the different resource types in the configurations.   00:53 New Vault and Boundary offerings advance Security Lifecycle Management at HashiDays 2024   Hashicorp held their “Hashidays” event in London this last week, and announced improvements to their Security Lifecycle Management (SLM) products: Vault and Boundary Vault will be getting Workload Identify Federation, coming soon to Vault Enterprise which enables secretless configuration for vault plugins that integrate with external systems supporting WIF, such as AWS, Azure and Google Cloud.  By enabling secretless configuration, organizations reduce security concerns that can come with using long-lived and highly privileged security credentials.  With WIF

Cale, Evan and Sujit have an insightful discussion with Niko Pamboukas and Siri Velauthapillai about the new Azure Boost feature that is being deployed into the Azure substrate for VMs. They explain the specialized FPGAs and ARM SoCs that provide extreme IOPs for storage and networking and almost no downtime for system upgrades.   Media file: https://azpodcast.blob.core.windows.net/episodes/Episode496.mp3 YouTube: https://youtu.be/4FPQCAmYrzw Resources: Learn more about Azure Boost at https://aka.ms/AzureBoost Learn about accelerated networking with Boost at https://aka.ms/MANA Learn about accelerated storage with Boost at https://aka.ms/NVMe   Other updates: Public preview: Azure Load Balancer now supports Admin State | Azure updates | Microsoft Azure   https://azure.microsoft.com/en-us/updates/public-preview-azure-bastion-premium/ https://azure.microsoft.com/en-us/updates/kubernetesmetadataandlogsfilteringpublicpreview/ https://azure.microsoft.com/en-us/updates/public-preview-azure-load-balancer-health-event-logs/ https://azure.microsoft.com/en-us/updates/generally-available-azure-chaos-studio-supports-a-new-pause-process-fault-for-windows-virtual-machines/

Join us for a deep dive into a perinatal IOP and what that involves. Today's expert shares helpful information so we can understand the value of this higher level of perinatal support. Roxanne Rosenberg is the co-founder and clinical director of Anchor Perinatal Wellness, the Southeast's only perinatal-specific intensive outpatient program (IOP). She is a member of the new federal Maternal Mental Health Task Force and has volunteered with Postpartum Support International at the local and national levels. She earned her bachelor's degree in psychology with honors from Yale University and her master's degree in psychology from Duke University. Roxanne has been supporting pregnant and postpartum people for over 15 years through individual psychotherapy, intensive outpatient programming, birth doula work, and advocacy. Her trainings in perinatal mental health and women's trauma have been available across the country. She is a bilingual Latina mom of two and is a survivor of perinatal loss and trauma.  Show Highlights: What is a perinatal IOP? Reasons why someone might need an IOP Understanding the history of IOPs in the US (first began in Rhode Island in 2000; even now, there are only 32 across the US) IOP resources are available both in-person and virtually. Typical perinatal symptoms that indicate the need for an IOP Barriers to IOP treatment, like insurance limitations (although most insurance will cover it!) Roxanne's role as the facilitator of the support system Promising results in Roxanne's IOP in the last two years Benefits of support in a group setting with a structured program Specific needs and concerns in the IOP environment How to find a perinatal IOP (and housing if you need to go to a different state for care) Anchor Perinatal Wellness supports and accommodates a parent with attachment to their baby by providing childcare. Perinatal IOPs are an underutilized resource because people are unaware of their existence! Roxanne's vision to make these IOPs more available to everyone who needs them The process of starting a perinatal IOP Advice for therapists who want to send their patients for this level of perinatal care Resources: Connect with Roxanne and Anchor Perinatal Wellness: Website, Roxanne's email, Anchor Perinatal's email, Facebook, YouTube, and phone: 919-275-0806 Please find resources in English and Spanish at Postpartum Support International, or by phone/text at 1-800-944-4773. There are many free resources, like online support groups, peer mentors, a specialist provider directory, and perinatal mental health training for therapists, physicians, nurses, doulas, and anyone who wants to better support people for whom they provide services.  You can also follow PSI on social media: Instagram, Facebook, and most other platforms Visit www.postpartum.net/professionals/certificate-trainings/ for information on the grief course.   Visit my website, www.wellmindperinatal.com, for more information, resources, and courses you can take today! Learn more about your ad choices. Visit megaphone.fm/adchoices

This article has a concept I've never heard about: invisible downtime. This is the idea that there are problems in your application that the customer sees. Your servers are running, but the application doesn't work correctly or is pausing with a delay that impacts customers. From an IT perspective, the SLA is being met and there aren't any problems. From a customer viewpoint, they're ready to start looking at a competitor's offering. Lots of developers and operations people know there are issues in our systems. We know networks go down or connectivity to some service is delayed. We also know the database gets slow, or at least, slower than we'd like. We know there are poor-performing code and under-sized hardware, running with storage that doesn't produce as many IOPs as our workload demands. We would also like time to fix these issues, but often we aren't given any resources. Read the rest of Invisible Downtime

To introduce this podcast episode, Emily and Jamie discuss Jamie's 13th wedding anniversary and her upcoming trip. They go on to reflect on the importance of self-care and introduce this episode's guest, Jackie Lightner, talking about the different levels of mental health care and the unique approach of her program, Lightwork Therapy.  Jamie talks with Jackie Lightner, LICSW, and Executive Director of Lightwork Therapy and Recovery, a mental health service provider for women in Massachusetts. They discuss the evolving landscape of mental health care for women, acknowledging historical biases and the pressure on women to fulfill multiple roles. They explore societal expectations, the normalization of therapy, and challenges in accessing mental health support. The conversation delves into the need for intensive outpatient programs (IOPs) for women, highlighting issues with insurance coverage and the importance of tailored, supportive environments like Lightwork's female-focused space. They further discuss the challenges individuals face when transitioning from hospitalization to home care, highlighting the unpredictable wait times and insurance coverage issues. They emphasize the importance of navigating the system and advocating for proper care, sharing personal experiences and strategies to streamline the process. Jackie shares Lightwork's different approaches and experts, as well as their structured 20 week curriculum that covers themes like safety, guilt, and shame. They emphasize the importance of self-care for high-functioning individuals, providing accessible help without the need for referrals. Jackie highlights their commitment to connecting individuals with appropriate care, even if it's not with them. She encourages reaching out via their website or Instagram for support. In this week's Q&A, Emily and Jamie prepare listeners for the warmer weather by answering a question about the use of bug spray on 2 year olds.  This podcast is proudly brought to you by our fabulous sponsors: Feast & Fettle: Use code NAPSPOD for $30 off your first order kozēkozē: Use code NAPS for 20% off your purchase Kibou: Use code NAPS for 15% off your purchase of $89+

In this week's episode, Anna (https://twitter.com/annarrose) and Kobi (https://twitter.com/kobigurk) chat with Gal Arnon (https://galarnon42.github.io/), Ph.D student from the Weizmann Institute of Science (https://weizmann.ac.il/pages/) & Giacomo Fenzi (https://twitter.com/GiacomoFenzi), Ph.D. student in the COMPSEC Lab (https://compsec.epfl.ch/) at EPFL (https://epfl.ch/). Gal and Giacomo are amongst the co-authors of ‘STIR: Reed–Solomon Proximity Testing with Fewer Queries' (https://eprint.iacr.org/2024/390) and in this conversation, they discuss how their research led them to work on these topics and where the thesis for this particular work sparked from. They set the stage by exploring the history of FRI and discussing some hidden nuances in how FRI works. And then they introduce STIR, a system that can be used in place of FRI, which incorporates various optimisations to improve the performance. Here's some additional links for this episode: FRIDA: Data Availability Sampling from FRI by Hall-Andersen, Simkin and Wagner (https://eprint.iacr.org/2024/248.pdf) Lattice-Based Polynomial Commitments: Towards Asymptotic and Concrete Efficiency by Fenzi, Moghaddas and Nguyen (https://eprint.iacr.org/2023/846.pdf) DEEP-FRI: Sampling Outside the Box Improves Soundness by Ben-Sasson, Goldberg, Kopparty and Saraf (https://eprint.iacr.org/2019/336.pdf) Proximity Gaps for Reed–Solomon Codes by Ben-Sasson, Carmon, Ishai, Kopparty and Saraf (https://eprint.iacr.org/2020/654.pdf) IOPs with Inverse Polynomial Soundness Error by Arnon, Chiesa and Yogev (https://eprint.iacr.org/2023/1062.pdf) Episode 293: Exploring Security of ZK Systems with Nethermind's Michał & Albert (https://zeroknowledge.fm/293-2/) Circle STARKs by Haböck, Levit and Papini (https://eprint.iacr.org/2024/278.pdf) Episode 304: Exploring FRI, LogUp and using M31 for STARKs with Ulrich Haböck (https://zeroknowledge.fm/304-2/) FRI-Binius: Improved Polynomial Commitments for Binary Towers (https://www.ulvetanna.io/news/fri-binius) The next ZK Hack IRL is happening May 17-19 in Kraków, apply to join now at zkkrakow.com (https://www.zkkrakow.com/) Aleo (http://aleo.org/) is a new Layer-1 blockchain that achieves the programmability of Ethereum, the privacy of Zcash, and the scalability of a rollup. Dive deeper and discover more about Aleo at http://aleo.org/ (http://aleo.org/) If you like what we do: * Find all our links here! @ZeroKnowledge | Linktree (https://linktr.ee/zeroknowledge) * Subscribe to our podcast newsletter (https://zeroknowledge.substack.com) * Follow us on Twitter @zeroknowledgefm (https://twitter.com/zeroknowledgefm) * Join us on Telegram (https://zeroknowledge.fm/telegram) * Catch us on YouTube (https://zeroknowledge.fm/)

In this episode, we provide an overview of Amazon EBS, which stands for Elastic Block Storage. We explain what block storage is and how EBS provides highly available and high-performance storage volumes that can be attached to EC2 instances. We discuss the various EBS volume types, including GP3, GP2, provisioned IOPS, and HDD volumes, and explain how they differ in performance characteristics like IOPS and throughput. We go over important concepts like IOPS, throughput, and volume types so listeners can make informed decisions when provisioning EBS. We also cover EBS features like snapshots, encryption, direct API access, and ECS integration. Overall, this is a comprehensive guide to understanding EBS and choosing the right options based on your workload needs.

Thu, 01 Feb 2024 16:30:00 +0000 https://podcast.cloudonaut.io/85-losing-trust-in-kms c88b842d6dc869b9d099d0c0a50d6ca5 Andreas and Michael are losing trust in KMS because of a potential key policy privilege escalation. Andreas and Michael Wittig are building on AWS since 2009. Follow their journey of developing products like bucketAV, marbot, and HyperEnv and learn from practice. Topics KMS Key Policy Privilege Escalation AWS Management Console misses ability to integrate with AWS Marketplace solutions AWS News Check Links KMS Key Policy Privilege Escalation AWS CodeBuild announces support for reserved capacity Amazon ECS announces managed instance draining AWS announces higher read IOPS for Amazon Elastic File System Amazon ECS Service Connect introduces support for automatic traffic encryption with TLS Certificates Amazon Inspector now supports CIS Benchmark assessments for operating systems in EC2 instances Amazon EKS and Amazon EKS Distro now support Kubernetes version 1.29 Provisioned capacity for API limits now available in Amazon Cognito Yan Cui on Provisioned capacity for Cognito API limits Subscribe Make sure you are not missing upcoming shows … Podcast feed YouTube channel Newsletter Projects bucketAV — Antivirus protection for Amazon S3 marbot — AWS Monitoring made simple! HyperEnv for GitHub Actions — Deploy self-hosted GitHub runners on AWS with ease! attachmentAV — Antivirus for Atlassian Jira and Confluence Contact and Feedback hello@cloudonaut.io Mastodon (Andreas) Mastodon (Michael) LinkedIn (Andreas) LinkedIn (Michael) 85 full Andreas and Michael are losing trust in KMS because of a potential key policy privilege escalation. no Andreas Wittig and Michael Wittig focusing on AWS Cloud

Evelyn Osman, Principal Platform Engineer at AutoScout24, joins Corey on Screaming in the Cloud to discuss the dire need for developers to agree on a standardized tool set in order to scale their projects and innovate quickly. Corey and Evelyn pick apart the new products being launched in cloud computing and discover a large disconnect between what the industry needs and what is actually being created. Evelyn shares her thoughts on why viewing platforms as products themselves forces developers to get into the minds of their users and produces a better end result.About EvelynEvelyn is a recovering improviser currently role playing as a Lead Platform Engineer at Autoscout24 in Munich, Germany. While she says she specializes in AWS architecture and integration after spending 11 years with it, in truth she spends her days convincing engineers that a product mindset will make them hate their product managers less.Links Referenced:LinkedIn: https://www.linkedin.com/in/evelyn-osman/TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. My guest today is Evelyn Osman, engineering manager at AutoScout24. Evelyn, thank you for joining me.Evelyn: Thank you very much, Corey. It's actually really fun to be on here.Corey: I have to say one of the big reasons that I was enthused to talk to you is that you have been using AWS—to be direct—longer than I have, and that puts you in a somewhat rarefied position where AWS's customer base has absolutely exploded over the past 15 years that it's been around, but at the beginning, it was a very different type of thing. Nowadays, it seems like we've lost some of that magic from the beginning. Where do you land on that whole topic?Evelyn: That's actually a really good point because I always like to say, you know, when I come into a room, you know, I really started doing introductions like, “Oh, you know, hey,” I'm like, you know, “I'm this director, I've done this XYZ,” and I always say, like, “I'm Evelyn, engineering manager, or architect, or however,” and then I say, you know, “I've been working with AWS, you know, 11, 12 years,” or now I can't quite remember.Corey: Time becomes a flat circle. The pandemic didn't help.Evelyn: [laugh] Yeah, I just, like, a look at that the year, and I'm like, “Jesus. It's been that long.” Yeah. And usually, like you know, you get some odd looks like, “Oh, my God, you must be a sage.” And for me, I'm… you see how different services kind of, like, have just been reinventions of another one, or they just take a managed service and make another managed service around it. So, I feel that there's a lot of where it's just, you know, wrapping up a pretty bow, and calling it something different, it feels like.Corey: That's what I've been low-key asking people for a while now over the past year, namely, “What is the most foundational, interesting thing that AWS has done lately, that winds up solving for this problem of whatever it is you do as a company? What is it that has foundationally made things better that AWS has put out in the last service? What was it?” And the answers I get are all depressingly far in the past, I have to say. What's yours?Evelyn: Honestly, I think the biggest game-changer I remember experiencing was at an analyst summit in Stockholm when they announced Lambda.Corey: That was announced before I even got into this space, as an example of how far back things were. And you're right. That was transformative. That was awesome.Evelyn: Yeah, precisely. Because before, you know, we were always, like, trying to figure, okay, how do we, like, launch an instance, run some short code, and then clean it up. AWS is going to charge for an hour, so we need to figure out, you know, how to pack everything into one instance, run for one hour. And then they announced Lambda, and suddenly, like, holy shit, this is actually a game changer. We can actually write small functions that do specific things.And, you know, you go from, like, microservices, like, to like, tiny, serverless functions. So, that was huge. And then DynamoDB along with that, really kind of like, transformed the entire space for us in many ways. So, back when I was at TIBCO, there was a few innovations around that, even, like, one startup inside TIBCO that quite literally, their entire product was just Lambda functions. And one of their problems was, they wanted to sell in the Marketplace, and they couldn't figure out how to sell Lambda on the marketplace.Corey: It's kind of wild when we see just how far it's come, but also how much they've announced that doesn't change that much, to be direct. For me, one of the big changes that I remember that really made things better for customers—thought it took a couple of years—was EFS. And even that's a little bit embarrassing because all that is, “All right, we finally found a way to stuff a NetApp into us-east-1,” so now NFS, just like you used to use it in the 90s and the naughts, can be done responsibly in the cloud. And that, on some level, wasn't a feature launch so much as it was a concession to the ways that companies had built things and weren't likely to change.Evelyn: Honestly, I found the EFS launch to be a bit embarrassing because, like, you know, when you look closer at it, you realize, like, the performance isn't actually that great.Corey: Oh, it was horrible when it launched. It would just slam to a halt because you got the IOPS scaled with how much data you stored on it. The documentation explicitly said to use dd to start loading a bunch of data onto it to increase the performance. It's like, “Look, just sandbag the thing so it does what you'd want.” And all that stuff got fixed, but at the time it looked like it was clown shoes.Evelyn: Yeah, and that reminds me of, like, EBS's, like, gp2 when we're, like you know, we're talking, like, okay, provision IOPS with gp2. We just kept saying, like, just give yourself really big volume for performance. And it feel like they just kind of kept that with EFS. And it took years for them to really iterate off of that. Yeah, so, like, EFS was a huge thing, and I see us, we're still using it now today, and like, we're trying to integrate, especially for, like, data center migrations, but yeah, you always see that a lot of these were first more for, like, you know, data centers to the cloud, you know. So, first I had, like, EC2 classic. That's where I started. And I always like to tell a story that in my team, we're talking about using AWS, I was the only person fiercely against it because we did basically large data processing—sorry, I forget the right words—data analytics. There we go [laugh].Corey: I remember that, too. When it first came out, it was, “This sounds dangerous and scary, and it's going to be a flash in the pan because who would ever trust their core compute infrastructure to some random third-party company, especially a bookstore?” And yeah, I think I got that one very wrong.Evelyn: Yeah, exactly. I was just like, no way. You know, I see all these articles talking about, like, terrible disk performance, and here I am, where it's like, it's my bread and butter. I'm specialized in it, you know? I write code in my sleep and such.[Yeah, the interesting thing is, I was like, first, it was like, I can 00:06:03] launch services, you know, to kind of replicate when you get in a data center to make it feature comparable, and then it was taking all this complex services and wrapping it up in a pretty bow for—as a managed service. Like, EKS, I think, was the biggest one, if we're looking at managed services. Technically Elasticsearch, but I feel like that was the redheaded stepchild for quite some time.Corey: Yeah, there was—Elasticsearch was a weird one, and still is. It's not a pleasant service to run in any meaningful sense. Like, what people actually want as the next enhancement that would excite everyone is, I want a serverless version of this thing where I can just point it at a bunch of data, I hit an API that I don't have to manage, and get Elasticsearch results back from. They finally launched a serverless offering that's anything but. You have to still provision compute units for it, so apparently, the word serverless just means managed service over at AWS-land now. And it just, it ties into the increasing sense of disappointment I've had with almost all of their recent launches versus what I felt they could have been.Evelyn: Yeah, the interesting thing about Elasticsearch is, a couple of years ago, they came out with OpenSearch, a competing Elasticsearch after [unintelligible 00:07:08] kind of gave us the finger and change the licensing. I mean, OpenSearch actually become a really great offering if you run it yourself, but if you use their managed service, it can kind—you lose all the benefits, in a way.Corey: I'm curious, as well, to get your take on what I've been seeing that I think could only be described as an internal shift, where it's almost as if there's been a decree passed down that every service has to run its own P&L or whatnot, and as a result, everything that gets put out seems to be monetized in weird ways, even when I'd argue it shouldn't be. The classic example I like to use for this is AWS Config, where it charges you per evaluation, and that happens whenever a cloud resource changes. What that means is that by using the cloud dynamically—the way that they supposedly want us to do—we wind up paying a fee for that as a result. And it's not like anyone is using that service in isolation; it is definitionally being used as people are using other cloud resources, so why does it cost money? And the answer is because literally everything they put out costs money.Evelyn: Yep, pretty simple. Oftentimes, there's, like, R&D that goes into it, but the charges seem a bit… odd. Like from an S3 lens, was, I mean, that's, like, you know, if you're talking about services, that was actually a really nice one, very nice holistic overview, you know, like, I could drill into a data lake and, like, look into things. But if you actually want to get anything useful, you have to pay for it.Corey: Yeah. Everything seems to, for one reason or another, be stuck in this place where, “Well, if you want to use it, it's going to cost.” And what that means is that it gets harder and harder to do anything that even remotely resembles being able to wind up figuring out where's the spend going, or what's it going to cost me as time goes on? Because it's not just what are the resources I'm spinning up going to cost, what are the second, third, and fourth-order effects of that? And the honest answer is, well, nobody knows. You're going to have to basically run an experiment and find out.Evelyn: Yeah. No, true. So, what I… at AutoScout, we actually ended up doing is—because we're trying to figure out how to tackle these costs—is they—we built an in-house cost allocation solution so we could track all of that. Now, AWS has actually improved Cost Explorer quite a bit, and even, I think, Billing Conductor was one that came out [unintelligible 00:09:21], kind of like, do a custom tiered and account pricing model where you can kind of do the same thing. But even that also, there is a cost with it.I think that was trying to compete with other, you know, vendors doing similar solutions. But it still isn't something where we see that either there's, like, arbitrarily low pricing there, or the costs itself doesn't really quite make sense. Like, AWS [unintelligible 00:09:45], as you mentioned, it's a terrific service. You know, we try to use it for compliance enforcement and other things, catching bad behavior, but then as soon as people see the price tag, we just run away from it. So, a lot of the security services themselves, actually, the costs, kind of like, goes—skyrockets tremendously when you start trying to use it across a large organization. And oftentimes, the organization isn't actually that large.Corey: Yeah, it gets to this point where, especially in small environments, you have to spend more energy and money chasing down what the cost is than you're actually spending on the thing. There were blog posts early on that, “Oh, here's how you analyze your bill with Redshift,” and that was a minimum 750 bucks a month. It's, well, I'm guessing that that's not really for my $50 a month account.Evelyn: Yeah. No, precisely. I remember seeing that, like, entire ETL process is just, you know, analyze your invoice. Cost [unintelligible 00:10:33], you know, is fantastic, but at the end of the day, like, what you're actually looking at [laugh], is infinitesimally small compared to all the data in that report. Like, I think oftentimes, it's simply, you know, like, I just want to look at my resources and allocate them in a multidimensional way. Which actually isn't really that multidimensional, when you think about it [laugh].Corey: Increasingly, Cost Explorer has gotten better. It's not a new service, but every iteration seems to improve it to a point now where I'm talking to folks, and they're having a hard time justifying most of the tools in the cost optimization space, just because, okay, they want a percentage of my spend on AWS to basically be a slightly better version of a thing that's already improving and works for free. That doesn't necessarily make sense. And I feel like that's what you get trapped into when you start going down the VC path in the cost optimization space. You've got to wind up having a revenue model and an offering that scales through software… and I thought, originally, I was going to be doing something like that. At this point, I'm unconvinced that anything like that is really tenable.Evelyn: Yeah. When you're a small organization you're trying to optimize, you might not have the expertise and the knowledge to do so, so when one of these small consultancies comes along, saying, “Hey, we're going to charge you a really small percentage of your invoice,” like, okay, great. That's, like, you know, like, a few $100 a month to make sure I'm fully optimized, and I'm saving, you know, far more than that. But as soon as your invoice turns into, you know, it's like $100,000, or $300,000 or more, that percentage becomes rather significant. And I've had vendors come to me and, like, talk to me and is like, “Hey, we can, you know, for a small percentage, you know, we're going to do this machine learning, you know, AI optimization for you. You know, you don't have to do anything. We guaranteed buybacks your RIs.” And as soon as you look at the price tag with it, we just have to walk away. Or oftentimes we look at it, and there are truly very simple ways to do it on your own, if you just kind of put some thought into it.Corey: While we want to talking a bit before this show, you taught me something new about GameLift, which I think is a different problem that AWS has been dealing with lately. I've never paid much attention to it because it is the—as I assume from what it says on the tin, oh, it's a service for just running a whole bunch of games at scale, and I'm not generally doing that. My favorite computer game remains to be Twitter at this point, but that's okay. What is GameLift, though, because you want to shining a different light on it, which makes me annoyed that Amazon Marketing has not pointed this out.Evelyn: Yeah, so I'll preface this by saying, like, I'm not an expert on GameLift. I haven't even spun it up myself because there's quite a bit of price. I learned this fall while chatting with an SA who works in the gaming space, and it kind of like, I went, like, “Back up a second.” If you think about, like, I'm, you know, like, World of Warcraft, all you have are thousands of game clients all over the world, playing the same game, you know, on the same server, in the same instance, and you need to make sure, you know, that when I'm running, and you're running, that we know that we're going to reach the same point the same time, or if there's one object in that room, that only one of us can get it. So, all these servers are doing is tracking state across thousands of clients.And GameLift, when you think about your dedicated game service, it really is just multi-region distributed state management. Like, at the basic, that's really what it is. Now, there's, you know, quite a bit more happening within GameLift, but that's what I was going to explain is, like, it's just state management. And there are far more use cases for it than just for video games.Corey: That's maddening to me because having a global session state store, for lack of a better term, is something that so many customers have built themselves repeatedly. They can build it on top of primitives like DynamoDB global tables, or alternately, you have a dedicated region where that thing has to live and everything far away takes forever to round-trip. If they've solved some of those things, why on earth would they bury it under a gaming-branded service? Like, offer that primitive to the rest of us because that's useful.Evelyn: No, absolutely. And honestly, I wouldn't be surprised if you peeled back the curtain with GameLift, you'll find a lot of—like, several other you know, AWS services that it's just built on top of. I kind of mentioned earlier is, like, what I see now with innovation, it's like we just see other services packaged together and releases a new product.Corey: Yeah, IoT had the same problem going on for years where there was a lot of really good stuff buried in there, like IOT events. People were talking about using that for things like browser extensions and whatnot, but you need to be explicitly told that that's a thing that exists and is handy, but otherwise you'd never know it was there because, “Well, I'm not building anything that's IoT-related. Why would I bother?” It feels like that was one direction that they tended to go in.And now they take existing services that are, mmm, kind of milquetoast, if I'm being honest, and then saying, “Oh, like, we have Comprehend that does, effectively detection of themes, keywords, and whatnot, from text. We're going to wind up re-releasing that as Comprehend Medical.” Same type of thing, but now focused on a particular vertical. Seems to me that instead of being a specific service for that vertical, just improve the baseline the service and offer HIPAA compliance if it didn't exist already, and you're mostly there. But what do I know? I'm not a product manager trying to get promoted.Evelyn: Yeah, that's true. Well, I was going to mention that maybe it's the HIPAA compliance, but actually, a lot of their services already have HIPAA compliance. And I've stared far too long at that compliance section on AWS's site to know this, but you know, a lot of them actually are HIPAA-compliant, they're PCI-compliant, and ISO-compliant, and you know, and everything. So, I'm actually pretty intrigued to know why they [wouldn't 00:16:04] take that advantage.Corey: I just checked. Amazon Comprehend is itself HIPAA-compliant and is qualified and certified to hold Personal Health Information—PHI—Private Health Information, whatever the acronym stands for. Now, what's the difference, then, between that and Medical? In fact, the HIPAA section says for Comprehend Medical, “For guidance, see the previous section on Amazon Comprehend.” So, there's no difference from a regulatory point of view.Evelyn: That's fascinating. I am intrigued because I do know that, like, within AWS, you know, they have different segments, you know? There's, like, Digital Native Business, there's Enterprise, there's Startup. So, I am curious how things look over the engineering side. I'm going to talk to somebody about this now [laugh].Corey: Yeah, it's the—like, I almost wonder, on some level, it feels like, “Well, we wound to building this thing in the hopes that someone would use it for something. And well, if we just use different words, it checks a box in some analyst's chart somewhere.” I don't know. I mean, I hate to sound that negative about it, but it's… increasingly when I talk to customers who are active in these spaces around the industry vertical targeted stuff aimed at their industry, they're like, “Yeah, we took a look at it. It was adorable, but we're not using it that way. We're going to use either the baseline version or we're going to work with someone who actively gets our industry.” And I've heard that repeated about three or four different releases that they've put out across the board of what they've been doing. It feels like it is a misunderstanding between what the world needs and what they're able to or willing to build for us.Evelyn: Not sure. I wouldn't be surprised, if we go far enough, it could probably be that it's just a product manager saying, like, “We have to advertise directly to the industry.” And if you look at it, you know, in the backend, you know, it's an engineer, you know, kicking off a build and just changing the name from Comprehend to Comprehend Medical.Corey: And, on some level, too, they're moving a lot more slowly than they used to. There was a time where they were, in many cases, if not the first mover, the first one to do it well. Take Code Whisperer, their AI powered coding assistant. That would have been a transformative thing if GitHub Copilot hadn't beaten them every punch, come out with new features, and frankly, in head-to-head experiments that I've run, came out way better as a product than what Code Whisperer is. And while I'd like to say that this is great, but it's too little too late. And when I talk to engineers, they're very excited about what Copilot can do, and the only people I see who are even talking about Code Whisperer work at AWS.Evelyn: No, that's true. And so, I think what's happening—and this is my opinion—is that first you had AWS, like, launching a really innovative new services, you know, that kind of like, it's like, “Ah, it's a whole new way of running your workloads in the cloud.” Instead of you know, basically, hiring a whole team, I just click a button, you have your instance, you use it, sell software, blah, blah, blah, blah. And then they went towards serverless, and then IoT, and then it started targeting large data lakes, and then eventually that kind of run backwards towards security, after the umpteenth S3 data leak.Corey: Oh, yeah. And especially now, like, so they had a hit in some corners with SageMaker, so now there are 40 services all starting with the word SageMaker. That's always pleasant.Evelyn: Yeah, precisely. And what I kind of notice is… now they're actually having to run it even further back because they caught all the corporations that could pivot to the cloud, they caught all the startups who started in the cloud, and now they're going for the larger behemoths who have massive data centers, and they don't want to innovate. They just want to reduce this massive sysadmin team. And I always like to use the example of a Bare Metal. When that came out in 2019, everybody—we've all kind of scratched your head. I'm like, really [laugh]?Corey: Yeah, I could see where it makes some sense just for very specific workloads that involve things like specific capabilities of processors that don't work under emulation in some weird way, but it's also such a weird niche that I'm sure it's there for someone. My default assumption, just given the breadth of AWS's customer base, is that whenever I see something that they just announced, well, okay, it's clearly not for me; that doesn't mean it's not meeting the needs of someone who looks nothing like me. But increasingly as I start exploring the industry in these services have time to percolate in the popular imagination and I still don't see anything interesting coming out with it, it really makes you start to wonder.Evelyn: Yeah. But then, like, I think, like, roughly a year or something, right after Bare Metal came out, they announced Outposts. So, then it was like, another way to just stay within your data center and be in the cloud.Corey: Yeah. There's a bunch of different ways they have that, okay, here's ways you can run AWS services on-prem, but still pay us by the hour for the privilege of running things that you have living in your facility. And that doesn't seem like it's quite fair.Evelyn: That's exactly it. So, I feel like now it's sort of in diminishing returns and sort of doing more cloud-native work compared to, you know, these huge opportunities, which is everybody who still has a data center for various reasons, or they're cloud-native, and they grow so big, that they actually start running their own data centers.Corey: I want to call out as well before we wind up being accused of being oblivious, that we're recording this before re:Invent. So, it's entirely possible—I hope this happens—that they announce something or several some things that make this look ridiculous, and we're embarrassed to have had this conversation. And yeah, they're totally getting it now, and they have completely surprised us with stuff that's going to be transformative for almost every customer. I've been expecting and hoping for that for the last three or four re:Invents now, and I haven't gotten it.Evelyn: Yeah, that's right. And I think there's even a new service launches that actually are missing fairly obvious things in a way. Like, mine is the Managed Workflow for Amazon—it's Managed Airflow, sorry. So, we were using Data Pipeline for, you know, big ETL processing, so it was an in-house tool we kind of built at Autoscout, we do platform engineering.And it was deprecated, so we looked at a new—what to replace it with. And so, we looked at Airflow, and we decided this is the way to go, we want to use managed because we don't want to maintain our own infrastructure. And the problem we ran into is that it doesn't have support for shared VPCs. And we actually talked to our account team, and they were confused. Because they said, like, “Well, every new service should support it natively.” But it just didn't have it. And that's, kind of, what, I kind of found is, like, there's—it feels—sometimes it's—there's a—it's getting rushed out the door, and it'll actually have a new managed service or new service launched out, but they're also sort of cutting some corners just to actually make sure it's packaged up and ready to go.Corey: When I'm looking at this, and seeing how this stuff gets packaged, and how it's built out, I start to understand a pattern that I've been relatively down on across the board. I'm curious to get your take because you work at a fairly sizable company as an engineering manager, running teams of people who do this sort of thing. Where do you land on the idea of companies building internal platforms to wrap around the offerings that the cloud service providers that they use make available to them?Evelyn: So, my opinion is that you need to build out some form of standardized tool set in order to actually be able to innovate quickly. Now, this sounds counterintuitive because everyone is like, “Oh, you know, if I want to innovate, I should be able to do this experiment, and try out everything, and use what works, and just release it.” And that greatness [unintelligible 00:23:14] mentality, you know, it's like five talented engineers working to build something. But when you have, instead of five engineers, you have five teams of five engineers each, and every single team does something totally different. You know, one uses Scala, and other on TypeScript, another one, you know .NET, and then there could have been a [last 00:23:30] one, you know, comes in, you know, saying they're still using Ruby.And then next thing you know, you know, you have, like, incredibly diverse platforms for services. And if you want to do any sort of like hiring or cross-training, it becomes incredibly difficult. And actually, as the organization grows, you want to hire talent, and so you're going to have to hire, you know, a developer for this team, you going to have to hire, you know, Ruby developer for this one, a Scala guy here, a Node.js guy over there.And so, this is where we say, “Okay, let's agree. We're going to be a Scala shop. Great. All right, are we running serverless? Are we running containerized?” And you agree on those things. So, that's already, like, the formation of it. And oftentimes, you start with DevOps. You'll say, like, “I'm a DevOps team,” you know, or doing a DevOps culture, if you do it properly, but you always hit this scaling issue where you start growing, and then how do you maintain that common tool set? And that's where we start looking at, you know, having a platform… approach, but I'm going to say it's Platform-as-a-Product. That's the key.Corey: Yeah, that's a good way of framing it because originally, the entire world needed that. That's what RightScale was when EC2 first came out. It was a reimagining of the EC2 console that was actually usable. And in time, AWS improved that to the point where RightScale didn't really have a place anymore in a way that it had previously, and that became a business challenge for them. But you have, what is it now, 2, 300 services that AWS has put out, and out, and okay, great. Most companies are really only actively working with a handful of those. How do you make those available in a reasonable way to your teams, in ways that aren't distracting, dangerous, et cetera? I don't know the answer on that one.Evelyn: Yeah. No, that's true. So, full disclosure. At AutoScout, we do platform engineering. So, I'm part of, like, the platform engineering group, and we built a platform for our product teams. It's kind of like, you need to decide to [follow 00:25:24] those answers, you know? Like, are we going to be fully containerized? Okay, then, great, we're going to use Fargate. All right, how do we do it so that developers don't actually—don't need to think that they're running Fargate workloads?And that's, like, you know, where it's really important to have those standardized abstractions that developers actually enjoy using. And I'd even say that, before you start saying, “Ah, we're going to do platform,” you say, “We should probably think about developer experience.” Because you can do a developer experience without a platform. You can do that, you know, in a DevOps approach, you know? It's basically build tools that makes it easy for developers to write code. That's the first step for anything. It's just, like, you have people writing the code; make sure that they can do the things easily, and then look at how to operate it.Corey: That sure would be nice. There's a lack of focus on usability, especially when it comes to a number of developer tools that we see out there in the wild, in that, they're clearly built by people who understand the problem space super well, but they're designing these things to be used by people who just want to make the website work. They don't have the insight, the knowledge, the approach, any of it, nor should they necessarily be expected to.Evelyn: No, that's true. And what I see is, a lot of the times, it's a couple really talented engineers who are just getting shit done, and they get shit done however they can. So, it's basically like, if they're just trying to run the website, they're just going to write the code to get things out there and call it a day. And then somebody else comes along, has a heart attack when see what's been done, and they're kind of stuck with it because there is no guardrails or paved path or however you want to call it.Corey: I really hope—truly—that this is going to be something that we look back and laugh when this episode airs, that, “Oh, yeah, we just got it so wrong. Look at all the amazing stuff that came out of re:Invent.” Are you going to be there this year?Evelyn: I am going to be there this year.Corey: My condolences. I keep hoping people get to escape.Evelyn: This is actually my first one in, I think, five years. So, I mean, the last time I was there was when everybody's going crazy over pins. And I still have a bag of them [laugh].Corey: Yeah, that did seem like a hot-second collectable moment, didn't it?Evelyn: Yeah. And then at the—I think, what, the very last day, as everybody's heading to re:Play, you could just go into the registration area, and they just had, like, bags of them lying around to take. So, all the competing, you know, to get the requirements for a pin was kind of moot [laugh].Corey: Don't you hate it at some point where it's like, you feel like I'm going to finally get this crowning achievement, it's like or just show up at the buffet at the end and grab one of everything, and wow, that would have saved me a lot of pain and trouble.Evelyn: Yeah.Corey: Ugh, scavenger hunts are hard, as I'm about to learn to my own detriment.Evelyn: Yeah. No, true. Yeah. But I am really hoping that re:Invent proves me wrong. Embarrassingly wrong, and then all my colleagues can proceed to mock me for this ridiculous podcast that I made with you. But I am a fierce skeptic. Optimistic nihilist, but still a nihilist, so we'll see how re:Invent turns out.Corey: So, I am curious, given your experience at more large companies than I tend to be embedded with for any period of time, how have you found that these large organizations tend to pick up new technologies? What does the adoption process look like? And honestly, if you feel like throwing some shade, how do they tend to get it wrong?Evelyn: In most cases, I've seen it go… terrible. Like, it just blows up in their face. And I say that is because a lot of the time, an organization will say, “Hey, we're going to adopt this new way of organizing teams or developing products,” and they look at all the practices. They say, “Okay, great. Product management is going to bring it in, they're going to structure things, how we do the planning, here's some great charts and diagrams,” but they don't really look at the culture aspect.And that's always where I've seen things fall apart. I've been in a room where, you know, our VP was really excited about team topologies and say, “Hey, we're going to adopt it.” And then an engineering manager proceeded to say, “Okay, you're responsible for this team, you're responsible for that team, you're responsible for this team talking to, like, a team of, like, five engineers,” which doesn't really work at all. Or, like, I think the best example is DevOps, you know, where you say, “Ah, we're going to adopt DevOps, we're going to have a DevOps team, or have a DevOps engineer.”Corey: Step one: we're going to rebadge everyone with existing job titles to have the new fancy job titles that reflect it. It turns out that's not necessarily sufficient in and of itself.Evelyn: Not really. The Spotify model. People say, like, “Oh, we're going to do the Spotify model. We're going to do skills, tribes, you know, and everything. It's going to be awesome, it's going to be great, you know, and nice, cross-functional.”The reason I say it bails on us every single time is because somebody wants to be in control of the process, and if the process is meant to encourage collaboration and innovation, that person actually becomes a chokehold for it. And it could be somebody that says, like, “Ah, I need to be involved in every single team, and listen to know what's happening, just so I'm aware of it.” What ends up happening is that everybody differs to them. So, there is no collaboration, there is no innovation. DevOps, you say, like, “Hey, we're going to have a team to do everything, so your developers don't need to worry about it.” What ends up happening is you're still an ops team, you still have your silos.And that's always a challenge is you actually have to say, “Okay, what are the cultural values around this process?” You know, what is SRE? What is DevOps, you know? Is it seen as processes, is it a series of principles, platform, maybe, you know? We have to say, like—that's why I say, Platform-as-a-Product because you need to have that product mindset, that culture of product thinking, to really build a platform that works because it's all about the user journey.It's not about building a common set of tools. It's the user journey of how a person interacts with their code to get it into a production environment. And so, you need to understand how that person sits down at their desk, starts the laptop up, logs in, opens the IDE, what they're actually trying to get done. And once you understand that, then you know your requirements, and you build something to fill those things so that they are happy to use it, as opposed to saying, “This is our platform, and you're going to use it.” And they're probably going to say, “No.” And the next thing, you know, they're just doing their own thing on the side.Corey: Yeah, the rise of Shadow IT has never gone away. It's just, on some level, it's the natural expression, I think it's an immune reaction that companies tend to have when process gets in the way. Great, we have an outcome that we need to drive towards; we don't have a choice. Cloud empowered a lot of that and also has given tools to help rein it in, and as with everything, the arms race continues.Evelyn: Yeah. And so, what I'm going to continue now, kind of like, toot the platform horn. So, Gregor Hohpe, he's a [solutions architect 00:31:56]—I always f- up his name. I'm so sorry, Gregor. He has a great book, and even a talk, called The Magic of Platforms, that if somebody is actually curious about understanding of why platforms are nice, they should really watch that talk.If you see him at re:Invent, or a summit or somewhere giving a talk, go listen to that, and just pick his brain. Because that's—for me, I really kind of strongly agree with his approach because that's really how, like, you know, as he says, like, boost innovation is, you know, where you're actually building a platform that really works.Corey: Yeah, it's a hard problem, but it's also one of those things where you're trying to focus on—at least ideally—an outcome or a better situation than you currently find yourselves in. It's hard to turn down things that might very well get you there sooner, faster, but it's like trying to effectively cargo-cult the leadership principles from your last employer into your new one. It just doesn't work. I mean, you see more startups from Amazonians who try that, and it just goes horribly because without the cultural understanding and the supporting structures, it doesn't work.Evelyn: Exactly. So, I've worked with, like, organizations, like, 4000-plus people, I've worked for, like, small startups, consulted, and this is why I say, almost every single transformation, it fails the first time because somebody needs to be in control and track things and basically be really, really certain that people are doing it right. And as soon as it blows up in their face, that's when they realize they should actually take a step back. And so, even for building out a platform, you know, doing Platform-as-a-Product, I always reiterate that you have to really be willing to just invest upfront, and not get very much back. Because you have to figure out the whole user journey, and what you're actually building, before you actually build it.Corey: I really want to thank you for taking the time to speak with me today. If people want to learn more, where's the best place for them to find you?Evelyn: So, I used to be on Twitter, but I've actually got off there after it kind of turned a bit toxic and crazy.Corey: Feels like that was years ago, but that's beside the point.Evelyn: Yeah, precisely. So, I would even just say because this feels like a corporate show, but find me on LinkedIn of all places because I will be sharing whatever I find on there, you know? So, just look me up on my name, Evelyn Osman, and give me a follow, and I'll probably be screaming into the cloud like you are.Corey: And we will, of course, put links to that in the show notes. Thank you so much for taking the time to speak with me. I appreciate it.Evelyn: Thank you, Corey.Corey: Evelyn Osman, engineering manager at AutoScout24. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, and I will read it once I finish building an internal platform to normalize all of those platforms together into one.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business, and we get to the point. Visit duckbillgroup.com to get started.

Begin your recovery journey in Freehold, NJ today with the substance abuse IOPs offered by Relevance Recovery (866-245-1497)! The drug rehab center uses an individualized approach to help you heal much faster and for longer. Learn more at https://relevancerecovery.com/ Relevance Behavioral Health City: Freehold Township Address: 61 W Main Street Website https://relevancerecovery.com/ Phone +1 866 245 1497 Email info@hucenters.com

Amir Szekely, Owner at CloudSnorkel, joins Corey on Screaming in the Cloud to discuss how he got his start in the early days of cloud and his solo project, CloudSnorkel. Throughout this conversation, Corey and Amir discuss the importance of being pragmatic when moving to the cloud, and the different approaches they see in developers from the early days of cloud to now. Amir shares what motivates him to develop open-source projects, and why he finds fulfillment in fixing bugs and operating CloudSnorkel as a one-man show. About AmirAmir Szekely is a cloud consultant specializing in deployment automation, AWS CDK, CloudFormation, and CI/CD. His background includes security, virtualization, and Windows development. Amir enjoys creating open-source projects like cdk-github-runners, cdk-turbo-layers, and NSIS.Links Referenced: CloudSnorkel: https://cloudsnorkel.com/ lasttootinaws.com: https://lasttootinaws.com camelcamelcamel.com: https://camelcamelcamel.com github.com/cloudsnorkel: https://github.com/cloudsnorkel Personal website: https://kichik.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn, and this is an episode that I have been angling for for longer than you might imagine. My guest today is Amir Szekely, who's the owner at CloudSnorkel. Amir, thank you for joining me.Amir: Thanks for having me, Corey. I love being here.Corey: So, I've been using one of your open-source projects for an embarrassingly long amount of time, and for the longest time, I make the critical mistake of referring to the project itself as CloudSnorkel because that's the word that shows up in the GitHub project that I can actually see that jumps out at me. The actual name of the project within your org is cdk-github-runners if I'm not mistaken.Amir: That's real original, right?Corey: Exactly. It's like, “Oh, good, I'll just mention that, and suddenly everyone will know what I'm talking about.” But ignoring the problems of naming things well, which is a pain that everyone at AWS or who uses it knows far too well, the product is basically magic. Before I wind up basically embarrassing myself by doing a poor job of explaining what it is, how do you think about it?Amir: Well, I mean, it's a pretty simple project, which I think what makes it great as well. It creates GitHub runners with CDK. That's about it. It's in the name, and it just does that. And I really tried to make it as simple as possible and kind of learn from other projects that I've seen that are similar, and basically learn from my pain points in them.I think the reason I started is because I actually deployed CDK runners—sorry, GitHub runners—for one company, and I ended up using the Kubernetes one, right? So, GitHub in themselves, they have two projects they recommend—and not to nudge GitHub, please recommend my project one day as well—they have the Kubernetes controller and they have the Terraform deployer. And the specific client that I worked for, they wanted to use Kubernetes. And I tried to deploy it, and, Corey, I swear, I worked three days; three days to deploy the thing, which was crazy to me. And every single step of the way, I had to go and read some documentation, figure out what I did wrong, and apparently the order the documentation was was incorrect.And I had to—I even opened tickets, and they—you know, they were rightfully like, “It's open-source project. Please contribute and fix the documentation for us.” At that point, I said, “Nah.” [laugh]. Let me create something better with CDK and I decided just to have the simplest setup possible.So usually, right, what you end up doing in these projects, you have to set up either secrets or SSM parameters, and you have to prepare the ground and you have to get your GitHub token and all those things. And that's just annoying. So, I decided to create a—Corey: So much busy work.Amir: Yes, yeah, so much busy work and so much boilerplate and so much figuring out the right way and the right order, and just annoying. So, I decided to create a setup page. I thought, “What if you can actually install it just like you install any app on GitHub,” which is the way it's supposed to be right? So, when you install cdk-github-runners—CloudSnorkel—you get an HTML page and you just click a few buttons and you tell it where to install it and it just installs it for you. And it sets the secrets and everything. And if you want to change the secret, you don't have to redeploy. You can just change the secret, right? You have to roll the token over or whatever. So, it's much, much easier to install.Corey: And I feel like I discovered this project through one of the more surreal approaches—and I had cause to revisit it a few weeks ago when I was redoing my talk for the CDK Community Day, which has since happened and people liked the talk—and I mentioned what CloudSnorkel had been doing and how I was using the runners accordingly. So, that was what I accidentally caused me to pop back up with, “Hey, I've got some issues here.” But we'll get to that. Because once upon a time, I built a Twitter client for creating threads because shitposting is my love language, I would sit and create Twitter threads in the middle of live keynote talks. Threading in the native client was always terrible, and I wanted to build something that would help me do that. So, I did.And it was up for a while. It's not anymore because I'm not paying $42,000 a month in API costs to some jackass, but it still exists in the form of lasttootinaws.com if you want to create threads on Mastodon. But after I put this out, some people complained that it was slow.To which my response was, “What do you mean? It's super fast for me in San Francisco talking to it hosted in Oregon.” But on every round trip from halfway around the world, it became a problem. So, I got it into my head that since this thing was fully stateless, other than a Lambda function being fronted via an API Gateway, that I should deploy it to every region. It didn't quite fit into a Cloudflare Worker or into one of the Edge Lambda functions that AWS has given up on, but okay, how do I deploy something to every region?And the answer is, with great difficulty because it's clear that no one was ever imagining with all those regions that anyone would use all of them. It's imagined that most customers use two or three, but customers are different, so which two or three is going to be widely varied. So, anything halfway sensible about doing deployments like this didn't work out. Again, because this thing was also a Lambda function and an API Gateway, it was dirt cheap, so I didn't really want to start spending stupid amounts of money doing deployment infrastructure and the rest.So okay, how do I do this? Well, GitHub Actions is awesome. It is basically what all of AWS's code offerings wish that they were. CodeBuild is sad and this was kind of great. The problem is, once you're out of the free tier, and if you're a bad developer where you do a deploy on every iteration, suddenly it starts costing for what I was doing in every region, something like a quarter of per deploy, which adds up when you're really, really bad at programming.Amir: [laugh].Corey: So, their matrix jobs are awesome, but I wanted to do some self-hosted runners. How do I do that? And I want to keep it cheap, so how do I do a self-hosted runner inside of a Lambda function? Which led me directly to you. And it was nothing short of astonishing. This was a few years ago. I seem to recall that it used to be a bit less well-architected in terms of its elegance. Did it always use step functions, for example, to wind up orchestrating these things?Amir: Yeah, so I do remember that day. We met pretty much… basically as a joke because the Lambda Runner was a joke that I did, and I posted on Twitter, and I was half-proud of my joke that starts in ten seconds, right? But yeah, no, the—I think it always used functions. I've been kind of in love with the functions for the past two years. They just—they're nice.Corey: Oh, they're magic, and AWS is so bad at telling their story. Both of those things are true.Amir: Yeah. And the API is not amazing. But like, when you get it working—and you know, you have to spend some time to get it working—it's really nice because then you have nothing to manage, ever. And they can call APIs directly now, so you don't have to even create Lambdas. It's pretty cool.Corey: And what I loved is you wind up deploying this thing to whatever account you want it to live within. What is it, the OIDC? I always get those letters in the wrong direction. OIDC, I think, is correct.Amir: I think it's OIDC, yeah.Corey: Yeah, and it winds up doing this through a secure method as opposed to just okay, now anyone with access to the project can deploy into your account, which is not ideal. And it just works. It spins up a whole bunch of these Lambda functions that are using a Docker image as the deployment environment. And yeah, all right, if effectively my CDK deploy—which is what it's doing inside of this thing—doesn't complete within 15 minutes, then it's not going to and the thing is going to break out. We've solved the halting problem. After 15 minutes, the loop will terminate. The end.But that's never been a problem, even with getting ACM certificates spun up. It completes well within that time limit. And its cost to me is effectively nothing. With one key exception: that you made the choice to use Secrets Manager to wind up storing a lot of the things it cares about instead of Parameter Store, so I think you wind up costing me—I think there's two of those different secrets, so that's 80 cents a month. Which I will be demanding in blood one of these days if I ever catch you at re:Invent.Amir: I'll buy you beer [laugh].Corey: There we go. That'll count. That'll buy, like, several months of that. That works—at re:Invent, no. The beers there are, like, $18, so that'll cover me for years. We're set.Amir: We'll split it [laugh].Corey: Exactly. Problem solved. But I like the elegance of it, I like how clever it is, and I want to be very clear, though, it's not just for shitposting. Because it's very configurable where, yes, you can use Lambda functions, you can use Spot Instances, you can use CodeBuild containers, you can use Fargate containers, you can use EC2 instances, and it just automatically orchestrates and adds these self-hosted runners to your account, and every build gets a pristine environment as a result. That is no small thing.Amir: Oh, and I love making things configurable. People really appreciate it I feel, you know, and gives people kind of a sense of power. But as long as you make that configuration simple enough, right, or at least the defaults good defaults, right, then, even with that power, people still don't shoot themselves in the foot and it still works really well. By the way, we just added ECS recently, which people really were asking for because it gives you the, kind of, easy option to have the runner—well, not the runner but at least the runner infrastructure staying up, right? So, you can have auto-scaling group backing ECS and then the runner can start up a lot faster. It was actually very important to other people because Lambda, as fast that it is, it's limited, and Fargate, for whatever reason, still to this day, takes a minute to start up.Corey: Yeah. What's wild to me about this is, start to finish, I hit a deploy to the main branch and it sparks the thing up, runs the deploy. Deploy itself takes a little over two minutes. And every time I do this, within three minutes of me pushing to commit, the deploy is done globally. It is lightning fast.And I know it's easy to lose yourself in the idea of this being a giant shitpost, where, oh, who's going to do deployment jobs in Lambda functions? Well, kind of a lot of us for a variety of reasons, some of which might be better than others. In my case, it was just because I was cheap, but the massive parallelization ability to do 20 simultaneous deploys in a matrix configuration that doesn't wind up smacking into rate limits everywhere, that was kind of great.Amir: Yeah, we have seen people use Lambda a lot. It's mostly for, yeah, like you said, small jobs. And the environment that they give you, it's kind of limited, so you can't actually install packages, right? There is no sudo, and you can't actually install anything unless it's in your temp directory. But still, like, just being able to run a lot of little jobs, it's really great. Yeah.Corey: And you can also make sure that there's a Docker image ready to go with the stuff that you need, just by configuring how the build works in the CDK. I will admit, I did have a couple of bug reports for you. One was kind of useful, where it was not at all clear how to do this on top of a Graviton-based Lambda function—because yeah, that was back when not everything really supported ARM architectures super well—and a couple of other times when the documentation was fairly ambiguous from my perspective, where it wasn't at all clear, what was I doing? I spent four hours trying to beat my way through it, I give up, filed an issue, went to get a cup of coffee, came back, and the answer was sitting there waiting for me because I'm not convinced you sleep.Amir: Well, I am a vampire. My last name is from the Transylvania area [laugh]. So—Corey: Excellent. Excellent.Amir: By the way, not the first time people tell me that. But anyway [laugh].Corey: There's something to be said for getting immediate responsiveness because one of the reasons I'm always so loath to go and do a support ticket anywhere is this is going to take weeks. And then someone's going to come back with a, “I don't get it.” And try and, like, read the support portfolio to you. No, you went right into yeah, it's this. Fix it and your problem goes away. And sure enough, it did.Amir: The escalation process that some companies put you through is very frustrating. I mean, lucky for you, CloudSnorkel is a one-man show and this man loves solving bugs. So [laugh].Corey: Yeah. Do you know of anyone using it for anything that isn't ridiculous and trivial like what I'm using it for?Amir: Yeah, I have to think whether or not I can… I mean, so—okay. We have a bunch of dedicated users, right, the GitHub repo, that keep posting bugs and keep posting even patches, right, so you can tell that they're using it. I even have one sponsor, one recurring sponsor on GitHub that uses it.Corey: It's always nice when people thank you via money.Amir: Yeah. Yeah, it is very validating. I think [BLEEP] is using it, but I also don't think I can actually say it because I got it from the GitHub.Corey: It's always fun. That's the beautiful part about open-source. You don't know who's using this. You see what other things people are working on, and you never know, is one of their—is this someone's side project, is it a skunkworks thing, or God forbid, is this inside of every car going forward and no one bothered to tell me about that. That is the magic and mystery of open-source. And you've been doing open-source for longer than I have and I thought I was old. You were originally named in some of the WinAMP credits, for God's sake, that media player that really whipped the llama's ass.Amir: Oh, yeah, I started real early. I started about when I was 15, I think. I started off with Pascal or something or even Perl, and then I decided I have to learn C and I have to learn Windows API. I don't know what possessed me to do that. Win32 API is… unique [laugh].But once I created those applications for myself, right, I think there was—oh my God, do you know the—what is it called, Sherlock in macOS, right? And these days, for PowerToys, there is the equivalent of it called, I don't know, whatever that—PowerBar? That's exactly—that was that. That's a project I created as a kid. I wanted something where I can go to the Run menu of Windows when you hit Winkey R, and you can just type something and it will start it up, right?I didn't want to go to the Start menu and browse and click things. I wanted to do everything with the keyboard. So, I created something called Blazerun [laugh], which [laugh] helped you really easily create shortcuts that went into your path, right, the Windows path, so you can really easily start them from Winkey R. I don't think that anyone besides me used it, but anyway, that thing needed an installer, right? Because Windows, you got to install things. So, I ended up—Corey: Yeah, these days on Mac OS, I use Alfred for that which is kind of long in the tooth, but there's a launch bar and a bunch of other stuff for it. What I love is that if I—I can double-tap the command key and that just pops up whatever I need it to and tell the computer what to do. It feels like there's an AI play in there somewhere if people can figure out how to spend ten minutes on building AI that does something other than lets them fire their customer service staff.Amir: Oh, my God. Please don't fire customer service staff. AI is so bad.Corey: Yeah, when I reach out to talk to a human, I really needed a human.Amir: Yes. Like, I'm not calling you because I want to talk to a robot. I know there's a website. Leave me alone, just give me a person.Corey: Yeah. Like, you already failed to solve my problem on your website. It's person time.Amir: Exactly. Oh, my God. Anyway [laugh]. So, I had to create an installer, right, and I found it was called NSIS. So, it was a Nullsoft “SuperPiMP” installation system. Or in the future, when Justin, the guy who created Winamp and NSIS, tried to tone down a little bit, Nullsoft Scriptable Installation System. And SuperPiMP is—this is such useless history for you, right, but SuperPiMP is the next generation of PiMP which is Plug-in Mini Packager [laugh].Corey: I remember so many of the—like, these days, no one would ever name any project like that, just because it's so off-putting to people with sensibilities, but back then that was half the stuff that came out. “Oh, you don't like how this thing I built for free in the wee hours when I wasn't working at my fast food job wound up—you know, like, how I chose to name it, well, that's okay. Don't use it. Go build your own. Oh, what you're using it anyway. That's what I thought.”Amir: Yeah. The source code was filled with profanity, too. And like, I didn't care, I really did not care, but some people would complain and open bug reports and patches. And my policy was kind of like, okay if you're complaining, I'm just going to ignore you. If you're opening a patch, fine, I'm going to accept that you're—you guys want to create something that's sensible for everybody, sure.I mean, it's just source code, you know? Whatever. So yeah, I started working on that NSIS. I used it for myself and I joined the forums—and this kind of answers to your question of why I respond to things so fast, just because of the fun—I did the same when I was 15, right? I started going on the forums, you remember forums? You remember that [laugh]?Corey: Oh, yeah, back before they all became terrible and monetized.Amir: Oh, yeah. So, you know, people were using NSIS, too, and they had requests, right? They wanted. Back in the day—what was it—there was only support for 16-bit colors for the icon, so they want 32-bit colors and big colors—32—big icon, sorry, 32 pixels by 32 pixels. Remember, 32 pixels?Corey: Oh, yes. Not well, and not happily, but I remember it.Amir: Yeah. So, I started just, you know, giving people—working on that open-source and creating up a fork. It wasn't even called ‘fork' back then, but yeah, I created, like, a little fork of myself and I started adding all these features. And people were really happy, and kind of created, like, this happy cycle for myself: when people were happy, I was happy coding. And then people were happy by what I was coding. And then they were asking for more and they were getting happier, the more I responded.So, it was kind of like a serotonin cycle that made me happy and made everybody happy. So, it's like a win, win, win, win, win. And that's how I started with open-source. And eventually… NSIS—again, that installation system—got so big, like, my fork got so big, and Justin, the guy who works on WinAMP and NSIS, he had other things to deal with. You know, there's a whole history there with AOL. I'm sure you've heard all the funny stories.Corey: Oh, yes. In fact, one thing that—you want to talk about weird collisions of things crossing, one of the things I picked up from your bio when you finally got tired of telling me no and agreed to be on the show was that you're also one of the team who works on camelcamelcamel.com. And I keep forgetting that's one of those things that most people have no idea exists. But it's very simple: all it does is it tracks Amazon products that you tell it to and alerts you when there's a price drop on the thing that you're looking at.It's something that is useful. I try and use it for things of substance or hobbies because I feel really pathetic when I'm like, get excited emails about a price drop in toilet paper. But you know, it's very handy just to keep an idea for price history, where okay, am I actually being ripped off? Oh, they claim it's their big Amazon Deals day and this is 40% off. Let's see what camelcamelcamel has to say.Oh, surprise. They just jacked the price right beforehand and now knocked 40% off. Genius. I love that. It always felt like something that was going to be blown off the radar by Amazon being displeased, but I discovered you folks in 2010 and here you are now, 13 years later, still here. I will say the website looks a lot better now.Amir: [laugh]. That's a recent change. I actually joined camel, maybe two or three years ago. I wasn't there from the beginning. But I knew the guy who created it—again, as you were saying—from the Winamp days, right? So, we were both working in the free—well, it wasn't freenode. It was not freenode. It was a separate IRC server that, again, Justin created for himself. It was called landoleet.Corey: Mmm. I never encountered that one.Amir: Yeah, no, it was pretty private. The only people that cared about WinAMP and NSIS ended up joining there. But it was a lot of fun. I met a lot of friends there. And yeah, I met Daniel Green there as well, and he's the guy that created, along with some other people in there that I think want to remain anonymous so I'm not going to mention, but they also were on the camel project.And yeah, I was kind of doing my poor version of shitposting on Twitter about AWS, kind of starting to get some traction and maybe some clients and talk about AWS so people can approach me, and Daniel approached me out of the blue and he was like, “Do you just post about AWS on Twitter or do you also do some AWS work?” I was like, “I do some AWS work.”Corey: Yes, as do all of us. It's one of those, well crap, we're getting called out now. “Do you actually know how any of this stuff works?” Like, “Much to my everlasting shame, yes. Why are you asking?”Amir: Oh, my God, no, I cannot fix your printer. Leave me alone.Corey: Mm-hm.Amir: I don't want to fix your Lambdas. No, but I do actually want to fix your Lambdas. And so, [laugh] he approached me and he asked if I can help them move camelcamelcamel from their data center to AWS. So, that was a nice big project. So, we moved, actually, all of camelcamelcamel into AWS. And this is how I found myself not only in the Winamp credits, but also in the camelcamelcamel credits page, which has a great picture of me riding a camel.Corey: Excellent. But one of the things I've always found has been that when you take an application that has been pre-existing for a while in a data center and then move it into the cloud, you suddenly have to care about things that no one sensible pays any attention to in the land of the data center. Because it's like, “What do I care about how much data passes between my application server and the database? Wait, what do you mean that in this configuration, that's a chargeable data transfer? Oh, dear Lord.” And things that you've never had to think about optimizing are suddenly things are very much optimizing.Because let's face it, when it comes to putting things in racks and then running servers, you aren't auto-scaling those things, so everything tends to be running over-provisioned, for very good reasons. It's an interesting education. Anything you picked out from that process that you think it'd be useful for folks to bear in mind if they're staring down the barrel of the same thing?Amir: Yeah, for sure. I think… in general, right, not just here. But in general, you always want to be pragmatic, right? You don't want to take steps are huge, right? So, the thing we did was not necessarily rewrite everything and change everything to AWS and move everything to Lambda and move everything to Docker.Basically, we did a mini lift-and-shift, but not exactly lift-and-shift, right? We didn't take it as is. We moved to RDS, we moved to ElastiCache, right, we obviously made use of security groups and session connect and we dropped SSH Sage and we improved the security a lot and we locked everything down, all the permissions and all that kind of stuff, right? But like you said, there's stuff that you start having to pay attention to. In our case, it was less the data transfer because we have a pretty good CDN. There was more of IOPS. So—and IOPS, specifically for a database.We had a huge database with about one terabyte of data and a lot of it is that price history that you see, right? So, all those nice little graphs that we create in—what do you call them, charts—that we create in camelcamelcamel off the price history. There's a lot of data behind that. And what we always want to do is actually remove that from MySQL, which has been kind of struggling with it even before the move to AWS, but after the move to AWS, where everything was no longer over-provisioned and we couldn't just buy a few more NVMes on Amazon for 100 bucks when they were on sale—back when we had to pay Amazon—Corey: And you know, when they're on sale. That's the best part.Amir: And we know [laugh]. We get good prices on NVMe. But yeah, on Amazon—on AWS, sorry—you have to pay for io1 or something, and that adds up real quick, as you were saying. So, part of that move was also to move to something that was a little better for that data structure. And we actually removed just that data, the price history, the price points from MySQL to DynamoDB, which was a pretty nice little project.Actually, I wrote about it in my blog. There is, kind of, lessons learned from moving one terabyte from MySQL to DynamoDB, and I think the biggest lesson was about hidden price of storage in DynamoDB. But before that, I want to talk about what you asked, which was the way that other people should make that move, right? So again, be pragmatic, right? If you Google, “How do I move stuff from DynamoDB to MySQL,” everybody's always talking about their cool project using Lambda and how you throttle Lambda and how you get throttled from DynamoDB and how you set it up with an SQS, and this and that. You don't need all that.Just fire up an EC2 instance, write some quick code to do it. I used, I think it was Go with some limiter code from Uber, and that was it. And you don't need all those Lambdas and SQS and the complication. That thing was a one-time thing anyway, so it doesn't need to be super… super-duper serverless, you know?Corey: That is almost always the way that it tends to play out. You encounter these weird little things along the way. And you see so many things that are tied to this is how architecture absolutely must be done. And oh you're not a real serverless person if you don't have everything running in Lambda and the rest. There are times where yeah, spin up an EC2 box, write some relatively inefficient code in ten minutes and just do the thing, and then turn it off when you're done. Problem solved. But there's such an aversion to that. It's nice to encounter people who are pragmatists more than they are zealots.Amir: I mostly learned that lesson. And both Daniel Green and me learned that lesson from the Winamp days. Because we both have written plugins for Winamp and we've been around that area and you can… if you took one of those non-pragmatist people, right, and you had them review the Winamp code right now—or even before—they would have a million things to say. That code was—and NSIS, too, by the way—and it was so optimized. It was so not necessarily readable, right? But it worked and it worked amazing. And Justin would—if you think I respond quickly, right, Justin Frankel, the guy who wrote Winamp, he would release versions of NSIS and of Winamp, like, four versions a day, right? That was before [laugh] you had CI/CD systems and GitHub and stuff. That was just CVS. You remember CVS [laugh]?Corey: Oh, I've done multiple CVS migrations. One to Git and a couple to Subversion.Amir: Oh yeah, Subversion. Yep. Done ‘em all. CVS to Subversion to Git. Yep. Yep. That was fun.Corey: And these days, everyone's using Git because it—we're beginning to have a monoculture.Amir: Yeah, yeah. I mean, but Git is nicer than Subversion, for me, at least. I've had more fun with it.Corey: Talk about damning with faint praise.Amir: Faint?Corey: Yeah, anything's better than Subversion, let's be honest here.Amir: Oh [laugh].Corey: I mean, realistically, copying a bunch of files and directories to a.bak folder is better than Subversion.Amir: Well—Corey: At least these days. But back then it was great.Amir: Yeah, I mean, the only thing you had, right [laugh]?Corey: [laugh].Amir: Anyway, achieving great things with not necessarily the right tools, but just sheer power of will, that's what I took from the Winamp days. Just the entire world used Winamp. And by the way, the NSIS project that I was working on, right, I always used to joke that every computer in the world ran my code, every Windows computer in the world when my code, just because—Corey: Yes.Amir: So, many different companies use NSIS. And none of them cared that the code was not very readable, to put it mildly.Corey: So, many companies founder on those shores where they lose sight of the fact that I can point to basically no companies that died because their code was terrible, yeah, had an awful lot that died with great-looking code, but they didn't nail the business problem.Amir: Yeah. I would be lying if I said that I nailed exactly the business problem at NSIS because the most of the time I would spend there and actually shrinking the stub, right, there was appended to your installer data, right? So, there's a little stub that came—the executable, basically, that came before your data that was extracted. I spent, I want to say, years of my life [laugh] just shrinking it down by bytes—by literal bytes—just so it stays under 34, 35 kilobytes. It was kind of a—it was a challenge and something that people appreciated, but not necessarily the thing that people appreciate the most. I think the features—Corey: Well, no I have to do the same thing to make sure something fits into a Lambda deployment package. The scale changes, the problem changes, but somehow everything sort of rhymes with history.Amir: Oh, yeah. I hope you don't have to disassemble code to do that, though because that's uh… I mean, it was fun. It was just a lot.Corey: I have to ask, how much work went into building your cdk-github-runners as far as getting it to a point of just working out the door? Because I look at that and it feels like there's—like, the early versions, yeah, there wasn't a whole bunch of code tied to it, but geez, the iterative, “How exactly does this ridiculous step functions API work or whatnot,” feels like I'm looking at weeks of frustration. At least it would have been for me.Amir: Yeah, yeah. I mean, it wasn't, like, a day or two. It was definitely not—but it was not years, either. I've been working on it I think about a year now. Don't quote me on that. But I've put a lot of time into it. So, you know, like you said, the skeleton code is pretty simple: it's a step function, which as we said, takes a long time to get right. The functions, they are really nice, but their definition language is not very straightforward. But beyond that, right, once that part worked, it worked. Then came all the bug reports and all the little corner cases, right? We—Corey: Hell is other people's use cases. Always is. But that's honestly better than a lot of folks wind up experiencing where they'll put an open-source project up and no one ever knows. So, getting users is often one of the biggest barriers to a lot of this stuff. I've found countless hidden gems lurking around on GitHub with a very particular search for something that no one had ever looked at before, as best I can tell.Amir: Yeah.Corey: Open-source is a tricky thing. There needs to be marketing brought into it, there needs to be storytelling around it, and has to actually—dare I say—solve a problem someone has.Amir: I mean, I have many open-source projects like that, that I find super useful, I created for myself, but no one knows. I think cdk-github-runners, I'm pretty sure people know about it only because you talked about it on Screaming in the Cloud or your newsletter. And by the way, thank you for telling me that you talked about it last week in the conference because now we know why there was a spike [laugh] all of a sudden. People Googled it.Corey: Yeah. I put links to it as well, but it's the, yeah, I use this a lot and it's great. I gave a crappy explanation on how it works, but that's the trick I've found between conference talks and, dare I say, podcast episodes, you gives people a glimpse and a hook and tell them where to go to learn more. Otherwise, you're trying to explain every nuance and every intricacy in 45 minutes. And you can't do that effectively in almost every case. All you're going to do is drive people away. Make it sound exciting, get them to see the value in it, and then let them go.Amir: You have to explain the market for it, right? That's it.Corey: Precisely.Amir: And I got to say, I somewhat disagree with your—or I have a different view when you say that, you know, open-source projects needs marketing and all those things. It depends on what open-source is for you, right? I don't create open-source projects so they are successful, right? It's obviously always nicer when they're successful, but—and I do get that cycle of happiness that, like I was saying, people create bugs and I have to fix them and stuff, right? But not every open-source project needs to be a success. Sometimes it's just fun.Corey: No. When I talk about marketing, I'm talking about exactly what we're doing here. I'm not talking take out an AdWords campaign or something horrifying like that. It's you build something that solved the problem for someone. The big problem that worries me about these things is how do you not lose sleep at night about the fact that solve someone's problem and they don't know that it exists?Because that drives me nuts. I've lost count of the number of times I've been beating my head against a wall and asked someone like, “How would you handle this?” Like, “Oh, well, what's wrong with this project?” “What do you mean?” “Well, this project seems to do exactly what you want it to do.” And no one has it all stuffed in their head. But yeah, then it seems like open-source becomes a little more corporatized and it becomes a lead gen tool for people to wind up selling their SaaS services or managed offerings or the rest.Amir: Yeah.Corey: And that feels like the increasing corporatization of open-source that I'm not a huge fan of.Amir: Yeah. I mean, I'm not going to lie, right? Like, part of why I created this—or I don't know if it was part of it, but like, I had a dream that, you know, I'm going to get, oh, tons of GitHub sponsors, and everybody's going to use it and I can retire on an island and just make money out of this, right? Like, that's always a dream, right? But it's a dream, you know?And I think bottom line open-source is… just a tool, and some people use it for, like you were saying, driving sales into their SaaS, some people, like, may use it just for fun, and some people use it for other things. Or some people use it for politics, even, right? There's a lot of politics around open-source.I got to tell you a story. Back in the NSIS days, right—talking about politics—so this is not even about politics of open-source. People made NSIS a battleground for their politics. We would have translations, right? People could upload their translations. And I, you know, or other people that worked on NSIS, right, we don't speak every language of the world, so there's only so much we can do about figuring out if it's a real translation, if it's good or not.Back in the day, Google Translate didn't exist. Like, these days, we check Google Translate, we kind of ask a few questions to make sure they make sense. But back in the day, we did the best that we could. At some point, we got a patch for Catalan language, I'm probably mispronouncing it—but the separatist people in Spain, I think, and I didn't know anything about that. I was a young kid and… I just didn't know.And I just included it, you know? Someone submitted a patch, they worked hard, they wanted to be part of the open-source project. Why not? Sure I included it. And then a few weeks later, someone from Spain wanted to change Catalan into Spanish to make sure that doesn't exist for whatever reason.And then they just started fighting with each other and started making demands of me. Like, you have to do this, you have to do that, you have to delete that, you have to change the name. And I was just so baffled by why would someone fight so much over a translation of an open-source project. Like, these days, I kind of get what they were getting at, right?Corey: But they were so bad at telling that story that it was just like, so basically, screw, “You for helping,” is how it comes across.Amir: Yeah, screw you for helping. You're a pawn now. Just—you're a pawn unwittingly. Just do what I say and help me in my political cause. I ended up just telling both of them if you guys can agree on anything, I'm just going to remove both translations. And that's what I ended up doing. I just removed both translations. And then a few months later—because we had a release every month basically, I just added both of them back and I've never heard from them again. So sort of problem solved. Peace the Middle East? I don't know.Corey: It's kind of wild just to see how often that sort of thing tends to happen. It's a, I don't necessarily understand why folks are so opposed to other people trying to help. I think they feel like there's this loss of control as things are slipping through their fingers, but it's a really unwelcoming approach. One of the things that got me deep into the open-source ecosystem surprisingly late in my development was when I started pitching in on the SaltStack project right after it was founded, where suddenly everything I threw their way was merged, and then Tom Hatch, the guy who founded the project, would immediately fix all the bugs and stuff I put in and then push something else immediately thereafter. But it was such a welcoming thing.Instead of nitpicking me to death in the pull request, it just got merged in and then silently fixed. And I thought that was a classy way to do it. Of course, it doesn't scale and of course, it causes other problems, but I envy the simplicity of those days and just the ethos behind that.Amir: That's something I've learned the last few years, I would say. Back in the NSIS day, I was not like that. I nitpicked. I nitpicked a lot. And I can guess why, but it just—you create a patch—in my mind, right, like you create a patch, you fix it, right?But these days I get, I've been on the other side as well, right? Like I created patches for open-source projects and I've seen them just wither away and die, and then five years later, someone's like, “Oh, can you fix this line to have one instead of two, and then I'll merge it.” I'm like, “I don't care anymore. It was five years ago. I don't work there anymore. I don't need it. If you want it, do it.”So, I get it these days. And these days, if someone creates a patch—just yesterday, someone created a patch to format cdk-github-runners in VS Code. And they did it just, like, a little bit wrong. So, I just fixed it for them and I approved it and pushed it. You know, it's much better. You don't need to bug people for most of it.Corey: You didn't yell at them for having the temerity to contribute?Amir: My voice is so raw because I've been yelling for five days at them, yeah.Corey: Exactly, exactly. I really want to thank you for taking the time to chat with me about how all this stuff came to be and your own path. If people want to learn more, where's the best place for them to find you?Amir: So, I really appreciate you having me and driving all this traffic to my projects. If people want to learn more, they can always go to cloudsnorkel.com; it has all the projects. github.com/cloudsnorkel has a few more. And then my private blog is kichik.com. So, K-I-C-H-I-K dot com. I don't post there as much as I should, but it has some interesting AWS projects from the past few years that I've done.Corey: And we will, of course, put links to all of that in the show notes. Thank you so much for taking the time. I really appreciate it.Amir: Thank you, Corey. It was really nice meeting you.Corey: Amir Szekely, owner of CloudSnorkel. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an insulting comment. Heck, put it on all of the podcast platforms with a step function state machine that you somehow can't quite figure out how the API works.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

In episode 166 of our SAP on Azure video podcast we go deep on Premium v2 storage with Peter Kalan and Anbu Govindasamy. We look at the different storage options for SAP on Azure, show some performance comparisions, dynamic tiering and snappshotting. Then also talk about how to migrate to premium v2. Find all the links mentioned here: https://www.saponazurepodcast.de/episode166 Reach out to us for any feedback / questions: * Robert Boban: https://www.linkedin.com/in/rboban/ * Goran Condric: https://www.linkedin.com/in/gorancondric/ * Holger Bruchelt: https://www.linkedin.com/in/holger-bruchelt/ #Microsoft #SAP #Azure #SAPonAzure ## Summary created by AI * Features and benefits of premium SSD V2: Premium SSD V2 is a new version of Azure storage that offers sub-millisecond latency, customizable size and performance, and lower cost than premium SSD V1. It can support large database workloads such as SAP HANA, Oracle, and DB2. * How to use premium SSD V2 for SAP HANA: Premium SSD V2 does not require write accelerator for SAP HANA log, and can use different VM sizes than M series. It also allows changing the IOPS and throughput of the disks on the fly without downtime. It is certified by SAP and has best practice guidelines for optimal configuration. * Demo of premium SSD V2: The document shows a demo of how to create and configure premium SSD V2 disks, how to check the sector size and latency, how to increase the throughput dynamically, and how to take snapshots and create new disks from them. * Comparison of premium SSD V2 and V1: The document compares the price and performance of premium SSD V2 and V1, and shows that V2 is cheaper and faster than V1. It also explains how to optimize the disk size and number to get the best performance for the same price.

Welcome episode 227 of the Cloud Pod podcast - where the forecast is always cloudy! This week your hosts are Justin, Jonathan, Matthew and Ryan - and they're REALLY excited to tell you all about the 161 one things announced at Google Next. Literally, all the things. We're also saying farewell to EC2 Classic, Amazon SES, and Azure's Explicit Proxy - which probably isn't what you think it is.  Titles we almost went with this week:

Welcome episode 223 of The CloudPod Podcast! It's a full house - Justin, Matt, Ryan, and Jonathan are all here this week to discuss all the cloud news you need. This week, cost optimization is the big one, with a deep dive on the newest AWS blog. Additionally, we've got updates to BigQuery, Google's Health Service, managed services for Prometheus, and more. Titles we almost went with this week:

This week, host Anna Rose (https://twitter.com/annarrose) and Nico Mohnblatt (https://twitter.com/nico_mnbl) chat with Ron Rothblum (https://csaws.cs.technion.ac.il/~rothblum/), Professor of Computer Science at Technion. They explore information theory and ZK, diving into the weeds on multiple topics including error correcting codes, FRI, FFTs, Reed-Solomon encoding, Fiat-Shamir and more. Here's some additional links for this episode: Fiat-Shamir via List-Recoverable Codes (or: Parallel Repetition of GMW is not Zero-Knowledge) by Holmgren, Lombardi and Rothblum (https://eprint.iacr.org/2021/286.pdf) Proving as Fast as Computing: Succinct Arguments with Constant Prover Overhead by Ron-Zewi and Rothblum (https://eprint.iacr.org/2021/1673.pdf) Faster Sounder Succinct Arguments and IOPs by Holmgren and Rothblum (https://eprint.iacr.org/2022/994.pdf) The Random Oracle Methodology, Revisited by Canetti, Goldreich and Halevi (https://eprint.iacr.org/1998/011.pdf) Linear-Time Arguments with Sublinear Verification from Tensor Codes by Bootle, Chiesa and Groth (https://eprint.iacr.org/2020/1426.pdf) Testudo: Linear Time Prover SNARKs with Constant Size Proofs and Square Root Size Universal Setup by Campanelli, Gailly, Gennaro, Jovanovic, Mihali and Thaler (https://eprint.iacr.org/2023/961.pdf) Reed-Solomon Codes (https://www.cs.cmu.edu/~guyb/realworld/reedsolomon/reed_solomon_codes.html) Shannon's Source Coding Theorem (https://en.wikipedia.org/wiki/Shannon%27s_source_coding_theorem#References) Guy Rothblum Publications (https://guyrothblum.wordpress.com/about/publications/) Episode 274: SNARKs: A Trilogy with Ariel Gabizon (https://zeroknowledge.fm/274-2/) zkSummit 10 is happening in London on September 20, 2023! Apply to attend now -> https://9lcje6jbgv1.typeform.com/zkSummit10 Aleo (https://www.aleo.org/) is a new Layer-1 blockchain that achieves the programmability of Ethereum, the privacy of Zcash, and the scalability of a rollup. Interested in building private applications? Check out Aleo's programming language called Leo that enables non-cryptographers to harness the power of ZKPs to deploy decentralized exchanges, hidden information games, regulated stablecoins, and more. Visit http://developer.aleo.org (http://developer.aleo.org/). For questions, join their Discord at aleo.org/discord (http://aleo.org/discord). If you like what we do: * Find all our links here! @ZeroKnowledge | Linktree (https://linktr.ee/zeroknowledge) * Subscribe to our podcast newsletter (https://zeroknowledge.substack.com) * Follow us on Twitter @zeroknowledgefm (https://twitter.com/zeroknowledgefm) * Join us on Telegram (https://zeroknowledge.fm/telegram) * Catch us on YouTube (https://zeroknowledge.fm/)

Cast:Dr. Tara Egan - hostEllen Herbert, LCSW - guest expertIs an Intensive Outpatient Program (IOP) right for your teen? What exactly is an IOP?Our special guest expert this week helps us understand what Intensive Outpatient Programs look like for teens and shares some great information to educate parents about the process.Ellen Herbert is a Licensed Clinical Social Worker. She is currently the Clinical Director of the Intensive Outpatient Program at Queen City Counseling, located in Charlotte, NC. She received her Bachelors in Psychology from Vanderbilt University, her Masters in Social Work from Winthrop University and has been practicing as a clinical social worker ever since. Throughout her career, she has worked primarily with adolescents and has held positions in outpatient therapy, intensive in-home services and partial hospitalizationToday Ellen is here to discuss the ins and outs of IOPs, or intensive outpatient programs. What an IOP is? How is it different from outpatient therapy? How is it different from an inpatient program?What type of issues are addressed by IOP (substance use, eating disorders, etc)? How do these programs take into account developmental stage/age (for example, teenage vs adult)?There are many avenues for support and differing levels of care; how would a parent know what level of care is right for their teen?What benefits can a parent expect to see with an IOP Program for teens? Are there any risks or issues that parents should be mindful of?If you are a parent with a teen that needs support – where do you begin?To learn more about Ellen Herbert  and her services: https://qc-counseling.com For more information and resources -Dr. Tara Egan:Website -Dr. Tara Egan's child & adolescent therapy services books, webinars, public speaking opportunities, and coaching/consultation services, Go HERE.Facebook - learn more HERE.YouTube - learn more HERE.Instagram - learn more HERE.Edited by Christian Fox

Welcome to the newest episode of The Cloud Pod podcast! Justin, Ryan, Jonathan, Matthew are your hosts this week. Join us as we discuss all things cloud, AI, the upcoming Google AI Conference, AWS Console, and Duet AI for Google cloud.  Titles we almost went with this week:

Welcome to the newest episode of The Cloud Pod podcast! Justin, Ryan, Jonathan, Matthew and Peter are your hosts this week as we discuss all things cloud and AI,  Titles we almost went with this week: The Cloud Pod is better than Bob's Used Books The Cloud Pod sets up AWS notifications for all The Cloud Pod is non-differential about privacy in BigQuery The Cloud Pod finds Windows Bob The Cloud Pod starts preparing for its Azure Emergency today A big thanks to this week's sponsor: Foghorn Consulting, provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

Implementing parenting tools as preventative measures, even before things get out of hand, is absolutely invaluable when it comes to parenting a struggling teen. Changing the environment, being able to regulate your own emotions differently, being able to relate to your kid's emotions and reason with your kid differently, are all skills that can be learned. Today's guest, Laura Goldstein, has developed an incredibly valuable resource for parents to learn these tools which they can employ not only for their kids but also for themselves. With the development of TheraCourses, Laura made these skills available for parents from anywhere.In this episode on preventative measures, we discuss:The importance of implementing parenting strategies as preventative measures, before things get out of hand;Why it's so important to put what you learn into practice;Learning new parenting skills and tools is a muscle that can be trained;How TheraCourses helps parents learn new parenting skills and implement them right away;Modeling the behavior you wish to see;And more!If you'd like to connect, you can find me on Instagram (@bethhillmancoaching) or go to my website www.bethhillmancoaching.com. And if you're interested in working with me, you can learn more about my private coaching here or my group coaching here.And remember parents, the change begins with us.- - - - - - - - - -Ps. Are you getting great value out of this podcast? It would mean the world to me if you could leave a review on Apple Podcasts. This way, you will help me reach and help more parents of struggling teens develop healthy responses and boundaries instead of acting out of fear and anxiety. You can leave a review by clicking here, scrolling to the bottom, tapping to leave a star rating and then write your review. Thanks so much!And if you haven't already done so, make sure to subscribe to our show so you don't miss any of my future episodes!—--------More about Laura GoldsteinLaura Goldstein is a licensed clinical marriage and family therapist in Rockville MD. She is the founder and Executive Director of Montgomery County Counseling Center and the founder of TheraCourses, which she will talk more about in next week's episode! She has worked across multiple settings including in-home behavioral health services, IOPS for adolescent dual diagnosis treatment and young adults struggling to launch, and her private practice. You can learn more about Laura here or about TheraCourses by clicking here.

If you're familiar with my work or have listened to my podcast before, you know how I strive to help parents see their own part and take responsibility for it. Today I'm having such a valuable conversation around this with my guest, Laura Goldstein, LMFT. She shares some amazing metaphors that will really help shift the way we think and show us the role parents play in their family's dynamics and their child's behavior.Laura also provides us with a very clear explanation of different kinds of therapists out there to help you choose which one is best for your family.In this episode on doing your own work and finding the right therapist, we discuss: The difference between a psychologist and a psychiatrist;An explanation of the difference between an LMFT, LCSW, etc.;Great metaphors to show the role parents play in the family dynamics and their child's behavior;And more!If you'd like to connect, you can find me on Instagram (@bethhillmancoaching) or go to my website www.bethhillmancoaching.com. And if you're interested in working with me, you can learn more about my private coaching here or my group coaching here.And remember parents, the change begins with us.- - - - - - - - - -Ps. Are you getting great value out of this podcast? It would mean the world to me if you could leave a review on Apple Podcasts. This way, you will help me reach and help more parents of struggling teens develop healthy responses and boundaries instead of acting out of fear and anxiety. You can leave a review by clicking here, scrolling to the bottom, tapping to leave a star rating and then write your review. Thanks so much!And if you haven't already done so, make sure to subscribe to our show so you don't miss any of my future episodes!- - - - - - - - - - More about Laura GoldsteinLaura Goldstein is a licensed clinical marriage and family therapist in Rockville MD. She is the founder and Executive Director of Montgomery County Counseling Center and the founder of TheraCourses, which she will talk more about in next week's episode! She has worked across multiple settings including in-home behavioral health services, IOPS for adolescent dual diagnosis treatment and young adults struggling to launch, and her private practice. 

Todd Owens, Field Marketing Director, and Nishant Lodha, Director of Product Marketing – Emerging Technologies, discuss some of the metrics most commonly used to refer to storage performance, how the figures are derived from Marvell as well as other I/O device manufacturers, how performance figures drive decisions, and an in-depth discussion around IOPS.  Learn more: https://bit.ly/3STtLkH

Kelly Brown has been sober since 2008 after a 30 year drinking career.  Her journey towards recovery was not easy.  In and out of the rooms for 4 years, she struggled to let go of the perceived comfort of alcohol and the idea she would never be happy without it.  Multiple rehabs, detoxes, IOPs and counselors were not piercing through the wall of fear she had created over decades of addiction. That changed once she was out of options and given the gift of desperation.Kelly grew up in a suburb outside of New York City and lived in Chicago, Los Angeles, Istanbul, and NYC before settling down in the Scranton area in 2008.  Her professional experience includes executive recruiting, human resources, media, and advertising. Since 2013, Kelly has worked for a local non-profit.  Today, her career is beyond her wildest dreams, just like the rest of her life.  #recoveryispossible #recovery #substanceusedisorder #awakening #nyc #lalaland #chicago #istanbul #scranton  Support the show

Ask Kati Anything ep.131 | Your mental health podcast, with Kati Morton, LMFT This week Kati talks about how we can move forward if we were abusive to our siblings when we were younger. She also explains why we can fantasize about going missing or wanting to run away from our lives, and why it's common to have pretend conversations with ourselves and feel like they are real. Kati also shares the best time to journal, how to deal with a push pull urge in therapy, and how to move past denial. She also explains why we can feel the urge to invalidate our little t traumas, how to finally get to the root of our issues, and finally what we can do if it feels like nothing is helping. Audience questions: 1. There are a lot of questions asked by people who were abused by their siblings when they were younger, but what if I was the abuser? It's been over 15 years since but I was put in charge of watching my special needs little sister (only 16 months apart) a lot of the time and I used violence... 2. For years I've had this fantasy of “going missing,” or disappearing intentionally – just getting in my car, driving a thousand miles, leaving it in some parking lot and then just walking away. Over time I learned that this is not actually illegal, as long as you're an adult and you're not evading the... 3. This is kind of embarrassing to ask, but surely I'm not the only one who does this. Why do I pretend I'm having conversations with people who aren't really there? It's as if I'm actually having a back and forth conversation with another person, but in reality I guess I'm just talking to myself? 4. Why do I have such a strong push pull relationship with therapy? I have seen seven different therapists in the past two years and couldn't connect with any of them. It's like the first couple of sessions I want to tell them everything and then on the third and fourth sessions I don't want to... 5. Regarding journaling, is it more used to just write things down in the moment or is there value in going back and re-reading it at some point? I've been journaling pretty regularly for the past year and want to go back through and read it but I'm finding that I'm very hesitant to do so… 6. Is it possible to know you're in denial and yet you still don't want to believe the truth? I am trying to come to terms with being emotionally neglected by my parents but the part I'm struggling with is the acceptance that it happened. I know it sounds like a contradiction because I can name the... 7. How do I stop invalidating my little T traumas as you call them? I had a lot of things happen to me over my lifetime that I would consider smaller traumas if anything. For example, my father was quite abusive, but he left when I was still very young and we didn't see him often. My mother was/is an addict, but she still took care of us quite well... 8. How do I get to the root of my issues? I feel like I'm so caught up in running away by using maladaptive coping strategies (anorexia, over-exercise, suicidality etc) that I don't even know what I'm trying to cope with. I do know that there‘s more emotional pain when I reduce my disordered behaviors... 9. One of your answers prompted me to ask a question. I'm struggling with feeling like I've tried everything and feeling like I have no choice left but to end things. I have been inpatient multiple times, have done multiple IOPs/partials. I have tried so many meds... --- Send in a voice message: https://anchor.fm/askkatianything/message Support this podcast: https://anchor.fm/askkatianything/support

Intensive Ouptatient Programs are for more than just addiction treatment. Join Katie Walker of Revitalist as she sits down with Hope Reneau of The Middle Path to discuss Intensive Outpatient Programs (IOP). In this multi-part series, Revitalist and The Middle Path discuss IOPs and their integration in a comprehensive approach to helathcare. www.RevitalistClinic.com www.TheMiddlePath.life

There is (arguably) no faster mainstream storage available than Infinidat's just-launched InfiniBox SSA II array. Infinidat CMO Eric Herzog joins host Steve McDowell, principal analyst at Moor Insights & Strategy, to walk us through just how Infinidat is able to increase throughput and IOPs by more than 50% in the new array, while also ensuring a compelling level of data protection and cyber-resilience. The guys also talk about the continuing evolution of storage, with a deep-dive into AIOps and how new workloads (such as cloud-native) impact storage architecture. This is a great podcast for anyone interested in high-performance storage. This podcast is sponsored by Infinidat. Special Guest: Eric Herzog.

Google Biglake takes the feature of the week with the ability to federate data from multiple data lakes. On The Cloud Pod this week, the team discusses the most expensive way to run a VM (Oracle wins). Plus some exciting developments, an AWS OpenSearch 1.2 update with several new features, and Azure's having a party, so bring your own IP addresses (BYOIP). A big thanks to this week's sponsor, Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. This week's highlights

On The Cloud Pod this week, it's a brave new world for Ryan, who learns all kinds of things. Plus the Okta breach leads to customer outrage over not telling them for months, AWS announces its new Billing Conductor, and Google expands Contact Center AI for a reimagined customer experience.  A big thanks to this week's sponsor, Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. This week's highlights