Ep. 112 Cloud Powerhouse Unveiled How Managed Services Elevate Azure and AWS with Donavan Brady

Subscribe to the Next Level BizTech podcast, so you don’t miss an episode!
Amazon Music | Apple Podcasts | Listen on Spotify | Watch on YouTube

Today we’re joined by industry expert Donavan Brady of the Rapidscale/Logicworks family. Donavan is the Director of Solutions Architecture an heavily entrenched in the hyperscalers. He has a unique glimpse into many complex AWS & Azure environments. Not only does he get to see first-hand, where customers are struggling, he has a plethora of services to help manage all the complex products customers struggle to manage on their own. If your customer has significant spending on AWS or Azure, don’t miss this episode as we talk cloud, AI, AI, and more AI!

Welcome to the podcast designed to fuel your success in selling technology solutions. I’m your host, Josh LuprestoSVP of sales engineering at Telarus and this is Next Level BizTech Look at that, you can see Donovan super excited. Welcome everybody. We’re talking cloud. We’re talking managed services. And more importantly, we’re talking about how to elevate Azure and AWS for customers. So today on with us as mentioned Mr. Donovan Brady, Director of Solution Architecture from RapidScale. Welcome on my man. Yeah, thank you for having me. Happy to be here. Donovan, we’re gonna hype you up in just a little bit. But before that, I want people to get to know you. So start us off for anybody that doesn’t know you hasn’t listened to you before. Tell us about your background. How did you get into this space overall? Where did you start winding path? Anything exciting?

Yeah, okay. Good question. So I have been in this field for my entire career. I think it really started because I love video games. I love video games when I was a kid. And I was like, Oh, man, imagine if I could make these that would be so cool. And so I grew up taking apart things, fixing Xboxes, I actually started a business in high school, building computers with my friend. And then in college, I became a computer science major and engineer. I graduated as a software engineer at LogicWorks. And realized that while I liked software engineering, and I really liked the tech, I really liked to talk. So I transitioned from behind the scenes back end engineer into solutions architecture, and really found my niche there. I really derived joy from working with customers, helping them solve their business problems and their business objectives, and helping grow the team. So when I joined LogicWorks 10 years ago, we had 45 people total. Now we are over 500 people combined with rapid scale. So it’s really been an awesome journey to see the growth that LogicWorks and rapid scale collectively have achieved. Wow, love it. Well, man, let’s unpack this a little bit. So first of all, we’re glad that you got from behind the screen and got in front of the screen. So talk to us about, you know, in your role here as director of solution architecture, for anybody that doesn’t know what this LogicWorks acquisition means for rapid scale, fill us in on that at a high level, but then also what your role is. Yeah. So for those of you who don’t know who rapid scale is, rapid scale is a full services IT provider, right? We help simplify IT and unleash innovation. And what does that mean? That means that whether you need help with your end user computing, whether that need means that you need help with managing your infrastructure, or even progressing to the next level of public cloud, right, the future of technology, we have the solution for you, right? So we are that full spectrum services, migration, managed services partner.

LogicWorks has been around actually since 1993. But we had a few different paths throughout the years. Really, in 2012, we solidified our stance on we’re going to be a public cloud partner, right? And so we kind of stopped doing our private cloud stuff, we stopped doing any on prem work, and went full in on AWS. And over the years, we’ve started to grow that initiative. Now we do AWS, Azure and Google. And our primary goal is to help customers achieve their business objectives by migrating to the cloud, optimizing their resources, and improving their IT estate, so that ultimately, it can drive more efficiency and money for them, right? Historically, we focused on mission critical hyper compliant types of customers, right? LogicWorks is certified and audited for HIPAA, PCI, high trust, SOC 1, SOC 2, basically any kind of compliance regulation that you could think of, we have it. So we try to focus on how can customers achieve their business goals, while maintaining a performant environment, while also having security in mind from the very base level, right? And so with our combined services with RapidScale, under Cox Communications, we were able to reach whole new levels of the market that we never even considered, right? Small little LogicWorks, we’re about 200 people big, there’s no way that we could be as far reaching as with the growth and expansiveness of Cox, right? And of RapidScale, which RapidScale has already an amazing brand in the market. So it’s a really exciting time for all of us. Yeah, I love it. So I would say the channel of RapidScale has a tremendous brand in the channel, right, as you mentioned, and I would argue that the channel is pretty familiar with the Rapid Scale side of things, right, and knows who they are from a cloud perspective, at least. So let’s do product speed dating, I guess. So walk us through, you know, where LogicWorks comes into the picture, if I’m a partner, and I’m trying to go find the skew list of products that LogicWorks can offer me or help with. I don’t know that we have time to cover them all on this podcast. But let’s talk about as it relates to the title of this right, elevating, you know, hyperscale or stuff with managed services. Walk us through some of the products.

