Rich Martin • 00:05

Hello, everyone, thanks for joining us again. My name is Rich Martin, Director of Technical Marketing, and today we are going to be unpacking this idea of going from infrastructure to services, how attention can take you from where you’re at in your automation, help you to do stateful orchestration, so you can enable on-demand self-service resources across the lifetime of these particular services. And we’re going to really get into this. I’m super excited to be joined today by Ankit Bhansali. Ankit is, in my opinion, an expert on this because he’s done the work and he’s talked to the customers. So instead of me blabbing about it, Ankit, why don’t you just introduce yourself really briefly and we’ll jump right in.

Ankit Bhansali • 00:47

Hey Rich, thank you for having me. Name’s Ankit Bhansali, Senior Solution Architect at Etentral and looking forward to presenting some cool stuff we do.

Rich Martin • 00:56

Awesome. Well, Ankit, when we talk about this idea of, we’ve been talking at Etentral about this idea of having the product mindset, right? And I’m just gonna be honest, coming from the network engineering background, my mind is not wrapped around the product mindset. My mind is wrapped around, I’m the data center network engineer, my world is the data center, I do all the data center things. And when we’re asked to create something in response to maybe like an internal customer requesting an application, I do think in terms of a service, but I only think in terms of like the service that I provide. and one of the things that I tension, we’re not only educating our customers, but I think our customers are coming to us and educating us about what they want to do is having this product mindset. I want to explore this topic really quickly before we get into the demo with you.

Rich Martin • 01:50

Tell us a little bit about what you’ve seen from some of our prospects, some of our current customers about their wanting to get into this offering products instead of looking at their infrastructure as disparate services that have to be cobbled together at the last minute.

Ankit Bhansali • 02:06

Correct. And I’ll pick it up from the last sentence, disparate services, right? I’ll go one step further in this idea, because there’s so much tooling out there right now. And folks have picked up a lot of skills, which is either writing scripts or, you know, doing REST interfaces with controllers. So they have picked a lot of skills and teams have also picked up their technologies and their go to market in terms of how they want to deliver these solutions. So now when it comes to managers and organization concept, they have too many disparate teams with too many disparate tools. And they’re trying to figure out what’s an overarching thing that can actually help them connect these dots, still give the freedom to the engineer in picking the Python or writing a batch script or a pull script at the same time, providing organizations the ability to actually build end-to-end services and productizing it. So they have compliance and standards associated in delivering something similar and consistent, because that’s been the current challenge across all of the customers we have been talking.

Ankit Bhansali • 03:13

And that’s because people have learned a lot. They’ve understood a lot. And with chat GPT, Gemini and AI tools, they can even write more code than they were before. Yeah, we also have to accommodate those kind of engineers who are skilled enough to now take advantage of the AI tooling and bring new solutions to the organization. But organizations are struggling how to standardize those kind of ideas and still give the freedom to engineers.

Rich Martin • 03:42

Right, right. And so starting with the product mindset, it’s really about taking all those tools that you have and not throwing them out, but actually finding a way to utilize them all together more holistically. So when I think about the product mindset, maybe as a network engineer, My first step into changing the way I think about things is maybe to relate to. things outside of the world of networking and infrastructure and IT. And you and I had a conversation the other day about, you know, an analogy to this that hit kind of close to home. So what was it that we talked about?

Ankit Bhansali • 04:15

Yeah. So I’m in global supply chain, right, as a concept. And we’ll take one off from manufacturing plants. Let’s say it’s manufacturing a car. We all love cars. People drive cars. We love Toyota. I know that’s your favorite. That’s my favorite. So so imagine how Toyota is actually managing this concept of manufacturing cars, right? At the end of the day, the car is made up of multiple components selected by multiple different reasons, regions and reasons behind why they are choosing those kind of components.

Ankit Bhansali • 04:49

And there’s always going to be an iterative approach towards that car, you know, trying to make it the more optimized, more efficient and more cost effective to the end consumer. Right. We’re trying to see that similar mindset where now folks have built a lot of components in their organization. But how do you have something as simple as ordering a car in terms of auditing the services from a networking side, especially for organization when when you have so many disparate systems, the idea is the firewall, the load balancers and co-networking folks writing their own technology. So we. I think that helps us kind of encompass the idea, how do we bring together so that we have a finished product at the end, which everybody kind of drives the same car at the end of the day if you’re buying a particular model. So there’s, because of the standards in place, now they can have reliability and ability to go at scale rather than having to manage these custom ad hoc solutions.

