WEBVTT
00:00:18.460 --> 00:00:52.929
Hey folks, welcome back to Serverless Craic!, We're back after a short break, and we're good to go again. So I figured we'd do something slightly different for this episode. I think we should talk about the Serverless Developer Relations or the DA team at AWS. I think it's probably a good thing to talk about and reflect on. But firstly we are just finished ServerlessDays Belfast which kept us busy. Do you have any reflections on the event.
00:00:57.520 --> 00:01:58.840
First and foremost, Dave, congratulations to you and the team that organised it. I thought it was really well organised. The Titanic theme, Titanic Hotel area and the engineering history of Belfast made for a really good atmosphere. And it was packed out. I think the big thing I took away is that there's way more adoption. And the level of the talks and interactions and experience of the people there seems to be very high. And I'm not just saying it because we were there or because it was local, or whatever. I really came away with a book of stuff. There are five or six things that I genuinely wanted to take back and look into. The quality of the speakers was very high.
00:01:58.870 --> 00:02:01.269
Really good event!
00:02:01.000 --> 00:02:03.549
I echo all of that.
00:02:01.000 --> 00:02:07.569
And it was very slick and a great venue. But there was a great community aspect to it.
00:02:07.989 --> 00:02:34.120
Lots of people and conversations with everything from beginner all the way up there to seasoned experts, having a good and meaningful conversations. It's not just the talks but the conversations on the side and the venue helped a lot with that. Great day and really impactful. Anyone who was there got a lot out of it and there was a buzz and energy. It was a very successful day, so well done!
00:02:34.090 --> 00:03:08.753
Thank you both. I didn't ask you for a lot of praise, so I probably should rephrase my question better! ServerlessDaysBelfast.com has all the details and content, and we'll be publishing videos of the talks soon. But I really enjoyed the event. The theme was'Building Beyond Boundaries'. We wanted to raise the bar and use the story of the Harland and Wolff Shipyard and Titanic. And the fact that Titanic was built in Belfast 120 years ago.
00:03:04.723 --> 00:03:57.415
Something like 1500 ships and ocean liners have been built there. So it was a centre of engineering 100 years ago. It was great to bring that back around to what we do. People were inspired to hear the stories of what happened then versus what we do now. It's a community event as well. So it's good to just bring everyone together to chat. And related to today's topic. it's very hard to measure that. You get 200-300 people in a room talking, learning, enjoying themselves and getting a bit of a spring to their step. It's very hard to put $1 amounts on what they bring back into their teams. It costs £60 per ticket and a day off work which is not expensive.
00:03:52.799 --> 00:04:01.960
But what you get from that, as an engineer,when you go back to your office is off the scale.
00:04:03.879 --> 00:04:24.970
There are low barriers to adoption of what you hear or learn about at ServerlessDays. You may hear about a company adopting step functions, for example, and you can take that away and try it.
00:04:19.300 --> 00:04:37.750
There's no big licencing, installation or outlay of expense required. You can act on wondering if that'll work in your context, company or for the problem you are trying to solve.
00:04:33.519 --> 00:05:06.939
So the feedback loop from the content, speakers and great ideas and you applying them to your ecosystem, context and company is tight. It's hard to measure the impact that those little nuggets of wisdom have on junior or even well seasoned engineers. They'll take lots away and apply it to their business. And you may not ever hear how successful it was.
00:05:13.209 --> 00:05:18.610
I have a bee in my bonnet about people saying they're brilliant engineers.
00:05:15.220 --> 00:05:34.000
Brilliant engineers are curious and learn from other people. If you put a brilliant engineer in a silo and ask them to build by themsevles, they'll probably mess it up. You've got to have a curiosity, look outside your space and get influenced and inspired by others. That's how it works.
00:05:34.389 --> 00:06:05.680
It's one of the only events I've been to in a long time, where you're seeing the next iteration of something that is coming. There were nice talks on the front end and approaches for Serverless. And then there was Jeremy's concept in terms of what he's doing at Ampt. That's certainly a different way of thinking. How do you apply that and look at things from slightly different angles.
00:06:08.990 --> 00:06:11.810
Jeremy Daly did a brilliant job with the Keynote.
00:06:12.259 --> 00:07:32.660
And what he's doing at Ampt is inspiring. He's lifting the bar, not just one notch, many notches. So it's great to see that. I actually can't stand the phrase Serverless because it doesn't really communicate what we're doing, either at the event ServerlessDays, or in relation to what we do. And in relation to the next topic of the AWS Serverless DA Team, or Developer Advocacy Team. And to give you context, there's been a couple of things on Twitter this past couple of weeks about the guys and gals from the Developer Service DA team who are changing teams. I don't want to get into the internals of AWS like but I wanted to pay tribute to a strong team, that was led by James Beswick. And before that, by Chris Mullins. And I would say over the last 10 years, we've been lapping up their content, on Twitter, at conferences and on LinkedIn. My number one resource is the people on that team, where I basically learn all the stuff that we do. Let's discuss that team for a bit and the massive impact they've had on what we
00:07:32.000 --> 00:07:32.779
They have had a huge impact and they are huge do.
00:07:36.199 --> 00:07:54.620
enablers for everything we've all done in our careers. And with the barriers that we were trying to push against, their content and the work that they did, gave us ammunition for challenging our status quo and context that we were dealing .
00:07:54.920 --> 00:08:25.009
So the external validation for our approach was coming from the Developer Advocacy Team. The blogs, patterns, examples, workshops, tutorials, or even getting some of them on calls and talking about the problems, we were having led to enablement and empowerment to try these things. And removed the barriers and friction we had. Kudos to them all.
00:08:25.000 --> 00:09:23.440
I don't know how to describe this properly and it's not meant to be personal but when you are trying to do something with step functions, and you need to know more about step functions. the sales guys on the phone will try to sell you more stuff. When you got one of the DA'a on the phone, they were able to say that's crazy, don't use that. Use EventBridge instead etc. They have you an honest answer based on their experience. So it was great to hear that unbiased opinion, they don't have any product interest, they're not trying to sell you something. It's just someone who's in the space, talks to lots of people, and they're good engineers. I find it super helpful and validating to hear their opinions on things. There were lots of times when you were thinking something and you thought 'hh, right, that's interesting'. And why did he say that? And then you realised that you were completely wrong.
00:09:23.000 --> 00:09:55.789
Amazon is a big company with a multitude of services available for teams like us to collaborate with in our day to day, and they're changing all the time. And a lot of stuff gets missed. If you're just looking through the list of change requests on a monthly basis. you can't appreciate what's changed or available.
00:09:49.909 --> 00:11:06.559
These guys do a good job of highlighting new things that come out by creating blogs and working examples to show you how these things are progressing. It makes it consumable and allows us to build. They are the engine that builds the movement and shows what others are doing and fleshes it out. Look at the podcasts they are doing and the content they produce. It's more consumable and leverageable. if you are reading it back, you're not appreciating all the things it could be used for. But when you see how someone actually does leverage it then that gets you thinking. They've breathed life into what's going on in Serverless. Julian's talk at ServerlessDays breathed life into concepts of flow control.
00:11:07.190 --> 00:11:12.230
That notation is really nice.
00:11:07.190 --> 00:11:26.450
Can we design this stuff in the abstract before we even consider services. You don't get that from reading the spec. you need the team to bring it to life.
00:11:26.929 --> 00:11:31.580
That's what they do and hopefully, that's what they continue to do.
00:11:34.059 --> 00:12:28.000
With our modernisation, migration and enablement work for organisations, we avoided undifferentiated heavy lifting by pointing towards Serverless Land, the DA team and the patterns, examples, workshops and tutorials that they provided. We didn't have to create that content or those courses, tutorials, workshops or blog posts. We were able to build on top of what they already put in place. So we were standing on the shoulders of the giants. When we were trying to transform a large enterprise, we were able to tailor the content to move ourselves up the value chain. So we're basically standing on top of the work that they have enabled us to do.
00:12:28.960 --> 00:12:47.590
Let's be specific. When we think of the transformation at Liberty Mutual it was based on the content that the DA Team were pushing out. It was validation that we weren't making stuff up. Chris Munns formed the DA Team in 2015/16.
00:12:49.690 --> 00:12:55.480
We got to the point where we were asking what is he tweeting about? What's he talking about in the articles he is writing.
00:12:55.509 --> 00:13:03.009
And that was a pretty good steer. And then as the team grew, James Beswick had solid blog posts with good content.
00:13:03.009 --> 00:13:27.850
There were lots of good conferences and different events that they ran. Julian Wood came to the first ServerlessDays Belfast in 2020. I'm remember asking him to do a talk in Liberty IT, asking him to explain what Serverless is, in plain English. He sat and just explained and it was brilliant.
00:13:28.389 --> 00:13:49.990
He has been aceing AWS re:Invent. He regularly gets recognised for the best Serverless talk. People recognise him in the street and take photographs of him. He's like a rock star. Eric Johnson is absolutely unbelievable. He has been driving so many events and he is such a good speaker.
00:13:50.169 --> 00:14:02.889
Ben Smith created Serverless Espresso and brilliant step functions on EventBridge implementations. David Boyne with all the EDA stuff. EDA visualisations are incredible.
00:14:02.919 --> 00:14:31.389
And Marcia Villalba with her YouTube channel. It is a wealth of information. The Serverless Land site is my go to whenever anyone asks about the tech. Go read that site, here's a few articles, but just consume that entire site. And then we'll talk because that's our strategy.
00:14:31.899 --> 00:14:44.110
We almost had our own internal Serverless Land with a mind map on this and a blog and the different EMP patterns all scattered around.
00:14:41.470 --> 00:14:54.039
Serverless Land brought it all together. So instead of own custom built resource, we can point people to Serverless Land.
00:14:54.000 --> 00:15:12.840
Even way back at the start, we were taking Chris Munns slides and putting them into our internal decks to drive messaging and create an environment where this messaging was slick.
00:15:29.789 --> 00:15:33.059
I've enjoyed our reflections and celebrations.
00:15:34.440 --> 00:15:54.330
There are a few other people in the team, but I'm talking about people who I personally know and worked with. They're all moving to different areas. And there's still a strong Developer Advocate movement within AWS.
00:15:44.850 --> 00:15:54.330
For me, Serverless is evolving.
00:15:55.350 --> 00:16:05.879
Ad there will always be a need for advocacy. What is hard about developer advocacy, or Dev Rel, is its measure of success.
00:16:06.000 --> 00:16:19.830
It can't be articles written or talks done It's hard to measure the impact, but I'm glad companies invest in Dev Rel, because it's how we learn.
00:16:19.000 --> 00:16:38.049
The Serverless DA Team have had millions or even billions worth of impact. But because that type of enablement is so hard to measure, they'll probably never know?How many times has that pattern being leveraged in massive companies?
00:16:38.049 --> 00:16:52.450
How many times has that blog post inspired Fortune 100 companies to build and assemble this way? How many times have those slides helped convince the C suite that it is the way to go. It's hard to get tangible, quantifiable metrics on that.
00:16:52.450 --> 00:17:03.549
But in our experience and from prolonged, anecdotal, alternate metrics, there have been big outcomes driven from the work that they've done.
00:17:09.299 --> 00:17:20.670
When I was younger I was seeing some talk, or some guy with a ponytail who sad something interesting. But I could not remember who it was.
00:17:16.019 --> 00:17:29.039
There are 1000s of people like that, who just remember seeing a talk or live stream and it set them off on a path.
00:17:41.720 --> 00:18:06.230
Last week, we were having a conversation with Julian on opentelemetry and AWS disposition and we were opinionated from our perspective. Engineers, architects and developers have opinions but we discuss it with them. And you can rest assured, they're feeding back into AWS.
00:18:07.039 --> 00:18:31.339
They take our thoughts and opinions and help shape what's going on in terms of the roadmap and progress for the Cloud Provider. They can take on critical feedback and run with
00:18:31.000 --> 00:18:31.549
I hope it continues with the evolution of developer it.
00:18:35.980 --> 00:18:44.890
advocacy in AWS and the feedback loop and shaping of product direction is still strong, and top of mind.
00:18:44.000 --> 00:19:32.299
I've had so many conversations where you ask for something and they're like, I'm not sure about that but why don't you contact the product team and explain what you're trying to do? Because they would love a customer testimonial or feature request. I'm looking forward to the content that they will continue to put out there.
00:19:24.259 --> 00:20:07.609
I'm looking forward to continue to follow them on their different channels. We can close off with the future of Serverless. I sense a shift coming. We've been about event driven architecture and EDA, recently. There is an evolution underway with some cool vendors out there, like Vercel and Momento. I find myself repeating that Severless is not just Lambdas or Functions.
00:20:09.670 --> 00:20:14.680
Do you have situational awareness? Do you know the value chain that you're trying to bring to bear here?
00:20:14.680 --> 00:20:45.940
And what is the best technology or the best solution to deliver that value chain? And for us, the model was Serverless for a long time. But as things evolve, there are new capabilities and components that you can plug in or a SaaS offering. And you may not use Lambda or Step Functions. We've been using the words modern cloud, modern cloud solutions or modern applications for a while.
00:20:50.380 --> 00:20:55.059
There's a higher level of abstraction beginning to emerge that's encompassed in Serverless.
00:20:57.579 --> 00:21:22.119
That's the craic.
00:20:57.579 --> 00:21:41.410
It is good to reflect on the Serverless DA Team. A massive thank you to the extended team for all their work. Check out TheServerlessEdge.com and follow us on X or LinkedIn hit subscribe on YouTube.
00:00:18.460 --> 00:00:52.929
Hey folks, welcome back to Serverless Craic!, We're back after a short break, and we're good to go again. So I figured we'd do something slightly different for this episode. I think we should talk about the Serverless Developer Relations or the DA team at AWS. I think it's probably a good thing to talk about and reflect on. But firstly we are just finished ServerlessDays Belfast which kept us busy. Do you have any reflections on the event.
00:00:57.520 --> 00:01:58.840
First and foremost, Dave, congratulations to you and the team that organised it. I thought it was really well organised. The Titanic theme, Titanic Hotel area and the engineering history of Belfast made for a really good atmosphere. And it was packed out. I think the big thing I took away is that there's way more adoption. And the level of the talks and interactions and experience of the people there seems to be very high. And I'm not just saying it because we were there or because it was local, or whatever. I really came away with a book of stuff. There are five or six things that I genuinely wanted to take back and look into. The quality of the speakers was very high.
00:01:58.870 --> 00:02:01.269
Really good event!
00:02:01.000 --> 00:02:03.549
I echo all of that.
00:02:01.000 --> 00:02:07.569
And it was very slick and a great venue. But there was a great community aspect to it.
00:02:07.989 --> 00:02:34.120
Lots of people and conversations with everything from beginner all the way up there to seasoned experts, having a good and meaningful conversations. It's not just the talks but the conversations on the side and the venue helped a lot with that. Great day and really impactful. Anyone who was there got a lot out of it and there was a buzz and energy. It was a very successful day, so well done!
00:02:34.090 --> 00:03:08.753
Thank you both. I didn't ask you for a lot of praise, so I probably should rephrase my question better! ServerlessDaysBelfast.com has all the details and content, and we'll be publishing videos of the talks soon. But I really enjoyed the event. The theme was'Building Beyond Boundaries'. We wanted to raise the bar and use the story of the Harland and Wolff Shipyard and Titanic. And the fact that Titanic was built in Belfast 120 years ago.
00:03:04.723 --> 00:03:57.415
Something like 1500 ships and ocean liners have been built there. So it was a centre of engineering 100 years ago. It was great to bring that back around to what we do. People were inspired to hear the stories of what happened then versus what we do now. It's a community event as well. So it's good to just bring everyone together to chat. And related to today's topic. it's very hard to measure that. You get 200-300 people in a room talking, learning, enjoying themselves and getting a bit of a spring to their step. It's very hard to put $1 amounts on what they bring back into their teams. It costs £60 per ticket and a day off work which is not expensive.
00:03:52.799 --> 00:04:01.960
But what you get from that, as an engineer,when you go back to your office is off the scale.
00:04:03.879 --> 00:04:24.970
There are low barriers to adoption of what you hear or learn about at ServerlessDays. You may hear about a company adopting step functions, for example, and you can take that away and try it.
00:04:19.300 --> 00:04:37.750
There's no big licencing, installation or outlay of expense required. You can act on wondering if that'll work in your context, company or for the problem you are trying to solve.
00:04:33.519 --> 00:05:06.939
So the feedback loop from the content, speakers and great ideas and you applying them to your ecosystem, context and company is tight. It's hard to measure the impact that those little nuggets of wisdom have on junior or even well seasoned engineers. They'll take lots away and apply it to their business. And you may not ever hear how successful it was.
00:05:13.209 --> 00:05:18.610
I have a bee in my bonnet about people saying they're brilliant engineers.
00:05:15.220 --> 00:05:34.000
Brilliant engineers are curious and learn from other people. If you put a brilliant engineer in a silo and ask them to build by themsevles, they'll probably mess it up. You've got to have a curiosity, look outside your space and get influenced and inspired by others. That's how it works.
00:05:34.389 --> 00:06:05.680
It's one of the only events I've been to in a long time, where you're seeing the next iteration of something that is coming. There were nice talks on the front end and approaches for Serverless. And then there was Jeremy's concept in terms of what he's doing at Ampt. That's certainly a different way of thinking. How do you apply that and look at things from slightly different angles.
00:06:08.990 --> 00:06:11.810
Jeremy Daly did a brilliant job with the Keynote.
00:06:12.259 --> 00:07:32.660
And what he's doing at Ampt is inspiring. He's lifting the bar, not just one notch, many notches. So it's great to see that. I actually can't stand the phrase Serverless because it doesn't really communicate what we're doing, either at the event ServerlessDays, or in relation to what we do. And in relation to the next topic of the AWS Serverless DA Team, or Developer Advocacy Team. And to give you context, there's been a couple of things on Twitter this past couple of weeks about the guys and gals from the Developer Service DA team who are changing teams. I don't want to get into the internals of AWS like but I wanted to pay tribute to a strong team, that was led by James Beswick. And before that, by Chris Mullins. And I would say over the last 10 years, we've been lapping up their content, on Twitter, at conferences and on LinkedIn. My number one resource is the people on that team, where I basically learn all the stuff that we do. Let's discuss that team for a bit and the massive impact they've had on what we
00:07:32.000 --> 00:07:32.779
They have had a huge impact and they are huge do.
00:07:36.199 --> 00:07:54.620
enablers for everything we've all done in our careers. And with the barriers that we were trying to push against, their content and the work that they did, gave us ammunition for challenging our status quo and context that we were dealing .
00:07:54.920 --> 00:08:25.009
So the external validation for our approach was coming from the Developer Advocacy Team. The blogs, patterns, examples, workshops, tutorials, or even getting some of them on calls and talking about the problems, we were having led to enablement and empowerment to try these things. And removed the barriers and friction we had. Kudos to them all.
00:08:25.000 --> 00:09:23.440
I don't know how to describe this properly and it's not meant to be personal but when you are trying to do something with step functions, and you need to know more about step functions. the sales guys on the phone will try to sell you more stuff. When you got one of the DA'a on the phone, they were able to say that's crazy, don't use that. Use EventBridge instead etc. They have you an honest answer based on their experience. So it was great to hear that unbiased opinion, they don't have any product interest, they're not trying to sell you something. It's just someone who's in the space, talks to lots of people, and they're good engineers. I find it super helpful and validating to hear their opinions on things. There were lots of times when you were thinking something and you thought 'hh, right, that's interesting'. And why did he say that? And then you realised that you were completely wrong.
00:09:23.000 --> 00:09:55.789
Amazon is a big company with a multitude of services available for teams like us to collaborate with in our day to day, and they're changing all the time. And a lot of stuff gets missed. If you're just looking through the list of change requests on a monthly basis. you can't appreciate what's changed or available.
00:09:49.909 --> 00:11:06.559
These guys do a good job of highlighting new things that come out by creating blogs and working examples to show you how these things are progressing. It makes it consumable and allows us to build. They are the engine that builds the movement and shows what others are doing and fleshes it out. Look at the podcasts they are doing and the content they produce. It's more consumable and leverageable. if you are reading it back, you're not appreciating all the things it could be used for. But when you see how someone actually does leverage it then that gets you thinking. They've breathed life into what's going on in Serverless. Julian's talk at ServerlessDays breathed life into concepts of flow control.
00:11:07.190 --> 00:11:12.230
That notation is really nice.
00:11:07.190 --> 00:11:26.450
Can we design this stuff in the abstract before we even consider services. You don't get that from reading the spec. you need the team to bring it to life.
00:11:26.929 --> 00:11:31.580
That's what they do and hopefully, that's what they continue to do.
00:11:34.059 --> 00:12:28.000
With our modernisation, migration and enablement work for organisations, we avoided undifferentiated heavy lifting by pointing towards Serverless Land, the DA team and the patterns, examples, workshops and tutorials that they provided. We didn't have to create that content or those courses, tutorials, workshops or blog posts. We were able to build on top of what they already put in place. So we were standing on the shoulders of the giants. When we were trying to transform a large enterprise, we were able to tailor the content to move ourselves up the value chain. So we're basically standing on top of the work that they have enabled us to do.
00:12:28.960 --> 00:12:47.590
Let's be specific. When we think of the transformation at Liberty Mutual it was based on the content that the DA Team were pushing out. It was validation that we weren't making stuff up. Chris Munns formed the DA Team in 2015/16.
00:12:49.690 --> 00:12:55.480
We got to the point where we were asking what is he tweeting about? What's he talking about in the articles he is writing.
00:12:55.509 --> 00:13:03.009
And that was a pretty good steer. And then as the team grew, James Beswick had solid blog posts with good content.
00:13:03.009 --> 00:13:27.850
There were lots of good conferences and different events that they ran. Julian Wood came to the first ServerlessDays Belfast in 2020. I'm remember asking him to do a talk in Liberty IT, asking him to explain what Serverless is, in plain English. He sat and just explained and it was brilliant.
00:13:28.389 --> 00:13:49.990
He has been aceing AWS re:Invent. He regularly gets recognised for the best Serverless talk. People recognise him in the street and take photographs of him. He's like a rock star. Eric Johnson is absolutely unbelievable. He has been driving so many events and he is such a good speaker.
00:13:50.169 --> 00:14:02.889
Ben Smith created Serverless Espresso and brilliant step functions on EventBridge implementations. David Boyne with all the EDA stuff. EDA visualisations are incredible.
00:14:02.919 --> 00:14:31.389
And Marcia Villalba with her YouTube channel. It is a wealth of information. The Serverless Land site is my go to whenever anyone asks about the tech. Go read that site, here's a few articles, but just consume that entire site. And then we'll talk because that's our strategy.
00:14:31.899 --> 00:14:44.110
We almost had our own internal Serverless Land with a mind map on this and a blog and the different EMP patterns all scattered around.
00:14:41.470 --> 00:14:54.039
Serverless Land brought it all together. So instead of own custom built resource, we can point people to Serverless Land.
00:14:54.000 --> 00:15:12.840
Even way back at the start, we were taking Chris Munns slides and putting them into our internal decks to drive messaging and create an environment where this messaging was slick.
00:15:29.789 --> 00:15:33.059
I've enjoyed our reflections and celebrations.
00:15:34.440 --> 00:15:54.330
There are a few other people in the team, but I'm talking about people who I personally know and worked with. They're all moving to different areas. And there's still a strong Developer Advocate movement within AWS.
00:15:44.850 --> 00:15:54.330
For me, Serverless is evolving.
00:15:55.350 --> 00:16:05.879
Ad there will always be a need for advocacy. What is hard about developer advocacy, or Dev Rel, is its measure of success.
00:16:06.000 --> 00:16:19.830
It can't be articles written or talks done It's hard to measure the impact, but I'm glad companies invest in Dev Rel, because it's how we learn.
00:16:19.000 --> 00:16:38.049
The Serverless DA Team have had millions or even billions worth of impact. But because that type of enablement is so hard to measure, they'll probably never know?How many times has that pattern being leveraged in massive companies?
00:16:38.049 --> 00:16:52.450
How many times has that blog post inspired Fortune 100 companies to build and assemble this way? How many times have those slides helped convince the C suite that it is the way to go. It's hard to get tangible, quantifiable metrics on that.
00:16:52.450 --> 00:17:03.549
But in our experience and from prolonged, anecdotal, alternate metrics, there have been big outcomes driven from the work that they've done.
00:17:09.299 --> 00:17:20.670
When I was younger I was seeing some talk, or some guy with a ponytail who sad something interesting. But I could not remember who it was.
00:17:16.019 --> 00:17:29.039
There are 1000s of people like that, who just remember seeing a talk or live stream and it set them off on a path.
00:17:41.720 --> 00:18:06.230
Last week, we were having a conversation with Julian on opentelemetry and AWS disposition and we were opinionated from our perspective. Engineers, architects and developers have opinions but we discuss it with them. And you can rest assured, they're feeding back into AWS.
00:18:07.039 --> 00:18:31.339
They take our thoughts and opinions and help shape what's going on in terms of the roadmap and progress for the Cloud Provider. They can take on critical feedback and run with
00:18:31.000 --> 00:18:31.549
I hope it continues with the evolution of developer it.
00:18:35.980 --> 00:18:44.890
advocacy in AWS and the feedback loop and shaping of product direction is still strong, and top of mind.
00:18:44.000 --> 00:19:32.299
I've had so many conversations where you ask for something and they're like, I'm not sure about that but why don't you contact the product team and explain what you're trying to do? Because they would love a customer testimonial or feature request. I'm looking forward to the content that they will continue to put out there.
00:19:24.259 --> 00:20:07.609
I'm looking forward to continue to follow them on their different channels. We can close off with the future of Serverless. I sense a shift coming. We've been about event driven architecture and EDA, recently. There is an evolution underway with some cool vendors out there, like Vercel and Momento. I find myself repeating that Severless is not just Lambdas or Functions.
00:20:09.670 --> 00:20:14.680
Do you have situational awareness? Do you know the value chain that you're trying to bring to bear here?
00:20:14.680 --> 00:20:45.940
And what is the best technology or the best solution to deliver that value chain? And for us, the model was Serverless for a long time. But as things evolve, there are new capabilities and components that you can plug in or a SaaS offering. And you may not use Lambda or Step Functions. We've been using the words modern cloud, modern cloud solutions or modern applications for a while.
00:20:50.380 --> 00:20:55.059
There's a higher level of abstraction beginning to emerge that's encompassed in Serverless.
00:20:57.579 --> 00:21:22.119
That's the craic.
00:20:57.579 --> 00:21:41.410
It is good to reflect on the Serverless DA Team. A massive thank you to the extended team for all their work. Check out TheServerlessEdge.com and follow us on X or LinkedIn hit subscribe on YouTube.