Yeah. So LogicWorks product set, I’d say breaks down into three different domains. The first would be professional services. The second would be managed services. And the third would be our platform, right. Platform kind of comes in on both of the professional and managed services side, right. But I would say, anytime a customer is looking to do any sort of optimization or migration or really professional services type of project, that’s where we come in. We have customers all the time, especially in today’s macroeconomic conditions, we have customers saying, hey, we don’t know that we’re optimized, we need help, we want to take a look at our cloud spend. We have a fair bit of cloud sprawl. Can you help us? Absolutely. There are tons of ways that we can help you. We can do as high level as a let’s put it in an automated tool, get some understandings of where you’re at, just spit out a report and say this is what we might be able to save you all the way through to all right, let’s get a couple solutions architects in there. Let’s review your architecture. Let’s review what you’re trying to accomplish and kind of redesign the whole thing. So that you’re completely well architected from the beginning, and already cost optimized and performant and all of those things, right. So that’s the first piece, just the professional services, professional services, as I mentioned, also really where we cut our teeth was with migrations, right, customers that are looking to move to the cloud. It’s 2023 about to be 2024. Happy New Year, everybody. There aren’t as many customers that were trying to migrate as maybe 2018, right, but there’s still tons of customers that are trying to migrate to the cloud, right. And so as I said, with our pedigree, as well as our focus on security, and operations and reliability, that mission critical piece, our bread and butter is building out a well architected environment from scratch for a customer, right, that could be a migration from an on prem. That could be a migration from a private cloud migration from a different cloud provider, right, Azure, Google to AWS or AWS to Azure, Google, whatever. Or even let’s say you’re already in AWS. But like I said, the first time pretty bad cloud sprawl, you built it 10 years ago, not using any modernized tools, it’s kind of a data center in the cloud. Let’s migrate you to a new workload in AWS, right. So that’s professional service, managed services, once we know that your environment is optimized and well architected, now we need to make sure that it’s well operated, right. And so back to the 1993 logic works services of old, we’ve always been a managed services provider, 24 by seven support, onshore knock, making sure that our customer environments are always on, always up, always running secure and reliable, right. And what we do with that is that third piece, the platform, we have something that we built called the cloud reliability platform. Now, I’ve mentioned the not so large nature of logic works, right. But we have some of the largest customers in the world, right. Under our management, we have the largest private investment company in the world, right. The largest private insurance company in the world, we have a lot of these, the largest healthcare exchange company in the world, a lot of these very large customers that have expansive cloud footprints, right? How are you able to manage such an expensive cloud footprint without people? The answer is automation, we have to eat our own dog food, we need to take our own medicine, right. So we’ve built this entire automation platform on the back end, that’s proactively monitoring and measuring these customers environments, and remediating things that we find that are out of scope or out of compliance with what we have deemed to be a best practice, whether that’s an industry best practice, or whether that’s a specific best practice for this customer, right? That could be compliance regulated, that could be reliability regulated, that could be contractual obligations for our customers, we built it into the automation of the tool that’s continuously tracking. And so all of these things come together for that managed service, allowing our customers to grow, focus on their business objectives, focus on the business logic of their applications, and not have to worry about the menial aspects of managing infrastructure. Because at the end of the day, how do we grow the hyperscale by leveraging managed services, you don’t focus on the menial tasks, right, you focus on the things that will grow your business. And so you offload those to us, and the AWS or Azure or Google cloud providers, and just ride that rocket ship to the moon. Love it. You know, the next thought here is, I think the channel was very used to for a number of years, just not being able to touch anything with regard to AWS and Azure and Google, we hear about these things and we go, you know, I can’t help you in that. But let me tell you about, you know, this situation, right, we could go this way. And, you know, look, there’s a lot of great products in there. And then customers had gone that direction, whether we’d liked it or not. So what’s nice about you guys coming into the play, right, is that maybe our first segue into that was 10, right, we could tell some of the hyperscalers, but you guys bring a whole different dynamic to this. And so you could take that to your point and some of the products that you just mentioned, yes, you could 10 but 10 is just the top line of what you guys can do, because whatever the recommendation is, you can go fix it, you can go migrate it, you can go build it, you can go automate it. So you guys bring an expansive portfolio. So what I’m curious on that is in the deals that you’re seeing, I always like to talk about wedge services. So when you’re coming into a conversation, all the deals that you get brought into, what’s the what’s the kickoff wedge service that you see most common? Is it backup? Is it DR? Is it I don’t know if I’m overspending? I mean, just walk us through that.