Rich Martin • 05:51

If that helps. Yeah, no, that’s very helpful because that’s really what hit close to home. I actually had to buy a car recently and my thought process was, and now we’re taking this from the end user perspective. What was I most interested in? I want a Toyota, I want a truck, I want a Tacoma, I want a V6 and those are the most important elements and everything outside of that is not as relevant as those things. Help me get the one thing that I’m looking for, right? And so now that I’m thinking in that perspective, how a car company would manufacture a car and all those different components and the supply chain on the backside and then coupling that with the front end, like the user experience, just get me the car that I’m looking for and get it to me as quickly as possible based off of this criteria.

Rich Martin • 06:36

that’s what we’re looking for. And so that’s really what the product mindset is built around. And we’re already used to it, right? Honestly, cars, whether it’s cars, whether it’s apps and app stores, software, you name it, you know, your DoorDash is all about the customer experience and gathering all these things together to make it happen as efficiently as possible. And so really, it’s not that much of a stretch for network teams, cloud teams, really all the IT infrastructure teams, because they all have to participate in this, is getting used to that product mindset. So when we talk about this, really there’s some key points that you have to solve for, right? Obviously, we talked about how to simplify and how you deliver this infrastructure kind of packaged up to the end user in a simplified way.

Rich Martin • 07:27

Creating repeatable products based off of these common infrastructure services. So again, all your teams are really gonna have to participate together using the automations that you called out earlier. And we do expect to see more and more automations with AI tooling, making it so simple to build. Then somebody has to intelligently choose the appropriate resources needed for these products. If I want a vehicle that’s off-road, it really ought to have off-road tires. In organizations, the person ordering may not be privy to all of the things, the policies on the back end, but knowing who they are, what they’re requesting, and those policies built in to this product mindset, we can deliver what’s appropriate for them.

Ankit Bhansali • 08:15

Yeah, and service delivery is key, not just important, but the way organizations get to govern these requests, because they’re going to have standard best practices built into the process flow, so they can go out and pick and choose the tools they want and still be able to deliver as fast as possible, and also expose new services for monetization purposes. So, think about an MSP, when let’s say if you want to sell additional add-on services as a concept, hey, I want to increase the bandwidth, can I do that really? And what do I have to do to increase in bandwidth for an L2 VPN kind of a service, right? I’d have to find all the information about the customers, all the systems that were used during provisioning, all those other external outside of network kind of attributes, you’ll have to also manage that. Imagine you could have it in one place, which means it would take me a second in terms of understanding what I’m trying to change for what customer, and still offer an add-on services. So for organization, it’s not just standardization and best practices, it’s service to delivery and opening new doors for revenue to go even further and faster.

Rich Martin • 09:29

Yeah, that’s a great point, and that really is our last two points here is that when you think of this product mindset, what you’ve got to deliver is the ability to track not just when that product comprised of many services was created. But over time, the changes, and then eventually, and this is maybe the kicker, because this is where we, especially as a network engineer, I lose sight, the decommissioning of all those resources. You ever had ghost configs? You ever have configs and ACLs that are stuck in the middle of something, and you’re like, what is that for? You solve for that problem when you take the product mindset and you build everything around the idea of delivering a product, and you get all kinds of rewards with this. Historical reporting, optimal resource utilization, security being tied to the product as well, with things like compliance and things like that, and then the ability to troubleshoot. Many times, okay, I’m gonna go ahead and throw the rest of my network angst out here.

Rich Martin • 10:28

Whenever some application breaks, what’s the first thing to blame? The network, and the networking folks are like, well, wait a minute, and this is how we already know that there’s a product mindset. We just don’t capitalize on relating to it as much, but when you’re being blamed for your thing being broken because somebody can’t connect to the web server or the database, as a networking person, I go, well, hold on a second. It could be a number of other things related to that application, right? You’ve got the operating system, the application, the software, the compute resources, the firewalls, all those things. We already understand the product mindset.

Ankit Bhansali • 11:03

Correct, correct, and then we’re trying to give that single window pane of glass here because to your point, it’s not just the network that is responsible, and I’m gonna piggyback on one point here is provisioning some asset or a service, it’s a one-time job. Decommissioning is a one-time job. But still it’s a big challenge on how people, you know, try to manage to do that is because it’s hard to bring everything together from an orchestration standpoint. Because you have to dip into multiple system of records, create these records, and again, they are lost in the ether, because nobody is kind of tracking to your point as a single product entity idea. But the biggest benefit in my understanding is brownfield networks. You’re going to have to sell these services, add on services, you’re going to keep changing these services. Imagine there’s an application, you’re going to deploy something with a load balancer, right?

