Ask Us Anything: Episode 15

Rahul

Hey, everyone. As you can see, we have a new location and we’re in the same room, which is very unusual.

Rahul

The same continent. In fact, we happen to be in Anaheim, California for the Summit. A lot of exciting stuff happening over here. So if you happen to visit the Summit here in Anaheim, please come to us, we’d love to catch up. And yeah, exciting talks planned.

Rahul

Yes.

Rahul

We have a lot of very, very fun stuff planned for the entire day tomorrow. So yeah, looking forward to meeting some of you who can join us over there. But we have an interesting lineup.

Rahul

A lot of traveling, in fact. I didn’t realize that the flight all the way from India to L.A. was that long. I haven’t flown directly to L.A. So I flew by Dubai. And that was nearly a 16-hour flight. I think it’s been a while since I’ve done that long. So yeah, that’s interesting. And got through an entire book during the flight, so that is pretty good.

Rahul

Yeah.

Rahul

Yeah. So yeah, it was good. I actually got some good reading done on the flight. And, yeah, I’m just hoping that you don’t see me going away during the session. I’m still jet-lagged. I just came last night. But hopefully, we’ll get through this. There’s so many things we’re gonna talk about.

Rahul

How was your weekend?

Rahul

Nice.

Rahul

Yeah, I remember these used WAX [SP] cables, right?

Rahul

Yeah, I remember doing this coaxial and setting up [inaudible 00:14:00] network with these chips. Yeah, that’s pretty cool.

Rahul

So I just found it funny that AWS 5G is really 4G. That was definitely interesting. But as I was getting through this, I was trying to understand where we were using this. So radio right now supports 100 SIMs, okay. And I think a lot of the use cases, the data out are about IoT in manufacturing use cases. But if you really think about it, you need an internet backbone somewhere in radio.

So you’re gonna have the internet backbone anyway, and you have a manufacturing unit. Wouldn’t Wi-Fi just be easier? And you could use Wi-Fi as much as you want across the setup. Or if you had multiple, you know, locations spread, then you could use any of the ubiquity hardware or [inaudible 00:15:49] or whatever, to this point [inaudible 00:15:51] over a radio signal, and then have Wi-Fi locally.

So I’m still struggling a little bit to understand who uses this, what, which customer. They haven’t put out a use case yet, which actually will really help to understand the use cases. I know that Amazon doesn’t build anything until it is a customer use case. So I would love to know who is actually using this and why. Also, when you look at pricing, this is pretty pricey, right? I mean, it’s about $10 an hour, if I’m not mistaken.

Rahul

It’s almost 90k.

Rahul

That’s about 90k a year to set up 100 radio devices, 100 [inaudible 00:16:43] points. That’s not much. With 90 grand, you could have state-of-the-art Wi-Fi all over the place. You could wire up every IoT device if you needed.

Rahul

Yeah, I think, I mean, that is one aspect to it, which is, this just seems really simple to set up. So if you are a provider who is trying to set up 5G, you know, something like a VNR [inaudible 00:17:50], this might be easier to get there. But yeah, I’m not entirely sure why or how someone uses it. It is really easy to set up. So you probably get that telco set up in a week with, you know, far less expense. And the time bucket is key, so you could probably do that. Right now, you have to piggyback on one of the, you know, service providers.

So [inaudible 00:18:20] that if you wanted to just [inaudible 00:18:21] from scratch without [inaudible 00:18:23] you could just get a big pipe of internet bandwidth and provide your own services to whatever [inaudible 00:18:30] you want. But that every radio only supports 100 SIMs, that seems like a limitation [inaudible 00:18:38] of that and the price. I’m not sure.

Rahul

Yeah, you would have a fixed number of, you know, IoT devices that are running on this. So again, I’d like to know what the real use case is or who the customer is that this is for.

Rahul

Sure. Wi-Fi is across all devices [inaudible 00:19:29] today.

Rahul