Yeah, I think there are a few. And it definitely changes every six months or so. Right. As I mentioned, the macroeconomic conditions, this year has been heavily focused on cost optimization. But prior to that, it wasn’t really focused on cost optimization. I think there have been a lot of conversations over time about how cloud might be more expensive and whatever, blah, blah, blah. But when people are considering migrating to the cloud, it’s more so for a different business objective, right. And I think oftentimes you just hit the nail on the head, we hear a lot of DR, right? I don’t know that I’m ready to die fully in. I’ve got some infrastructure here. I’ve got a VMware contract, all this stuff. I don’t want to just throw that to the wayside. But I do need a DR service. And if I’m going to do DR might as well try it in the cloud. Right. And so we hear that. We can help with that objective for sure. However,

you’ll hear many times throughout this, this talk that I like to focus on the actual business driver, right? So why are you trying to achieve the DR solution? What is your contractual obligation for uptime or RTO, RPR, whatever? Right. And so once they come to us, and they start saying, Yeah, we need this DR thing, I’m like, well, you know, it might be better if we did this thing a little differently, and then try to steer them more towards just the migration to the cloud. And, and that is really what gets their, their feet wet. And then they fall in love with the cloud. Because, I mean, just the case that it is, it’s way easier to deploy and grow than, than anywhere else. So DR is a big one. I think depreciating hardware or hardware refreshes, right? When customers say, well, you know, our hardware is old and dying, we need to do a hardware refresh in the next year, should we consider the cloud, right? And so then they come talk to us in similar kind of conversation, we try to understand why they’re looking to move to the cloud, because as I was just saying, the cloud might not always be cheaper, you know, the public cloud might not always be cheaper. You need to do it right. You can’t just build a data center in the cloud, you can’t just migrate all your technical debt. So we want to understand from from that perspective, why they’re looking to move. And then finally, I think the cost thing, customers that are already in the cloud, they might get a bill that they were not expected, right? Our bill just raised by $10,000 in the last month. What is this about? Because the public cloud is a variable cost that’s always fluctuating dependent on usage, that usage includes network traffic, it includes data egress, things like that, right. So, but it also includes something that you might have turned on and forgot to turn off. Right. So customers get a whopping bill. Yeah. And they’re like, what happened here? And then they call us and we have to help them out, take a look and see what happened. Yeah, it’s good. Okay, so let’s talk then, you know, that those are great, I think, kind of where you’re seeing the wedges come in. That’s good. Let’s talk about everybody’s favorite three words for 2023 going into 2024 large language models. So I believe that this is our next gold rush. I believe that everybody’s gonna want to do this. Everybody’s going to be told, it’s just like in the beginning of cloud, hey, we need to go check out cloud. Are you checking out cloud, right? Some C level that doesn’t understand what cloud is, but knows that they need to go check it out. So I think this is a little different, right? Because there’s quantifiable value immediately in this, but I think it’s hard. So Don of his opinion on how things like large language models, but you guys have great products and you’re right at the epicenter of how are these going to drive customers, infrastructure and security needs in 2024? And how do you guys help?