Ankit Bhansali • 11:55

Let’s say your product is going to be, you know, available for people to consume it is going to go live, which means that load balancer needs reconfiguration for, let’s say, primetime usage. How are you going to do that if you’re not managing it under a single product entity, right? So I think maintaining and those day two activities is where you get real value out of just having this model product services idea as compared to just fire and forget. And then creating multiple change requests that goes into multiple teams because a change in load balancer might change in firewall. Because guess what, there’s a new VIP name with new DNS entry that needs to be added to the rule that needs to allow some particular traffic on a different port. So there’s a lot of consequences because we did not plan it as a single product. And that’s where usually the customers are coming from is saying, okay, I understand we can do a lot of these things.

Ankit Bhansali • 12:50

How can I standardize it and give it as a self-service product? And I still get the benefit of having that single window pane of glass.

Rich Martin • 12:57

Fantastic. Okay, well, let’s dive a little deeper into the architecture. Walk us through what you’re going to be showing us today. Yeah.

Ankit Bhansali • 13:04

Yeah, so this is something cool, which we’ve been talking to a lot of customers. Ten years ago, Cloud was coming up and people were trying to evaluate different Clouds, different technologies, and I think right now we live in a hybrid Cloud world. It’s not just hybrid Cloud, it’s just going to go from on-prem data centers, trying to also incorporate among other things that want to be part of the end-to-end orchestration. So what we have seen from multiple organization is there are skilled people, SMEs on these Cloud providers, usually coming with Cloud certifications. When they plan something, they try to choose their own technology, their own best practices, right? But the real challenge from an organization standpoint is I cannot really productize this because every team is using these different things that suit them and they are choosing based on their budget, their regions, on Cloud providers. So in this example, I’m doing a bottom-up approach where I have a team that understands Cloud formation.

Ankit Bhansali • 14:09

They are very slick, they understand how to work with Cloud formation. There’s another team that understands how to provision things in Azure using Terraform or OpenTofu. And again, there’s another team that understands using OpenTofu and Terraform, how to interact with Google Cloud. All of these technologies I’m going to be using for just VM provisioning, very simple use case. We usually go to Cloud to provision a resource and in this case, I’m taking a VM provisioning example. From an organization standpoint, you do not have a choice other than to create these disparate change request tickets where you have to ask a lot of questions, and then an engineer comes in and try to understand where this might need to go. There’s some human routing required to understand the request.

Ankit Bhansali • 14:54

What we’re trying to propose here is, since Itential can connect to more than 200 and plus external systems, when it comes to ITSM, ticketing, firewall, load balancer, at the same time, we can also talk to multiple cloud providers in the technology of what the engineer wants, especially whether it’s a Python script, it’s open TOEFL plans, or even some ad hoc system which talks to these cloud provider. So what we are trying to do is give them a way to define service abstraction on top of these kind of tool set. So from a organization standpoint, it goes according to a services productized concept where I want to provide a product that is going to be provisioning a VM. That’s it from an organization standpoint, very simple. And then I can propose these separate services that helps you manage that product, whether it’s deployed on CloudFormation, Azure, or Google Cloud. There’s a fine bit of things here because if you’re familiar with Terraform, there are attributes that Terraform tries to track from a statefulness perspective, right? At the same time, you also have to go around in terms of Terraform to connect to multiple sources of record, your IPAM systems, your ITSM tool, right?

Ankit Bhansali • 16:13

This is where Itential kind of orchestrate end-to-end. And now it not just has the attributes of Terraform if required, it also has an attribute of all the products, all the attributes that are associated to the product from a request perspective. So now organizations kind of get a single window pane of glass. If Rich requested a VM, that VM based on where it needs to go, we’re going to understand and build intelligence. So we can natively use whatever we are building in terms of organization’s capabilities of delivering these services rather than reinventing the wheel. Because it’s so easy to tell you, hey, write everything in Terraform, and that will be a lot of pushback because you’ve already invested time. People have put so much time and effort in building these tools and best practices around this.

Ankit Bhansali • 17:03

We should be now relying on them rather than trying to ask them to recreate this whole new environment.

Rich Martin • 17:09