I’m scratching my head. Yeah. So I think if I were to score this one, we’ll score it on one to five on content, right? I think I’d give this a two, simply because we still don’t know where and how to use it.

Rahul

Yeah. The other thing that I would actually like is for them to have stated very clearly what the problem statement was. Right? When you look at every other AWS service, there’s a problem statement that that service tries to solve. Here, [inaudible 00:20:43] deploy 5G network. But why? Why do you need to deploy a 5G network, is something that I’m really confused. I know it takes a while. So is this meant for telco providers? Is it meant for [crosstalk 00:21:00]?

Rahul

But Wi-Fi does all of this. Like, why is Wi-Fi not the right [inaudible 00:21:17]?

Rahul

Because at the end of the day, there’s an internet backbone that supports this. You have to plug in your [inaudible 00:21:35] and plug it into the [inaudible 00:21:39]. So all your communication is going through that network. So why 5G and not Wi-Fi? That’s what I’m really confused about.

Rahul

Yeah, we don’t know the use case so it’s hard to say. We don’t have a use case to say, it makes life easier. Right now, I think given the [inaudible 00:22:17], the fact that we don’t understand it, [inaudible 00:22:23] a little bit.

Rahul

Yeah. So I think leave it open, and we’ll try to get more clarity from the AWS team. And it’s good that there’s gonna be the Summit, so we’ll probably catch someone tomorrow or today, and see if we can get this question answered.

Rahul

Yeah. To be honest, it’s pretty confusing. So you have the R family, you have the R5, which are the old Intel processors running at 3.1 gigahertz. And you have the R5as, which are the AMD family of processors. And then you have the R5b, which are the latest generation Intel instances, also running the latest generation Intel [inaudible 00:23:51] that are running at 3.1 gigahertz but peak to 3.5 gigahertz. So that’s pretty interesting.

But at the same time, you have the R6 family already there. So you have the R6as which are the latest EPYC processors for AMD. And then you have the R6g, which is the Graviton-based processors, right? And if you look at the price difference, the Intel ones, that is the R5 and the R6…I’m sorry, the R5b, are both about 20% more expensive than the AMD family. That’s the R6a as well as the R5a. I’m already getting very confused as I talk about this.

But the R6g, which is the latest Graviton processor, is about 40% cheaper than the R5b, which is the latest one that Intel [crosstalk 00:24:49].

Rahul

Correct. I mean, it makes absolute sense to just stick with the Graviton processors for RDS. And though, I’m not entirely sure if the SQL server specifically runs on the R6g.

Rahul

Correct.

Rahul

But there, the answer should basically be, I’ll have to check whether the SQL service will run on the Graviton processors. I doubt that they do. But at least the R6s, should run. There should be no reason to run the R5bs anymore. Because the R6as are already faster and, you know, cheaper, about 25% over the R5bs. So I don’t know why people would wanna use more R5s.

Rahul

So the i instances are mostly about IOPS, okay? Now, [inaudible 00:26:01] need tons of IOPS [inaudible 00:26:04] memory. What happens to the database is you wanna take all of the stuff that’s in there, load as much as you possibly can into memory. And then, your [inaudible 00:26:13] operations are relatively straightforward because they just [inaudible 00:26:17] indexes in the data and pulling it out, right?

Rahul

So the CPU operation is relatively light when it comes to databases. It’s mostly about your disk IOPS to load stuff into memory, and how much memory [inaudible 00:26:31]. Now, the funny thing is that especially with SQL server, there’s a history where tons of products have leveraged, historically, [inaudible 00:26:47] procedures.

So they’ve used these databases almost like compute, and I think that’s where the big problem lies. They stopped using the database like a database. They use it like an app server. There’s a lot of business logic kind of shoved into those databases. And I think that’s the wrong approach. I don’t think you should be doing that with databases. They were not originally designed to do that. There’s tons of hacks that have gone in.