Yeah. So one of those products that I didn’t talk about this nestled in the professional services is our AI team, right? We have a whole product set of designing and building AI models for our customers. How is that going to change the market? Well,

a lot of people, I think, as you just said, focus on the buzz wordiness of the AI ML thing. It is everywhere you look. Just a couple weeks ago, I was at reinvent AWS reinvent their big conference. And there were some really, really cool services that were released like AWS Aurora limitless, which is limitless sharding of your data, right? But that was so minuscule in comparison to all the AI and generative AI stuff, because the whole market is pushing AI and asking for AI, right? So it is I agree at gold rush, and everybody needs to be in on it.

However, they need to be aware and savvy of the conditions and the drawbacks. One thing that you just said is security, right? This is at present, sort of an unregulated kind of thing, right? There is a lot of data out there, customers either have their own data, or maybe they’re using some other data set, right? People might not understand the data that they’re putting into their models, right? And the way that AI works is that it’s continuously training based on the data, right? And there could be some nefarious or malicious things in the data. Or there could be nefarious AI models that are trying to attack you, you know, who knows? So I think the first thing every time I talk to anybody about AI is you need to get your data, right? You need to understand your data strategy, understand your data sources, clean the data, instead of just inputting a bunch of raw stuff in there, make sure that what you’re trying to get out is similar to what you’re actually putting in right? Because you don’t want it to be garbage in garbage out.

Aside from the security aspect, there are tons of ways that it’s transforming businesses and how we’ve already helped customers, right? We’ve helped customers build predictive maintenance models for their for their operations for hardware that might be depreciating or need to be replaced, right? We’ve built chatbots for customers, we’ve built image processing tools, right? There was a car wash that basically could take a picture of the car before and after and tell you what the what the aspects of the car wash were and things like that, right? But there are infinitely many ways that you can use this AI tool. There’s another one that I’m talking to a customer right now. They ingest

petabytes of data of phone calls, right? Recorded phone calls, they have a call center, right? And as we know, in the channel, this is a huge thing. They’re call centers for everybody, right? So how do you actually make sense of all of these calls? Right? Can we summarize these calls rather than having to listen to two hours worth of a customer service call? Can I actually drill down, get the summary, get the customer sentiment, understand what happened on that call, things like that, all of that is capable with AI without needing to use any sort of human intervention, right? Yeah. Awesome. I love it. This could almost be its own podcast. We’ll have to have you come back. There’s a lot to unpack there. But I think the summary on that, though, is all good stuff in that you’re already doing this, you’re positioned and you can help. So I want partners to remember that when they hear this part, you guys are you guys are right at the epicenter of that. So perfect stuff there. Okay, so some real quick practical advice, let’s talk about for partners that are listening to this, right? I’m excited. I have a better understanding of who LogicWorks is. What’s the approach, though? You know, what’s the practical advice or approach to just help them start some of these and capitalize on figuring out where these customers are with regard to cloud?