Yeah, exactly. That’s an excellent point because a lot of times in order to go forward, if you force people to give up the tools that they have, that they’ve invested their blood, sweat and tears in, they’re actually going backwards to go forwards, right? And this also helps to future proof you in the future, what tools around the corner are going to make us even more efficient, right? And being able to utilize those as well. So being able to give you a place at the table with the tools you have today, the tools that each organization, each domain, they choose those tools based off of a number of different metrics, right? This is what I know.

Rich Martin • 17:49

This is what is best for this particular network domain or this particular cloud platform, right? There’s a lot of things that we don’t need to dictate to our customers. They know best what tools are. We want to leverage all of those. And this also, it kind of gives you the explanation that you do need something beyond those automation tools in order to get to this productization of your infrastructure.

Ankit Bhansali • 18:13

Correct. And to your point, good automations, Pick your choice, be flexible on how you want to execute that, orchestrate the way organization wants to run that kind of idea. But at the same time, you get the ability to provide services that are standardized with governed principle, and that way they can do this at scale without having to fear in terms of breaking and then asking multiple requests to different stakeholders here in terms of, hey, I need a firewall rule, which means they have to investigate the whole network where this needs to be placed. I need a load balancer and they have to investigate which vendor to select from. So, and it’s not that it’s hard to do, it’s hard to, it’s hard for organizations to build this abstraction. And we have made it in such a way that now it’s flexible enough to define your own service abstraction, rather than being, you know, being in, excuse me, rather than being forced to follow certain standard and process from a particular tool itself.

Rich Martin • 19:18

Okay, fantastic. Well, do you want to jump in the demo and start taking a look at what it looks like under the hood?

Ankit Bhansali • 19:23

So going into the demo mode here, we will be doing a global VM provisioning concept. And during that provisioning, we’re going to make sure that we provision the VM in the right space. We pick the right cloud provider. And at the same time, we provide the right firewall rules in the right place and make sure we have a load balancer that’s also configured as part of the request. So it now becomes a standard experience for provisioning VM from a organization standpoint.

Rich Martin • 19:51

Fantastic.

Ankit Bhansali • 19:54

So I’ll share my screen. So Rich, as we discussed, IT team would love to use ServiceNow for requesting, just like they’re familiar with ordering any service, either from a service catalog item or coming into an Itential application inside of ServiceNow. So I fill up a form, I provide some information, and this is global VM provisioning. In this case, I’ve not identified in terms of the user does not have to understand where this needs to be deployed, what technology is going to be used behind the scene. All they care about is providing them with a virtual machine that is going to be purpose-built for training lab, which means it should have all the firewalls necessary to talk to the lab network. It’s used for development and the region it’s going to be used in for North America. Now, organization can ask these basic, simple questions and hand off this request to Itential, where Itential can do the intelligence in terms of the policy they want to apply on, on what type of rules they want to apply for a training lab, what load balancer is conveniently allowed for this kind of VM provisioning, what Cloud provider to use when the region is North America.

Ankit Bhansali • 21:08

I’m going to hit run. Yes.

Rich Martin • 21:10

Yeah, go for it. Hit run automation. I’m just going to mention that this is that first part of it. How do we streamline the end-user experience as they are ordering the resources that they need?

Ankit Bhansali • 21:21

Correct. So the way we have distributed this idea across lifecycle manager application is we have a global VM provisioning resource model that’s going to take in the request and it’s going to route it to the right VM provisioning Cloud provider. So the attributes and the request that’s coming in from a service construct is contained and you have advantages of actually seeing those attributes real-time. Because in the global VM provisioning, we have not decided which Cloud provider to use, we have not decided what firewall rule to apply or what load balancer to use. So if I’m going to check into global VM provisioning, I should see an instance called demo-vm1. If you see, it’s currently complete, which means we have initiated the request to itential and we got the request in and it looks like the properties are part of this flow.

Rich Martin • 22:25

That’s excellent. So basically, end users ordering with a minimal amount of information, just what they want, and this executes a workflow in the Itential platform under Lifecycle Manager, which is the application that’s going to help us not just create this, but now track this data that we’re looking at here. Is that right?

Ankit Bhansali • 22:49

Correct. So when we get the request, right, we have a flow that has the intelligence in terms of what it’s supposed to be doing. So if you look at this flow right now, we got a request and the request basically told us what region it was supposed to be deployed. And according to that region, we were able to identify what cloud provider to pick on. And assuming in this case, we were doing Azure because we saw it’s already complete. So it’s a high level routing concept where it’s trying to identify which cloud provider to use and then basically go provision a firewall rule depending on the purpose of this VM and an associated load balancer with that request.