You want your database [inaudible 00:27:13] as light as possible in the relational model and keep the logic outside. Today, you don’t have any other tradeoffs to be made, whether it be at work or, you know, CPU or IO. You can get all of them out of the database.

You know, back in the day, you had to move 10 [inaudible 00:27:30] out of DB into your app server. You would think twice. You know, you would really question how you’re gonna get that because the latencies were crazy.

Rahul

Correct.

Rahul

Yeah. Well, that’s [inaudible 00:28:32] inability [inaudible 00:28:34] just untenable in the long run. I mean, I’ve seen products with [inaudible 00:28:38] and you don’t know how to deal with it. And migrating to newer versions becomes hard. Migrating off of, you know, the extensive licensing into more common databases is incredibly hard because the business logic is [inaudible 00:28:54] over there and you don’t know how to deal with it.

So yeah, it’s a really tough space to be if you have tons of stored [inaudible 00:29:06] there is the more flexibility using the database itself for its core operation. If you look at the instances that we have, all of these instances have 12.5 Gbps at least, in terms of network bandwidth. Some of them have over 30 Gbps. If you look at R6i [inaudible 00:29:27], they use 37.

Rahul

Yeah, all the way up to 37. The R6i.metal goes up to 50.

Rahul

You can get your data. I mean, the network is no longer constrained like it used to be, you know, even just a year or two ago. So yeah, stored procedures, I think it’s one of that bad practices that has come in with the relational developers and has stuck on.

Rahul

True. So you wanna get rid of as many of the stored [inaudible 00:30:32] as possible and move them into a business logic that you can manage, maintain. Just make your life easier. Keeping them in stored [inaudible 00:30:39] isn’t tenable in the long run.

Rahul

Yeah. I think so M6i, R6i completely make sense. Definitely [inaudible 00:31:05]. The one point I would ding for is the R5b because I don’t understand why you would want to launch the R5b. The R6a should be a better option for a SQL server.

Rahul

Yeah. R6a is already there. R6a was launched some time ago. And R6a is 20% cheaper than the R5b. It’s already the next-generation EPYC processors. It is [inaudible 00:31:39]. It’s just not Intel. And your RDS SQL server should run just fine on that. So why wouldn’t you use R6a against the R5b?

Rahul

Yeah. There’s nothing.

Rahul

Yeah, I’d give it 3.5. Do we have a half? No, [crosstalk 00:32:32].

Rahul

So you give it 3.5 clouds. Okay.

Rahul

So the interactive video service is really cool. Think of the interactive service as taking a live stream, and then adding or embedding that with a larger application that can do interesting stuff with that live stream. So, you know, for example, if you were doing a sports broadcast, you have your commentary and your live broadcast going on. But at the same time, imagine being able to present all the stats or predictions about what’s going to happen in the game, doing all of that live, as the video stream is coming. That’s incredible. That’s basically what the IVS service is all about.

We use IVS. In fact, we have to demo this, and it works better when there are multiple [crosstalk 00:34:38]. So once I’m back in India and broadcasting from there, we’ll definitely do a demo session. I think that’s a pretty cool. So what we have done with IVS is we have a lot of meetings that we do in the organization, you know, when you have a few thousand people [crosstalk 00:34:57].

Rahul

Yeah, completely remote. These [inaudible 00:35:01] are a big part of our organizational knowledge and organization knowledge base. And one of the challenges of remote, as we all know, is when we’re in these Zoom calls or a Chime meeting or whatever, ends up monologue, people become disengaged. And the speakers usually have no idea about engagement in the audience. You know, you can have somebody drifting away and doing other stuff.

So we’ve created a little IVS, you know, solution, which takes our Zoom and Chime meetings and so on, and it does real-time live analysis of what’s going on in the meeting.

Rahul

Correct. It uses Comprehend to understand what the conversation is all about, so you can search for it later, if it’s recorded. You can search for it. You can, you know, figure what the meeting is about, and you go back to it. You can refer to it based on the keywords that [inaudible 00:35:58] finds in the topics [inaudible 00:35:59] finds.