So I always like to focus on pain points, right? Pain points and business drivers. Maybe we should rename the podcast pain points. Yeah, that’s about right. And so when I’m talking to a customer or when a partner is trying to talk to a customer, a simple question to ask is what kinds of issues are you facing right now? Right? What isn’t going as well as you would hope that it could be going? Right? And that just opens the door because once the customer starts talking, you could jump in on anything that they have to say, right? Oh, well, we said before, environment is too expensive, or maybe we’ve had some downtime, or maybe it’s not secure, blah, blah, blah, right? So that is probably the best way to uncover a customer’s need, right? Higher level than that. Just try to understand what they’re doing on their infrastructure side, right? Where are you hosted today? Is there something that you would desire that you’re not getting, you know, things like that? Yeah, no, it’s good. Perfect. Alright, let’s let’s talk specifically about an opportunity. So what I love to hear on this part of it is, how was it brought to you? What was the perceived problem? What was their tech stack before that you may be displaced? And then what did you end up, you know, moving them to?

Okay, so one of my favorite customer case studies is Servpro. I don’t know if you are familiar with them, they’ve got the big green trucks with the orange house. It’s like real life disaster recovery, right? It’s like your house gets flooded.

They come in and fix the whole thing, right?

Servpro actually contacted us directly. Because they were having some issues with their database, right? They’re like, got this giant SQL Server. And we’ve got a lot of things that are connected to the SQL Server. We’re considering how we might be able to move this to the cloud. Right? Okay, cool. So another one of those services that’s baked in the professional services is database services, right? We can help refactor migrate, transform databases, we can bring it from a SQL Server to a more modernized platform like a Postgres, or MySQL, or even NoSQL, like Snowflake and things like that.

Okay, so we start talking to this customer. And this is actually an amazing story. So thank you for asking. Start talking to the customer, they’re like, we’ve got this giant SQL Server, we’ve got 1800 franchises across the country that are all connecting to this one SQL Server that hosts all of the data for our ERP system, right? Okay, they also had apparently about 100 back end applications that are all pulling data from the SQL Server, right? Because it’s all back to go wrong. Yeah, what could go wrong? Everything is like it’s always going down their performance issues, there’s latency, all this stuff. So we’re thinking about putting a read replica in AWS. And I was like, okay, cool. How are you going to replicate the data, right? between this read replica and whatever. And we talked about it for a long time. There are a few ways that we could do it distributed availability groups or transaction replication logs, whatever. And eventually, I was like, guys, we’re going about this the whole wrong way. Like I said about the DR kind of conversation. We should put everything as the primary in the cloud and kind of rebuild it because the way that it’s architected right now is not built for success. It can’t be a distributed model as it is and expect it to be successful, right? 1800 franchises, tons of VPN connections like can we can we can we call out one thing I think this is really important that never gets talked about with databases. databases are really, really, really hard to scale. And it’s not like I can just say, let me spin up a second database, a second server, it doesn’t work like that, right? You can improve the compute, you can improve the RAM and all that stuff. But inevitably, like these guys were probably seeing a problem. So your thought is, you just because of the expertise that you have, you foresaw that, I don’t even know that’s a word, but we’re gonna make it a word, you foresaw that this was going to reach a point of contention. And this wasn’t going to work either. So I love that you called that out. Yes, exactly. Because even if you build one read replica in the cloud, first of all, all of your rights are still going to go to this primary database. So that’s the very first thing. The second thing is you have a finite number of replicas that you can build, right? And then every time that’s going to be latency and transaction issues, right? versus what we eventually spoiler alert, what we eventually migrated to them to was an Aurora Postgres based deployment in AWS, that natively can replicate across six databases horizontally, just by default, right? So that even without doing any other additional multi master or any of that stuff, you’re already six X better than what you were before, right? And that kind of compute capacity is only possible in the public cloud, right? So they were like, Okay, you know what, we’ll take your advice. Let’s see what this might look like. If we migrate the whole thing into AWS, we did an assessment and a design and we said, Okay, the the whole application isn’t isn’t that great. You know, it’s like 20 years old. Yeah, yeah, a lot of cruft that we could have improved. And so we’re like, Okay, let’s come on site. So we go on site. And we are in their lobby for like two hours, we try to check in. The secretary is like, our system is down. I don’t know, like I told them, but apparently they’re working on something. So just hang tight. We’re in the lobby for like two hours with any nobody coming to visit us or anything. And finally, the CTO comes out and he’s like, Hey, guys, sorry about that. We had a data center outage. It turns out a squirrel chewed through our AC lines. And though he AC went out, which means everything overheated and went out. And so we were like, sounds like you need to migrate it was like you could you could write this stuff. Yeah. So anyway, it was it was a really good on site. We did like this multi day engagement doing a whole bunch of white boarding they’re like, Okay, we’re bought it. Let’s do it. So let’s fast forward a little bit. We finished our assessment of their entire estate. It wasn’t just the ERP system. There’s also that hundred or so applications that they had on the back end. It wasn’t 100 or so applications, they had about 300 applications. A bunch of them they didn’t even realize we’re running because how many people you know, I know you can’t all raise your hands. But if you’re listening to this, how many of you actually have inventory management systems or automated tools that are continuously scanning your networks and keeping track of your applications and things like that? Yeah. 1% of companies, right? So they had all these applications and a lot of them were not in use. A lot of them were still in use. Then so we had to figure out, okay, what’s the best way to slice this. So for that ERP system, we ended up rebuilding that into a completely modernized micro service based architecture, right? So the front end and the the top two tiers, the web and the app tiers were completely containerized, built in an EKS based Kubernetes deployment, right? I think there were about eight different test definitions, eight different containers per pod, right? And then the back end, as I mentioned before, we migrated them away from SQL Server and into Aurora Postgres in AWS.