Rich Martin • 23:34

Right, so this is what we were talking about earlier when we’re embedding this logic in, we’re putting a minimal information in front of the end user customer. But based off of that information, the logic is now built in to determine precisely what they need, where it needs to go, and what we need to do with the other infrastructure resources like firewalls and things like that to connect it up, wire it up so that it can just be delivered to the end user, without them really needing to know where it actually exists.

Ankit Bhansali • 24:02

Yes, very true. This is the first part of the flow. In this case, we have three Cloud providers, one for Europe, one for Asia-Pac and one for North America, and as we can see in the flow, we took the North America route, and which means we must have triggered a Azure Cloud provider. Let’s go back to the Lifecycle Manager application and check out Azure. Okay. We should see there is multiple instances available or being triggered and the latest one was 259, like we can see here, which tells us that Azure was picked because as a policy of the organization, anything in North America should go to Azure. It looks like we have successfully provisioned something on the Azure side.

Ankit Bhansali • 24:49

It comes back with a set of attributes which are Cloud-associated, not the request or the product-associated. Now you get a separation of using the Cloud provider you want and you get the flexibility to interact with the Cloud provider the way you would like. Because in this case, I’m nowhere defining. If you saw, I’ve not picked OpenTofu or a Python script. Everything is under the hood where we have focused on service abstraction rather than focusing on how to interact with technologies.

Rich Martin • 25:23

Got it. Got it. That’s excellent.

Ankit Bhansali • 25:27

Now, we see that all these attributes have come in here already. Let’s go and verify that on the Azure site. To be consistent, we should be able to see a virtual machine, a virtual network that’s recently created, a new resource group that’s associated to that VM, and any subnets that are associated with provisioning that VM. I’m going to go into Azure. I’m going into all resources, and I’m going to copy the name which we provided. If you can see, this is my virtual machine. It’s provisioned in East US, and again, it’s in Azure.

Ankit Bhansali • 26:04

All other attributes of these VMs have been pre-configured. I’m deploying in Ubuntu 18.4, which tells you that if you have standardized this concept from not just the technology standpoint with the service abstraction, now the experience for the user is very seamless, because we can send them an e-mail with the right IP address. They can SSH too, and we can offer any additional services that will close the gap in terms of start consuming this VM. That gives us that flexibility in terms of provisioning. But I’m sure you are not that much thrilled, because a lot of folks can also do this in terms of provisioning new VMs. But the real value here we get is how do we provide additional services without having to spend a lot of time in building new use cases. From a create or a provisioning purpose, it’s going to be a one-time thing.

Ankit Bhansali • 27:00

But how about we add a new action, and let’s say provide a new service in terms of changing something on this VM from a firewall rule perspective or changing the load balancer. I’m going to go into global VM provisioning because firewall is outside of open TOFU or Terraform that’s being used, the infrastructure as core concept, because that’s part of the orchestration and the end-to-end concept. I’m going to go into this demo VM, and we can see in the property section, we have load balancer, Cloud provider, and the firewall rule. I’m going to change the load balancer. I’m going to offer a service to all global VM provisioning in terms of having the ability to switch load balancer as required. I’m going to go in here, provide a service called Advanced Load Balancer Service. And it’s going to be type modify.

Ankit Bhansali • 28:00

So, when I hit save. and hit global provisioning now, I have this service available to folks in terms of how to consume this. If I go to instances and click on Demo 1, now you can see I can not just change load balancer, I can even switch load balancer to a different name and a process if required. This gives you that ability to start having these add-on services and you can go to market with new services that provide revenues to your organization.

Rich Martin • 28:32

In this case then, we get the advantage of being able to track changes over time, your day 2 to day n, but also being able to add additional services for the product that they’ve ordered. You’ve built this here, so eventually this could make its way back into a ServiceNow request or a catalog entry, where they could take the services they have and then make the modifications that they need. Now, that saves teams a whole lot of time, because who’s doing that if you don’t have this product mindset and the technology behind it? We’re all doing that. We’re all figuring out, we’re all the pieces to this puzzle that we’ve created called a service or a product, trying to make those changes drastically as quickly as possible. But by tying all of these things together in a nice little package, we call it product, in an instance, and tracking that data, not only is it easy to find, but it’s easy to automate for the actual end-user to manage their own product.

Ankit Bhansali • 29:36

Yes, absolutely. And you also get to keep the transition that’s going to happen on this product over a period of time. So you can actually see changes that have affected this product and you can track them in a nice red and green way where you can see the initial state of the product. You added some new service changes or you offer different products. You can now track them without having to lose the context of what a product is for this customer.