Of course, you can train it with custom vocabulary like [inaudible 00:36:04]. So you can do all that stuff with it. The other thing that it does is it also uses video stream recognition. So it looks at, you know, facial sentiment, so whether everybody’s confused, disengaged, happy, or angry, or agitated. We wanna make sure that we are…you know, that the feedback comes back to the speaker. And, you know, generally, as part of the [inaudible 00:36:31], understand the audience and what kind of a mood.

Rahul

Great. And engagement is the biggest challenge of remote work. So, you know, one of the other things that’s really hard to figure out, we rely so much on body language, that kind of feedback. You just don’t get that in Zoom, or a Chime meeting or, you know, whatever mechanism you’re using for remote operation.

So we are trying to use IVS and AWS information and a bunch of other tools behind the scenes, to figure out, you know, whether people are engaged or not. By the way, another kind of conversation that is not very engaging is the one where you have one literally in the monologue. If you have 10 people who are just literally staring at a screen, that’s not an engaging conversation. That’s not the kind of conversation you want to encourage within an organization.

So you want, you know, everyone to interact. That’s the whole point of these meetings. If it’s a monologue, someone should just record it and post it. You shouldn’t be having a meeting wasting everyone’s time on it.

Rahul

Yeah, it also has an application in all of our DEI [SP] efforts. Like, inclusion is a big part of what we’re trying to do. And when you’re in meetings and only one or two people are interacting, you know, as a speaker, you’re so focused on weighing your view and your vision or whatever else and you miss out on the fact that one’s interacting. And if you’re, you know, IVS dashboard shows you that, “Hey, this person hasn’t interacted, you should engage proactively with person A and C.” And as per your communication, your messaging, you can actually ask that person the question and say, “Do you have any questions? Do you agree with this or not agree with it?” And it really helps with making sure that the conversation is a lot more inclusive.

And it separates out two modes of communication. One is a meeting where you want everyone to collaborate and work together. And the other one is a broadcast where you should record your views and put them up, and people watch them asynchronously and comment on it or whatever. By the way, we have an interesting solution on that also, we can probably bring that up during one of the sessions.

So we do these little snippets of videos we record, and we allow you to review them [inaudible 00:40:39], recommend them. And that’s really easy to communicate in a more natural manner than having to write these long documents. So yeah, it’s a very interesting platform. So the fact that now it can support in full HD, that’s pretty awesome.

Rahul

Yeah, by the way, the oldest video conferencing equipment that I ever had was this one megapixel. And I don’t think we even had a P associated with it. I’d have to work out what that would be. But it would typically…it was just a one megapixel [inaudible 00:41:52] device that sat on top of a CRT television, and you connected it to your CRT television for video out, over those analog cables.

Rahul

Yeah, it was pretty expensive. And it had those analog cables that would connect in to your CRT televisions.

Rahul

Exactly, [inaudible 00:42:13] cables. And then you had your ethernet into it. They would connect in to your internet connection. And then your only connect point, IP to IP.

Rahul

So picture it and that stuff, you know, was simple enough for you to navigate through it or set up port forwarding and solve all of the issues. So that you actually connect point to point between those two [inaudible 00:42:40].

Rahul

You had to manage all of that. It had no mechanism for doing any of that stuff. And from that, we moved to [inaudible 00:42:51] by Logitech I think at one point in time. I think over the years, we started remote work back in 2010. 2008, the conferencing was in its infancy. Nothing like what we have today. So I’m glad that we have full HD [inaudible 00:43:15]. If we can do [inaudible 00:43:16]. Are we broadcasting in 4k here?

Rahul

Yeah, and we are sitting in a hotel room, in a makeshift, you know, setup.

Rahul

Absolutely.

Rahul

This one is relatively simple and straightforward. So I think in terms of content, it definitely simplifies. In fact, more than simplifies it, it actually makes the service more useful in the current context. And yeah, I would rate this a four or five.