That allowed us to, as I mentioned before, scale, but also improve the performance of the database, while also cutting costs by like, 75%. Because now you’re not worried about licensing. Like you said before, scaling the database is very, very hard, right? So the only way to scale the database is to scale it up, right? But when you scale it up, the number of cores go up. And when the number of cores go up, the SQL licensing is very expensive, right? So now we don’t need to worry about SQL licensing anymore. Now we’ve got completely open source based Postgres engines, whatever. Awesome. And then any of the caching and customer preferences or any customer data was going to be stored in a NoSQL database in DynamoDB and AWS, right? Then we got to these 300 applications on the back end. And we said, Okay, these don’t necessarily need to be rearchitected. A lot of them are third party off the shelf cots, right? And so instead, what we did was we just built basically an automated pipeline that was picking up all of their applications, creating a golden image in AWS, deploying it with all of our tools, because they had to be PCI compliant and all this stuff, right? So we built that golden image that had all the security and reliability requirements on the back end, put put it in the in the pipeline, picked up their application, installed it on the image, redeployed it into the auto scaling groups, and basically rinsed and repeated this for these 300 applications. And within less than nine months, we were able to migrate their 700 server data center into AWS. So that is one of my favorite case studies because it,

as you said, started with a really small thing, how can I help improve my SQL Server and turned into how are we leveraging literally all of LogicWorks services, which by the way, culminated in them as a managed services customer that they’re still a managed services customer today. So great success. I love that, you know, not every opportunity is going to be that complex. But I love hearing opportunities like that, because they’re buying everything on the menu, right? So we know it works, we know you’re good at it. And they know they couldn’t have done it without you. And and now, the quality of that network, the performance of that work network, the squirrel factor is out. And amongst other things, the scale and the responsiveness, I can’t imagine how many metrics improved in their ability to continue to scale and how happy people are and the users are all the people running, you know, driving the trucks trying to access the applications, all those things. Yeah, that’s that’s awesome. Awesome story. Yeah, thank you.

Okay, so final couple thoughts here. So bring us home on next to last question here. I’m excited. Again, you’ve really opened everybody’s eyes to all the things that LogicWorks can do. So if I want to go back to my customers right now, I don’t even want to listen to the rest of this podcast. But I want to hear what are the top three questions that you would push a partner to ask to open up doors like this? Yeah. Okay. So top three questions. I mentioned one of them earlier, what are the primary challenges that you’re facing today with your IT or your tech stack, right? This could be for your infrastructure, it could be for reliability, it could be cost, whatever the answer is, what are the pain points that you’re facing, because we can expose the pain points, we can definitely find an opportunity for us to come in, right? Plain and simple, 10 out of 10 times.