Rich Martin • 30:07

Right. And, you know, we’re only doing this for one instance, but I think the real thing that we really need to take a look at and help have our audience imagine, imagine this at scale, imagine this being a problem at scale. And maybe you’re already experiencing this problem at scale, which is why so many customers are now coming to us saying, how do we do this? This is the thing we want to do. Perhaps, you know, this definitely takes some clues from the service provider world, but really enterprises are looking at doing this too, because not only is the end user experience better, but they’re also the internal management of all of your resources, of each individual team that’s building the automations to make changes on the network. This is actually much more beneficial for them in the long run, if you think about who really gets more advantage out of this.

Ankit Bhansali • 31:00

Correct, so there’s two main points. One, you’re simplifying it from a product standpoint, again, going back to that, but the other point you just made, right? The scale factor, like if you imagine you have 10,000 services running right now, imagine you had to do a global migration of those services, right? Not just migration, what if you want to introduce something new to all those services as a compliance policy? This is where things can become really useful because we know customers will have hundreds and thousands of services if they start doing this from a product standpoint, but we also provide them the ability to group these kinds of products so that they can apply global changes on these products that can be very easy to maintain and execute across your portfolio of services.

Rich Martin • 31:46

Right, so to your point then, when you just added something that did an update, that was able to do an update to an instance or multiple instances, maybe a group of instances, you could add something in like, when was the last time compliance was checked across this infrastructure? And we’re not just talking about firewalls and network devices, but we’re also talking about what else? Systems?

Ankit Bhansali • 32:11

systems auto-decommissioning with expirations, because there is Cloud cost money just so you know. That’s the biggest concern all customers had. I do not want these provisioning of these VMs on Cloud, just sitting there without being tracked from an expiration date. I want to make sure every VM is available for training purposes for seven days. After seven days, I want to make sure I decommissioned them automatically with an expiration date associated in the provisioning of the product, and make sure the resources are again freed up from the IP addresses, the firewall rules, and other components that might be part of this orchestration. Decommissioning, a very important concept, auto-decommissioning from expiration date. Again, to your point, running compliance, because Itential is in a unique position where we do not just run compliance on your native network infrastructure.

Ankit Bhansali • 33:07

We run compliance on your API-based controller infrastructure. We run compliance on Linux and Windows machine from an operating system standpoint. You can mix and match and make sure not just this service is healthy, but to have routine compliance. a system check’s been placed so that it’s in compliant with the standard policies, which will always change over time based on the vulnerabilities that are being exposed to the network.

Rich Martin • 33:35

Yeah, I think that’s something you and I should probably revisit at a later time is being able to take a product instance and then add something like compliance to both the VMs and the underlying infrastructure that supports the VMs as well, to more of a holistic service that now can be applied and attached to each one of those instances. Imagine the ability to report and identify, not just from one person’s domain. The Linux team says they’re completely secure. They’re all up to date. What about the app team? What about the network team? What about the firewall team? Each one of those is a part of this holistic whole for this product and ought to be treated in the same way. We should be making sure all of this infrastructure stack is compliant, not just one of them.

Ankit Bhansali • 34:25

Yeah, that sounds beautiful and I’m sure our guys who love making sure, especially on the cybersecurity side, they would love to have a compliance, not just on, to your point, a single domain, but compliance on the service itself, which is, again, we are encouraging people to bring their own tools, their own methodologies, but from an organization standpoint, they need to have that standard single point where they can interact with and run compliance across anything that’s under that service. So I think that you bring up a very important point in maintaining the health of the service, especially when it’s that disparate and that different when how people are interacting and consuming these kind of concepts.

Rich Martin • 35:09

Well, that’s awesome, Ankit. Thank you so much for the demonstration, walking us through what this looks like and how it works and how it can help, again, not only to deliver the services to the end user to make them super happy, right? But also how this makes all of the domain teams that are part of creating these products, making their lives a whole lot easier.

Ankit Bhansali • 35:31

Absolutely. Thank you for having me.

Rich Martin • 35:34

With that, we want to thank the audience for tuning in. If you have any questions, feel free to reach out to us. Our information is right here. Ankit, once again, thank you so much for your time and your expertise in this.

Ankit Bhansali • 35:47

Yeah, absolutely. Thank you for having me. Had a blast.

Rich Martin • 35:50

All right. Thank you. Bye-bye, everyone. Yes.