Rahul

Yeah, this is pretty straightforward and simple.

Rahul

Yeah. I think Config monitoring and management is insanely complex. I mean, take a look at the first one, the routing table, itself. So let’s say you have an organization giving its course.

Rahul

Yeah, that’s the previous one.

Rahul

So take a look at the routing tables, for example. You know, we have about 30,000 AWS accounts and with a very, very complex routing scheme across all of those different VCs and all of those different accounts. And these routing tables get pretty darn long.

Rahul

And you [inaudible 00:46:14] that there isn’t any drift that happens in configurations. Let’s say there are some servers that [inaudible 00:46:21] TransitGateway. You don’t want that unless it’s authorized, right? You want the table to open that Config changes. You want the version, you wanna set Config for a particular server, a particular device, for a particular [inaudible 00:46:34]. You wanna make sure that the changes that are happening in the configuration are controlled and you don’t have random services and API making those changes. You want to detect them, you want to act on it.

So I think having more and more support for detecting these kind of configuration changes is incredibly valuable. You want to get an alert whenever it happens, and you act on it. In most cases, you are going to basically revert. So for any organization that is centrally managed, you want to be able to revert any change that happens as it happens [inaudible 00:47:11] configuration management system.

Rahul

So you want to immediately, even if someone has admin permissions to a local [crosstalk 00:47:19].

Rahul

I think it’s a little more basic than that. You might…somebody [inaudible 00:47:37] operating and it’s too restrictive. So because they’re an admin, have access to that particular account, they go ahead and open up a port.

Rahul

Or they open up the network to other traffic that’s coming in, just to make their lives easier. Like, I’ve seen so many people [inaudible 00:47:56] their security groups [inaudible 00:47:59]. And that’s a terrible idea. You don’t want people to create, you know, [inaudible 00:48:08]. And override it locally. So at the AWS organization level, you have a configuration already set. Anytime you make a change in the Config, you get an alert. And then act on it and write something back.

Rahul

Exactly. And if we look at a set of these services, right, the other mechanism which configures use a lot is version control. You wanna make sure that you don’t haphazardly update or hold back versions of configuration across all of these different systems. Whether it be your Notebooks, whether it be your data club, you wanna keep control over all the versions. And in this Config app, you manage all of that.

Anytime you see that change, you get an alert, and you can go ahead and roll back or manage the version accordingly, okay? You want all of these…when you want better control over people randomly changing stuff, Config is the service you go to, to make sure that things are not kind of happening very haphazardly.

Rahul

Right now, look at all the different places and all the different points. I would say just short of 50 is my guess. I don’t have the full map, but I’d just say just short of 50%.

Rahul

Correct. Yeah, I think it’s pretty good. I mean, there are a bunch of services that are always playing catch up to the main service deployments.

Rahul

This is gonna be one of them, right. [inaudible 00:50:34] endpoints is the one where, you know, this comes out first, then you come out with the [inaudible 00:50:38] endpoints. You wanna roll out the basic services first, and all the other [inaudible 00:50:43]. Like, [inaudible 00:50:46] from the standpoint across all of these different, you know, services. It just takes them time to get those things plugged in.

So yeah, I’d say the Config always plays catchup. But I think they’ve made good progress.

Rahul

So I would say this is a good 4.5 to 5.0 because it’s pretty clear and obvious.

Rahul

Right. The traditional way of doing this was that you would have an event where something went down, or some configuration is a problem. And then, you would say, “Let’s go look [inaudible 00:51:54] to figure out who accessed this API to make changes to this particular service.” And then you will dig. And then you will go back to the person, and then you would know, you know, what config to bring back. And it would be [inaudible 00:52:06].

So [inaudible 00:52:07] in real time.

Rahul

Exactly. So this gives you much tighter control for that kind of scenario.

Rahul