Unless they’re doing like Amazon Connect, which is call center stuff that we don’t do. Aside from that, 10 out of 10 times, we’re going to be able to find something to help ease their pain, right? So just reiterate what challenges what are the pain points that you’re facing. Second, business drivers. Okay, so now that we have discussed a little bit about their infrastructure, maybe we know that they’re looking to migrate to AWS, for example, right? Okay, what is the business driver that’s compelling you to move to AWS? Right? Okay, you’re saying that you want to transform your database? Okay, why? What is the business driver that you’re trying to accomplish by transforming this database? Right? Because the reason why this is a very important question is, if the customer we so everybody should go check out rapid scales website, we just did a research paper asking 500 senior leaders about their

experiences in the cloud. And we got some very helpful data. I think something like 27% of senior leadership had skepticism with respect to their cloud journeys, right? That’s a pretty high number to me, right? But I know exactly why that happens, because it costs money, right? It’s going to cost money for you to transform your database, going to cost money for you to run the database, whatever the thing is, right? And so if they don’t understand themselves, what the business objectives are, then they’re not going to have faith in the project once it starts, right? Sounds like a good idea, then they’re like, maybe this is not a good idea, right? So for all parties sake, understand what the business driver is. And if they don’t have a good answer, figure it out with them, right? Well, here are the benefits that you can hope to enjoy by doing this thing, right?

And then tagging on top of that, kind of the last thing that I said, what are they hoping to achieve, right? What is the success that they’re looking to accomplish by doing this thing? Right? Is there success criteria specifically? Right? Is there, for an AI model, for example, let’s talk about that. That’s actually a specific question. What is the success criteria? Right? Is there a confidence interval? Is there a 95% accuracy rate that we need for x, y, and z, right? So I think with those three questions, you can uncover any opportunity in the public cloud in the hyperscalers. And then give us a call. I love it. I love it. All right. Final thoughts as we bring this home, Don of his opinion, any trends, any developments, anything product releases that you want to share or anything we need to pay attention to in the market that we haven’t already talked about or anything exciting new coming from the rapid scale logic work side?

Yeah, so we’ve talked about the AI ML stuff a little bit, right?

Just everybody keep an eye on that because the services and tools that are coming out across all the hyperscalers, it’s daily, right? They’re coming out with new things. Customers are asking about it. So just keep an eye on it so that even if you don’t know the details about the thing, it’s like, Oh, yeah, I heard about that. That was a thing that released that reinvent, right? For example, the other sub segment of that is the AI piece. I mean, sorry, the data piece of AI, right? So as I mentioned one before, the Aurora Limit List, there are a lot of data tools that are coming out right now. And your AI models are only going to be as good as the data strategy behind it, right? So they’re kind of intertwined in the market right now. So every time there’s a new AI thing that comes out, there’s a new data thing that comes out. So keep an eye out for the data trends that are coming out from the hyperscalers. And then finally, from rapid scale logic works,

again, focusing on the AI, we have this shiny AI team that can help build any AI services for customers, any large language models that they want, whether it’s built in AWS native like Amazon Bedrock or SageMaker, or if they want to do their own model built on a VM, we can do both, right? Yeah, I think that’s a lot. I love it. That’s really good. I’m gonna, I’m gonna require everybody to go back and listen to this three times. We covered a lot of good stuff. Donovan, that wraps us up, man. I really appreciate you coming on. You dropped a ton of knowledge today. Thank you so much for spending some time with us. Yeah, thank you for having me. Thank you everybody for listening and looking forward to talking to you all. Awesome. Okay. That wraps us up for today. Donovan Brady, director of solution architecture, rapid scale, cloud powerhouse managing AWS and Azure and elevating on Joss Lupresto SDP and Sales Engine Manager. Next Level BizTech has been a production of Telarus Studio 19. Please visit Telarus.com for more information.