They recommend to you a spatula or whatever, depending on what you bought. You know, typically, when you buy something, it says, “Other people who bought this also bought these particular items.” So depending on the parameters that are provided, the recommendation engine will give you a bunch of recommendations. You decide how many you want.

Rahul

Yes, yes, I’ve had some bad recommendations [inaudible 00:54:00] just look at the Amazon Store. Based on the stuff I usually buy, the recommendations are almost spot on. Like, especially when I’m buying groceries and stuff like that. The more data that the system has about my interaction with the Amazon shopping carts and so on, the better the predictions get.

Rahul

Like, once it realizes that I’m ordering something every month, it says…it recommends that make it a monthly order, rather than make it, you know, an ad hoc, you know, one-time thing. And it recognizes all of those patterns pretty intelligently. So AWS Personalize is really awesome in that sense, from that standpoint. And I think the very first episode we did, the other podcast, AWS Insiders…by the way, that you can find on awsmadeeasy.com as well. We have our very first…

Rahul

Yeah, it is on awsmadeeasy.com as well. So find that podcast there where we talked to Ankur Mehrotra, the GM of AWS Personalize. There you go. So go to that one. And the very first episode, we talk about AWS Personalize. It’s really very cool. A lot of very interesting scenarios.

What I like about this particular announcement is that [inaudible 00:55:30] things to do is when you have a set of recommendations, you want the recommendations to, A, be stuff that the engine finds. But somewhere in there, you also want to recommend things that you want to push like promotions. Right? These are things that you want to push to all users irrespective of what the recommendation sets are.

And that has historically been hard because you get a recommendation set and you have to figure out which one of those five or six items you want to eliminate to insert one of your promotions. And then how do you figure out the distribution? Do you promote the same stuff to all of your users? Or do you promote it only to a set of those users? So this system really helps you solve that problem where you can say, “I want 20% of the recommendations to have all the [inaudible 00:56:21] items to go to all of these users.”

Rahul

And so it’ll embed those inside recommendations based on also what is relevant to them. So you can say 20% of the recommendations should be stuff that I want to push, right? And the AWS Personalize will take care of that for you. It’ll still seem like all very relevant recommendations and the engine takes care of all the complexity for you.

Rahul

I mean, one example, I think I read a case study some time ago, where if you are buying baby products on Amazon, they always have a diaper in the recommendation. As far as I know, Amazon has never made a profit on the [inaudible 00:57:48], if I’m not mistaken, at one point in time. But it’s just such an essential part of the shopping experience. Like, if you don’t shop for diapers on Amazon, you would probably not buy the other products over there. So…

Rahul

Exactly. So they would look for it, and this is a mechanism that allows you to do that. And it’s not just retail. I think there’s a lot of application in any kind of content that you’re serving out to individuals, whether it be news, whether it be movies, whether it be music. In all of those scenarios, you have a situation where there’s a new show and you want to recommend a show.

Like, if we were to have a recommendation engine for someone visiting our AWS Made Easy site, we’d have to do a top five. Then in today’s show, we would push AWS Personalize and all the content that we have around Personalize. Because that’s what we’re talking about. Right? That’s something new, that’s a new announcement. So you can push that content.

Rahul

Right. Or any new releases, like a new movie just released or [inaudible 00:58:59]. They always have it part of the recommendations. So yeah, I mean, this makes life easy for anyone who is doing tons of recommendations as part of their application without having to manage the complexity of how to present all the data and inject these recommendations in the middle of other standard, you know, [crosstalk 00:59:24].

Rahul

Exactly.

Rahul

So I think would I really love for something like this is, like, the [inaudible 01:00:04] article that we reviewed in the beginning where there’s a step-by-step process of how you set this up. Having that step by step, you know, here’s how you do it in the console, here’s how you set up a new rule, that would have been really neat. Of course, this is fairly intuitive. You could probably just go to the console and figure it out. But from a content standpoint, I think having that would have been really useful.

Rahul

I think it’s a 3.5.

Rahul

Yeah, 3.5 seems good.

Rahul

We’re gonna make the clouds grey, I think. Or put in an Amazon, you know, a yellow or orange, whatever the shade is.

Rahul

The orange border around the cloud.

Rahul

In the standard catalog.

Rahul

This is the on-premise thinking for a cloud service.

Rahul

But I’m glad that they’re changing that.

Rahul

Yeah. I think so right now, for the inference [inaudible 01:02:55], they are using a lot of the Intel chips. But they’re working on their own Inferentia [SP] process as well. So I foresee that this price will go [inaudible 01:03:07] and move completely into serverless, where hopefully, we’ll never have to worry about, you know, setting up machines or inference units. And so it takes care of itself behind the scenes where you have one rate and you get charged on a per transaction basis. I think that’s the way to go.

And I have no doubt that AWS will get there. Right now, they use a whole lot of Intel-based inference engines or inference processors. And they have their own new Graviton-based Inferentia [inaudible 01:03:37] Inferentia. Yeah, it’s only a matter of time before most of these will turn into a serverless setup with all of it going to Inferentia.

I think it was in [inaudible 01:03:53] that they announced the work that they were doing on the Inferentia chip. It’s available today. I just don’t think it’s rolled out with enough capacity.

Rahul

Right.

Rahul

I think with any inference model, there are three dimensions of tradeoff. One is, what is the cost of training your model? Okay, but that’s not so much on the inference side. That’s more on the training side. But second is, what is the latency of the results and what is the accuracy of getting these results?

Okay, so, for example, you might be okay with the machine-learning accuracy being 90%, or confidence levels being 90%. You want the back under 100 milliseconds. But in other cases, you might want that level to be 99%. But that might take you two seconds to get that results.

So the workload is a function of not just the latency so much, but the latency and accuracy because that’s how much compute you will probably need [crosstalk 01:05:35].

Rahul

Correct.

Rahul

We’re still talking about hours to do this.

Rahul

I completely agree. It’s not consumer ready yet. It’s still, you know, like, I guess we find the people are using the mechanism of detecting defect in, let’s say, chips that you’re shipping [crosstalk 01:07:00].

Rahul

Correct. And you wanted it to run through defect detection on 10,000 [inaudible 01:07:09] and so on. I think it makes sense in those scenarios. But it’s still not quite commodity grade for some of the uses where you’d want to use it.

Rahul

Yeah. Like, if I wanted a content recognition, you know, mechanism that looked at all of my PPTs and extracted a bunch of data from there, allowed me to search through all of my PPTs or PDFs and stuff like that, this would not really be the mechanisms to look at all of those pictures.

Rahul

Yeah. So but it’s heading in the right direction, moving from just seeing what your [inaudible 01:07:59] is gonna be or your maximum capacity, moving to auto-scaling, definitely a step in the right direction. I’d love to see the [inaudible 01:08:08] second ideally, followed by serverless, where you run that…where it’s transaction based.

Rahul

[inaudible 01:08:21], yeah.

Rahul

And I think I’d give this a three. Three seems like a score that fits this particular [crosstalk 01:09:02].

Rahul

There’s a lot of interesting stuff that’s come out in the last week. There are a bunch more announcements, but I think this is just about the time that we have. So coming back to the event we have at hand. We have the AWS Partner Summit that’s currently being held here in Anaheim, California. If you’re around, once again, please come and say hi. We’d love to interact with you. We’d love to know what you would like to know so that we can bring that into our future episodes.

And I will be doing two talks tomorrow. One is on how you can systematically do a 50% cost savings goal with whatever cloud bill that you have. The second one on why you should not really own code anymore, and why code is a liability.

Rahul

We will have a long discussion about that tomorrow. So yeah, really excited to do that tomorrow. I look forward to seeing some of you here in Anaheim. And yeah. We’ll have a great show tomorrow.

Rahul

Thanks, everyone. It’s been awesome.