1
00:00:00,000 --> 00:00:06,220
So here we are at SpringOne Platform, the most awesome name conference ever, and I was catching up with someone.

2
00:00:06,400 --> 00:00:13,160
We'd been swapping stories about, what would you call it, kids' video games, ways of helping kids work on games.

3
00:00:13,360 --> 00:00:18,080
And then you were telling me about a project with Kubo that you were working on recently.

4
00:00:18,520 --> 00:00:19,920
So what was that project?

5
00:00:20,380 --> 00:00:26,820
Yeah, so we got approached by a prospect who basically wanted to set us a new challenge.

6
00:00:26,820 --> 00:00:35,240
You know, people already know that Cloud Foundry is a really good place to run Spring Boot applications.

7
00:00:35,600 --> 00:00:46,740
So the usual kind of, you know, well, we'll show you some microservices and we'll push them to Cloud Foundry and you'll be able to see how they work, just didn't really cut the mustard for that particular customer.

8
00:00:46,900 --> 00:00:53,360
So they set us a much more difficult challenge, which was, OK, so we've been into Sowa for quite a while.

9
00:00:53,360 --> 00:00:57,760
We've been doing, we built something that we call our integration fabric.

10
00:00:58,860 --> 00:01:01,380
We plug all of our legacy services into that.

11
00:01:01,620 --> 00:01:04,640
All of our sort of heritage systems are plugged into that.

12
00:01:05,120 --> 00:01:09,620
And this was a manufacturer that's been around for a long time.

13
00:01:09,720 --> 00:01:12,220
I mean, I would be guessing, but I would guess around a few years.

14
00:01:12,220 --> 00:01:15,900
So they had the typical, like, fabric, bus, whatever.

15
00:01:16,080 --> 00:01:20,460
The centralized, the network is the integration point or whatever it is.

16
00:01:20,500 --> 00:01:22,760
Not the network, but I just, I don't know.

17
00:01:22,960 --> 00:01:23,940
And they had all the...

18
00:01:23,940 --> 00:01:24,800
It's a bus fabric thing.

19
00:01:24,960 --> 00:01:26,660
All the usual middleware associated with that.

20
00:01:26,660 --> 00:01:27,100
Right, right.

21
00:01:27,140 --> 00:01:28,700
So they had an API gateway.

22
00:01:28,900 --> 00:01:30,700
They had an enterprise service bus.

23
00:01:30,920 --> 00:01:35,140
They have, you know, Sowa registries and all that sort of stuff.

24
00:01:35,260 --> 00:01:50,940
And their concern was, what do I do with all of these things, which are non-cloud native, heavyweight applications in this new sort of cloud world where I want to be able to use any cloud vendor that I want.

25
00:01:50,940 --> 00:01:53,480
Because currently they didn't have that freedom.

26
00:01:53,940 --> 00:01:58,060
They could, they had a lot of puppet and a lot of chef and various other things.

27
00:01:58,280 --> 00:02:09,520
So they could push these applications to maybe one or two IaaS vendors, but adding more or going to different regions like China or whatever it might be.

28
00:02:09,860 --> 00:02:14,200
And just standing up that stuff is a hassle because you have to, just the way that it has to be installed.

29
00:02:14,200 --> 00:02:22,700
Yeah, I mean, it's either, you know, installing it slowly or basically rewriting the installation of it to run on a new IaaS.

30
00:02:22,960 --> 00:02:29,460
So, you know, as they move from one region to another, maybe their preferred vendor isn't in that region and they still have to operate.

31
00:02:29,460 --> 00:02:43,500
So they asked us to show them multi-cloud and show running these historic heritage workloads on something that was multi-cloud.

32
00:02:43,700 --> 00:02:54,380
So we, we started to show them Kubo, which of course now is, is being integrated into a PKS and we used Kubo instead.

33
00:02:54,380 --> 00:03:13,380
So we, we brought up Kubernetes clusters and we created all the necessary scripting to push essentially these, these heavyweight ESBs and API gateways and that sort of thing onto this, this Kubernetes based infrastructure.

34
00:03:13,700 --> 00:03:17,100
infrastructure, which then because of Bosch is nicely multi-cloud.

35
00:03:17,140 --> 00:03:33,340
So you were able to essentially use Kubo at the time or, you know, PK, you were able to use Kubernetes as, as, shim is the wrong word, but a thing that you would put underneath the, this, this fabricry stuff to make it easier to install across multiple regions and things like that.

36
00:03:33,420 --> 00:03:40,980
So instead of having to rewrite those things or use something new, you just kind of added a, some packaging around it, a container, if you will.

37
00:03:40,980 --> 00:03:50,600
So it, so it, so it, so it, it essentially, it standardized the control plane, you know, Kubo CTL becomes your new kind of basic control plane for those, for those apps.

38
00:03:50,820 --> 00:04:03,560
So it, it, it, it gave us a multi-cloud, it gave us Bosch to manage those as well so that we could have, you know, again, a standardized control plane across how it's operated as well as how developers might interact with it.

39
00:04:04,160 --> 00:04:11,440
And it was a, it turned out to be quite a successful little project considering it was essentially proof of concept work.

40
00:04:11,440 --> 00:04:16,880
You know, we, we stood up a high availability cluster for an ESB, for example.

41
00:04:17,140 --> 00:04:20,940
The ESB that they had was WSO2, so.

42
00:04:21,600 --> 00:04:22,400
Right, right, okay.

43
00:04:22,540 --> 00:04:25,820
So, you know, most, a lot of people would be familiar with that.

44
00:04:26,780 --> 00:04:28,460
Yeah, so, so walk through what that was like.

45
00:04:28,540 --> 00:04:31,760
So you've got your, your WSO2 ESB, there it is.

46
00:04:32,020 --> 00:04:34,660
Like, we want to make it so that it's running on, on Kubo.

47
00:04:34,780 --> 00:04:41,200
Like, how do you, like, how long does that take and how do you start and what are the things that you have to architect around?

48
00:04:41,200 --> 00:04:43,500
Or do, like, what's that, what's that look like?

49
00:04:43,620 --> 00:04:46,880
Well, we thought that it would be quite difficult at first, you know.

50
00:04:46,940 --> 00:04:49,220
We figured there'd be quite a lot of work in it.

51
00:04:49,360 --> 00:04:59,820
But as it happens, WSO2 have already done quite a lot of work on dockerizing their containers, if you like.

52
00:04:59,820 --> 00:05:05,100
And also have done some work to integrate those with Kubernetes.

53
00:05:05,400 --> 00:05:10,520
So, so that you can do things like running a cluster using several Kubernetes pods.

54
00:05:10,960 --> 00:05:11,480
Okay, right, right, right.

55
00:05:11,480 --> 00:05:14,500
And it would know, for example, where the other nodes are in the cluster.

56
00:05:14,920 --> 00:05:18,020
So, so WSO2 has already done quite a lot of work on that.

57
00:05:18,220 --> 00:05:19,720
So, so we were fortunate, really.

58
00:05:19,800 --> 00:05:23,200
We got to be able to piggyback on the back of some of that stuff.

59
00:05:23,440 --> 00:05:25,020
So then it would seem like what you have to take.

60
00:05:25,080 --> 00:05:29,260
So they're already running the ESB outside of, you know, Kubernetes world.

61
00:05:29,780 --> 00:05:34,080
And so I guess you need to take the configuration and how everything's wired together.

62
00:05:34,080 --> 00:05:37,160
And somehow, and that's the main part of what you have to move over, I guess.

63
00:05:37,160 --> 00:05:37,560
Exactly, yeah.

64
00:05:37,700 --> 00:05:50,780
But, but at the same time, you know, not having to regenerate all that DIY sort of puppet and chef and, and actually push it and pave your IaaS and push it into the IaaS.

65
00:05:50,860 --> 00:05:51,080
Yeah, yeah.

66
00:05:51,080 --> 00:05:51,880
So it's a lot of time.

67
00:05:52,180 --> 00:05:57,860
So then, yeah, we could concentrate on moving the, the business logic, I guess you would call it.

68
00:05:57,920 --> 00:05:59,680
I mean, it's really, it's integration logic.

69
00:05:59,820 --> 00:06:00,160
Yeah, yeah, yeah.

70
00:06:00,160 --> 00:06:03,780
So it's, you know, this points to that and this sends messages there and all that kind of stuff.

71
00:06:04,040 --> 00:06:16,460
We were able to take that configuration and stand it up and show the customer, okay, you gave us these apps and you gave us these legacies, SOA definitions.

72
00:06:17,100 --> 00:06:20,640
We've wired it together exactly the same way as you currently have it.

73
00:06:21,120 --> 00:06:28,000
And we could show them and demonstrate to them the same thing that they're used to, but working in a completely new paradigm.

74
00:06:28,000 --> 00:06:34,040
And then the result, like you're saying, is you can run on, as they spread out to different regions, you can run on different infrastructure a lot more easily.

75
00:06:34,380 --> 00:06:34,580
Precisely.

76
00:06:34,600 --> 00:06:40,920
And then I would imagine there's like also just some raw management optimization, like abilities that you get.

77
00:06:40,960 --> 00:06:42,100
It's just easier to manage.

78
00:06:42,420 --> 00:06:42,580
Yeah.

79
00:06:42,580 --> 00:06:52,840
Because you've, you've, I keep using this word a lot because it's fun, but you've homogenized the sort of underlying, the layers of just monitoring and managing and updating and all of that.

80
00:06:53,140 --> 00:06:53,600
That's right.

81
00:06:53,600 --> 00:07:01,620
I mean, you know, as a customer, they'll be used to Bosch for PCF, but of course then they're managing the Kubernetes clusters via Bosch as well.

82
00:07:01,940 --> 00:07:02,340
So, right.

83
00:07:02,460 --> 00:07:13,440
So, they end up with kind of a standardized control plane for both legacy applications or, you know, middleware centric applications as well as the new sort of cloud native stuff.

84
00:07:14,600 --> 00:07:29,320
So, it was, it was quite an exciting project and we learned a lot about, about what it feels like to work with, with, with Kubernetes and it's sort of a hybrid between, we had some workloads on Cloud Foundry, we had some workloads on Kubernetes.

85
00:07:29,920 --> 00:07:34,240
So, we got a, you know, good exposure to mix in the two.

86
00:07:34,380 --> 00:07:39,160
Yeah. Like what do we call it now? The Pivotal Application Service? Is that right? The PaaS?

87
00:07:39,380 --> 00:07:39,760
Yeah.

88
00:07:39,760 --> 00:07:43,700
I never thought that it's sort of a pun on two A PaaS.

89
00:07:45,260 --> 00:07:46,520
Yeah, it's fewer A's.

90
00:07:46,660 --> 00:07:47,400
Yeah, yeah, yeah, yeah.

91
00:07:47,400 --> 00:07:48,620
We dropped an A somewhere.

92
00:07:48,620 --> 00:07:54,960
That almost aligns with Pivotal Culture. Not that many, so to speak, A's around. But anyways.

93
00:07:55,300 --> 00:07:56,100
The A bomb.

94
00:07:56,540 --> 00:08:09,620
But, so what is that like experience of, because that's one of the sort of promises, I guess, of having the PaaS, the Pivotal Application, classic build pack driven.

95
00:08:09,760 --> 00:08:25,040
Whatever, you know, Pivotal Cloud Foundry. And then you have your Kubernetes, your PKS run stuff over here and, you know, they should be able to work with each other and, you know, work with each other pretty effortlessly without knowing that they're different things.

96
00:08:25,260 --> 00:08:25,520
Yeah.

97
00:08:25,760 --> 00:08:27,720
And does that kind of pan out or what's that like?

98
00:08:27,800 --> 00:08:45,380
Well, we did learn lots of interesting things about that. So, so, so Kubo PKS can work in both an integrated fashion where you've integrated your Kubernetes through PKS with the PCF PaaS.

99
00:08:45,760 --> 00:08:46,060
Right, right, right, right.

100
00:08:46,060 --> 00:08:52,720
So, you can do that. You can go to the marketplace and you can say CF create service and you'll get a Kubernetes cluster.

101
00:08:52,720 --> 00:08:53,580
Oh, right, right, right, okay.

102
00:08:53,580 --> 00:09:07,300
Okay, so you can do that. But for middleware type workloads, it doesn't, it doesn't quite, it's not quite what you want. It's, the life cycle, for example, is associated with the Cloud Foundry space.

103
00:09:08,020 --> 00:09:09,160
Right, right, right, right, right.

104
00:09:09,360 --> 00:09:17,860
So, these middleware workloads, you know, they'd last for many years and they are usually independent and managed centrally.

105
00:09:18,120 --> 00:09:27,100
So, so the, the other way of doing that is to also use PKS but stand up individual externalized, if you like, PKS clusters.

106
00:09:27,220 --> 00:09:34,580
And is that like a different foundation that you run or is, or does it, it can still be the same PCF and run independently or?

107
00:09:34,580 --> 00:09:48,960
Well, I think I recall correctly that with the, with the service broker, so if you're in the CF marketplace, it's going to stand up, you know, based on the plan, it's going to stand up a certain size of Kubernetes cluster.

108
00:09:49,180 --> 00:09:49,340
Right, right.

109
00:09:50,300 --> 00:09:56,760
If you are deploying your Kubernetes through Bosch separately, then you have a bit more control over what that looks like.

110
00:09:56,900 --> 00:10:00,500
So, for example, you can give it more resources, you can have more nodes.

111
00:10:00,700 --> 00:10:10,100
Because, because to your point, you don't really, you don't need, whether you want to think of it as constraining and limiting or, or enabling and, you know, nice.

112
00:10:10,220 --> 00:10:13,820
You don't need that sort of plan stuff wrapped around it or containment.

113
00:10:13,960 --> 00:10:19,320
Because it is like, it's the middleware you're standing up is intended to be used by everyone.

114
00:10:19,580 --> 00:10:19,980
Exactly.

115
00:10:19,980 --> 00:10:21,700
Right, and to be long-lived and centralized.

116
00:10:21,880 --> 00:10:23,380
Yeah, that's an interesting distinction.

117
00:10:23,380 --> 00:10:36,420
But also, and probably similarly quite important, is if you're thinking about a middleware like an API gateway, you know, the purpose of that is really to be an edge service.

118
00:10:36,580 --> 00:10:38,960
You know, it's acting on the edges of your network.

119
00:10:39,480 --> 00:10:39,640
Yes.

120
00:10:39,640 --> 00:10:47,800
It's doing things like routing through to particular applications or, you know, looking at content or applying security or whatever it might be.

121
00:10:48,380 --> 00:11:02,420
In the integrated method, the, essentially, the traffic has already come through PCF before it gets to your, before it gets to your Kubernetes thing, whatever's in your pod.

122
00:11:02,760 --> 00:11:02,940
Yeah.

123
00:11:02,940 --> 00:11:08,300
So, you know, if you're trying to run an API gateway inside that pod, it's in the wrong place.

124
00:11:08,500 --> 00:11:08,720
Yeah, yeah, yeah.

125
00:11:08,720 --> 00:11:09,700
Because it's supposed to control traffic.

126
00:11:09,700 --> 00:11:11,440
Get an API gateway and an API gateway.

127
00:11:11,560 --> 00:11:12,420
Yeah, exactly, yeah.

128
00:11:12,420 --> 00:11:15,440
So, you end up with this kind of double router kind of problem.

129
00:11:15,760 --> 00:11:16,200
Yeah, yeah.

130
00:11:16,200 --> 00:11:21,620
So, it makes sense for these sort of middleware workloads to work in this kind of independent mode.

131
00:11:21,960 --> 00:11:25,620
And thankfully, PKS has got the flexibility to do both those things.

132
00:11:25,900 --> 00:11:26,320
Yeah, yeah.

133
00:11:26,400 --> 00:11:33,120
So, if you're a, you know, if you're a developer and you want some elastic search, whatever it might be, use the CF marketplace method.

134
00:11:33,320 --> 00:11:38,840
If you're an integrator and you need something long-lived, then use a kind of independent method.

135
00:11:38,840 --> 00:11:44,640
Yeah, and did y'all move over anything that wasn't luckily already containerized?

136
00:11:46,000 --> 00:11:51,440
No, we did, we, like I said, we managed to find containers for most things.

137
00:11:51,540 --> 00:11:51,680
Yeah.

138
00:11:51,680 --> 00:11:55,840
Although, the client had certain restrictions around versions.

139
00:11:56,120 --> 00:12:00,460
So, we did have some that we had to tweak and tinker with in order to make them work.

140
00:12:00,700 --> 00:12:06,440
But the WSO2 mechanism is to use a base container and then build on top of that.

141
00:12:06,580 --> 00:12:06,780
Yeah.

142
00:12:06,900 --> 00:12:08,360
So, it wasn't too bad.

143
00:12:08,360 --> 00:12:11,180
There was a few sort of small changes that we had to make.

144
00:12:12,080 --> 00:12:14,360
But it was a surprisingly smooth process.

145
00:12:14,560 --> 00:12:16,640
And I think that that's a good news thing.

146
00:12:16,800 --> 00:12:30,160
Because, you know, if you're an enterprise and you're thinking, you know, well, I work quite like multi-cloud for my, you know, workloads, my middleware workloads, then something like PKS could be a really good place to start.

147
00:12:30,160 --> 00:12:37,220
Yeah, yeah, that was another thing I wanted to ask is, I mean, there's no, it's just impressions and reflections at this point, probably.

148
00:12:37,360 --> 00:12:43,980
But for whatever reason, I hadn't thought about until a couple months ago the idea that, let's call them ISVs.

149
00:12:43,980 --> 00:12:52,500
But someone like WSO2 would be shipping their software in containers, right?

150
00:12:52,500 --> 00:12:56,720
Like, how does that change as far as consuming that software?

151
00:12:56,780 --> 00:13:10,380
Like, like, and for, if you didn't have, I haven't looked at WSO2 stuff in a long time, but if you didn't have it containerized, it would basically be like, here's like a jar or an ear or a war file.

152
00:13:10,380 --> 00:13:12,480
And here's how to get it set up in Tomcat.

153
00:13:13,000 --> 00:13:16,860
And you can kind of, and maybe we've got a VM image for you of like all this stuff built out.

154
00:13:16,900 --> 00:13:19,280
But basically, like, you should build this stuff.

155
00:13:19,340 --> 00:13:23,420
Whereas I would imagine if you put it in a container, it'd be like, I'm just making stuff up.

156
00:13:23,460 --> 00:13:25,400
But we've got five subcomponents to the system.

157
00:13:25,400 --> 00:13:27,000
And here are the five types of containers.

158
00:13:27,360 --> 00:13:30,640
And then you can just kind of inject the configuration into it.

159
00:13:30,800 --> 00:13:32,060
And then it's up and running.

160
00:13:32,060 --> 00:13:37,760
But I don't know, like, how do you think it's different using middleware that's already containerized?

161
00:13:38,400 --> 00:13:46,920
Well, there were, like I said, there was a few issues where some things perhaps hadn't had the demand on WSO2 maybe.

162
00:13:47,400 --> 00:13:50,440
So, you know, all the versions were quite old versions.

163
00:13:50,740 --> 00:13:52,400
So, you know, stuff goes out of date.

164
00:13:52,560 --> 00:13:57,080
Stuff doesn't get necessarily the love and attention that it needs to keep it all working.

165
00:13:57,240 --> 00:14:01,180
So we did have some work that we had to do.

166
00:14:01,180 --> 00:14:07,600
I think I recall it was perhaps around things like sharing configuration across a cluster.

167
00:14:08,120 --> 00:14:10,440
So in order to do that, they used subversion.

168
00:14:11,020 --> 00:14:11,420
Oh, okay.

169
00:14:11,440 --> 00:14:14,680
So you needed a containerized subversion in order to do that.

170
00:14:15,140 --> 00:14:15,720
That's interesting.

171
00:14:15,900 --> 00:14:23,140
So there were instances like that where we had to do a little bit of work just to finish off some, you know, round off some of those edges.

172
00:14:23,360 --> 00:14:23,560
Yeah.

173
00:14:23,920 --> 00:14:25,040
That didn't quite work.

174
00:14:25,040 --> 00:14:34,120
But I can see that, you know, it could be quite attractive to a vendor to, you know, be able to provide these container images.

175
00:14:34,400 --> 00:14:46,080
But from my understanding, from the press releases that I'm seeing and from some of the partnerships that we saw yesterday, for example, that, you know, more and more of them are looking to do that.

176
00:14:46,340 --> 00:14:46,560
Yeah.

177
00:14:46,700 --> 00:14:52,180
I forget the name of it, but there's like, it's not a, maybe it's a hub, but there's some directory of containerized things.

178
00:14:52,180 --> 00:14:55,900
I think for Kubernetes out there and there's a, there's a lot of things in there.

179
00:14:56,180 --> 00:14:56,540
Yeah.

180
00:14:56,660 --> 00:15:03,220
And also the, the Liberty bill pack, you know, being kind of included in the supported number of bill packs.

181
00:15:03,440 --> 00:15:03,460
Yeah.

182
00:15:03,460 --> 00:15:11,520
So that's a clear indication of how much WebSphere application server there is out there and how people are, you know, using the Liberty mechanism.

183
00:15:11,700 --> 00:15:12,160
Yeah, yeah.

184
00:15:12,180 --> 00:15:15,680
Try to leverage that and then push that stuff into the cloud.

185
00:15:15,700 --> 00:15:15,880
Yeah.

186
00:15:15,980 --> 00:15:19,160
And maybe we'll finally get all the advantages of like virtual appliances.

187
00:15:19,640 --> 00:15:25,020
Like that, that always seemed, it always seems like it'd be really a nice, really nice to have virtual appliances.

188
00:15:25,020 --> 00:15:29,420
And I, I always get the sense that never really pans out probably for many good reasons.

189
00:15:29,420 --> 00:15:29,680
Right.

190
00:15:29,700 --> 00:15:37,260
But just like the whole, the whole process of installing even mildly complicated middleware is, I mean, you were kind of hitting on it.

191
00:15:37,280 --> 00:15:40,820
It's like, well, you got to have this subversion thing over here that synchronizes with this.

192
00:15:40,820 --> 00:15:46,240
And, and you very quickly get into this situation of like, I got a whole other distributed application I got to deal with now.

193
00:15:46,660 --> 00:15:49,180
Do those appliances still come with CD drives?

194
00:15:50,220 --> 00:15:50,620
Exactly.

195
00:15:50,920 --> 00:15:54,260
Do you still have somewhere to put your coffee while you're working on it?

196
00:15:54,260 --> 00:15:59,740
Yeah, appliances are such a nice idea, but they, I mean, just, just the idea of like, ah, it just works.

197
00:16:00,540 --> 00:16:12,400
I mean, I guess maybe to some extent that's, that's like a, one of the huge reasons why like pure public cloud stuff is so attractive is it's not really an appliance, but it's already installed for you.

198
00:16:12,520 --> 00:16:12,920
Right.

199
00:16:13,020 --> 00:16:16,040
Like, and then you just have to configure it and get it set up how you want.

200
00:16:16,160 --> 00:16:17,520
But yeah, we'll see.

201
00:16:17,920 --> 00:16:18,560
Maybe one day.

202
00:16:18,960 --> 00:16:19,320
Appliances.

203
00:16:19,740 --> 00:16:21,220
We can all dream the dream coming.

204
00:16:21,960 --> 00:16:24,180
Well, I never, I never asked you to introduce yourself.

205
00:16:24,260 --> 00:16:24,900
Oh, okay.

206
00:16:25,060 --> 00:16:26,380
So, so, so, so who are you?

207
00:16:26,440 --> 00:16:26,620
Yeah.

208
00:16:26,720 --> 00:16:28,180
So, so my name is Ben Wilcock.

209
00:16:28,320 --> 00:16:32,080
I'm a solution architect working out of Europe.

210
00:16:32,380 --> 00:16:32,620
Yeah.

211
00:16:32,620 --> 00:16:38,960
I work for the application transformation team that helps our customers to move workloads into the cloud.

212
00:16:39,100 --> 00:16:41,100
And how many, how many people do we have on that team?

213
00:16:41,360 --> 00:16:47,100
Oh, it's a small team in Europe, but, uh, but across the globe, we've got something like 60, I think.

214
00:16:47,220 --> 00:16:47,580
Oh, wow.

215
00:16:47,580 --> 00:16:47,840
Okay.

216
00:16:48,060 --> 00:16:54,400
But the European team team is a small, uh, smaller percentage of that, but, uh, but we're growing and we're recruiting.

217
00:16:54,800 --> 00:16:57,460
So, you know, everyone's, uh, so, so what, what, what do y'all do?

218
00:16:57,540 --> 00:17:02,380
Is it, is it, um, I mean, from what you're describing, it sounds like a lot of everything, but like, yeah.

219
00:17:02,380 --> 00:17:13,020
What are the, what, like, what's the typical sort of like, like week or two of, of the kind of tasks that you do and the people you work with and the types of projects that you're working on?

220
00:17:13,120 --> 00:17:17,420
So, uh, so it's generally, you know, it's, it's usually always enterprise customers.

221
00:17:17,420 --> 00:17:29,460
So, so it's there, it's working with their developers essentially normally to either enable them to be able to use Cloud Foundry and to use the tools that they've got at their disposal.

222
00:17:29,960 --> 00:17:33,640
Or it's, uh, helping them move, you know, specific workloads.

223
00:17:33,860 --> 00:17:34,720
Migrating things.

224
00:17:34,920 --> 00:17:37,760
Or, or, do you say re-platforming or what's the terminology?

225
00:17:37,760 --> 00:17:38,080
We do.

226
00:17:38,300 --> 00:17:43,000
So we, we have, uh, we have sort of two terms that we normally use.

227
00:17:43,080 --> 00:17:55,220
So, uh, so re-platforming being small changes to things that are already, you know, if you've heard of 12 factors, then maybe these things would have, you know, you know, a few of those factors are already.

228
00:17:55,220 --> 00:17:59,520
And maybe they just need a few more in order to be able to push them into the cloud.

229
00:17:59,740 --> 00:18:01,420
So it's sort of like the spirit of refactoring.

230
00:18:01,560 --> 00:18:09,380
You're not really, this is a bastard or incorrect way of saying refactoring, but like, you're not really changing the way something operates.

231
00:18:09,620 --> 00:18:09,720
No.

232
00:18:09,860 --> 00:18:11,200
Well, no, actually it's literally that.

233
00:18:11,240 --> 00:18:14,220
You're changing the way something operates, but not the effect it has, right?

234
00:18:14,300 --> 00:18:16,580
Like you're not changing what it looks like to the end user.

235
00:18:16,720 --> 00:18:18,720
You're just messing around with the internal sort of.

236
00:18:18,900 --> 00:18:20,040
It's where it runs.

237
00:18:20,040 --> 00:18:20,620
Yeah, yeah, yeah.

238
00:18:20,620 --> 00:18:25,640
You know, rather than being on a specific box in a specific data center, you know, it's moving it.

239
00:18:25,840 --> 00:18:30,060
So it's a, so it's a more, uh, you know, it can be moved into any platform.

240
00:18:30,360 --> 00:18:32,220
Yeah, just moving to a new platform in the second term.

241
00:18:32,320 --> 00:18:33,420
That's the replatforming, yeah.

242
00:18:33,540 --> 00:18:42,100
The, uh, the modernization is where we take, uh, slightly more gnarly problems and we perhaps look at them with, you know, fresh eyes.

243
00:18:42,100 --> 00:18:51,660
So, uh, taking a piece of mainframe functionality, for example, and maybe, uh, separating that out into a set of microservices and pushing that into the cloud.

244
00:18:51,840 --> 00:18:54,660
So, so that's, uh, that's usually a bit more involved.

245
00:18:54,780 --> 00:18:56,340
It involves a little bit of design.

246
00:18:56,520 --> 00:19:01,420
Sometimes it involves thinking again about what the process is and what it should do.

247
00:19:01,540 --> 00:19:08,480
And very much our customers are at the forefront of helping drive that through because they know their context better than anybody else.

248
00:19:08,780 --> 00:19:15,600
But then, uh, of course, more recently, we've, we've also started to talk much more about lift and shift.

249
00:19:15,780 --> 00:19:27,500
You know, actually we've got a lot of customers who, uh, you know, there's only certain workloads that are worth the investment of modernizing or replatforming, you know.

250
00:19:27,520 --> 00:19:31,180
And there are, there are a lot of workloads that don't quite meet the business case.

251
00:19:31,420 --> 00:19:47,300
Um, they could be, you know, much more, uh, uh, uh, natural fit for something like PKS where you can take something that already exists, maybe containerize it and still get that sort of multi-cloud feel.

252
00:19:47,360 --> 00:19:48,540
And the management, uh, opt-in.

253
00:19:48,540 --> 00:19:57,960
Yeah, but without necessarily making it fully 12 factor and, and like you said, you know, getting that operator benefit where it can be scheduled and run anywhere.

254
00:19:58,100 --> 00:20:03,360
So it sounds like there's kind of like three areas of stuff that y'all do.

255
00:20:03,500 --> 00:20:13,200
And, and, and it's, I don't know, it's probably like, you know, uh, you know, 45, 45% or 40, 40, but kind of split between architecture sort of thinking.

256
00:20:13,200 --> 00:20:16,340
And then actual, just like development, like doing the work, right.

257
00:20:16,520 --> 00:20:16,840
Precisely.

258
00:20:16,860 --> 00:20:19,500
But then, you know, it's, it's, it's balanced.

259
00:20:19,600 --> 00:20:26,700
I would imagine it's balanced between that because you do have to be pretty deliberate about like, let's, you know, figure out the thing and how we're going to redo it or not redo it.

260
00:20:26,760 --> 00:20:27,960
That hints, the architecture part.

261
00:20:28,040 --> 00:20:29,260
And then, and then moving in.

262
00:20:29,380 --> 00:20:35,900
And then it seems like the minority of stuff though, it might be growing is, I don't know what you call it, like portfolio management.

263
00:20:35,900 --> 00:20:46,020
Almost like a little bit of, there's a tiny flavor of strategy in there where like you look at all the things that you could possibly move or change around or do something with.

264
00:20:46,180 --> 00:20:55,320
And you need some kind of input of like business rationale to basically sort through these ones we're going to leave over there on the, uh, on the mainframe.

265
00:20:55,320 --> 00:20:58,540
And those ones, these ones on the mainframe, we need to like modernize.

266
00:20:58,780 --> 00:21:04,920
And then this, this old like ESB over here, we're just going to like containerize to make it easier to move.

267
00:21:05,000 --> 00:21:08,520
But you need some kind of businessy input to prioritize that.

268
00:21:08,640 --> 00:21:08,920
Exactly.

269
00:21:09,300 --> 00:21:09,480
Yeah.

270
00:21:09,480 --> 00:21:24,240
And we, we do that with our customers during processes like scoping where we'll have a look at that portfolio and we'll perform that analysis to help them see, you know, which workloads are worth the investment, which ones are almost there.

271
00:21:24,240 --> 00:21:34,460
It might be worth, you know, thinking about and which ones they might want to, you know, over time, perhaps they'll retire them, for example, you know, retirement is also a valid option.

272
00:21:34,460 --> 00:21:40,700
But, uh, but we, we are, we are seeing sort of a, you know, we can reach deeper than ever before.

273
00:21:40,700 --> 00:21:44,460
We can move more workloads than ever before onto, onto the cloud.

274
00:21:44,460 --> 00:21:52,520
So, uh, so we're seeing a lot of engagement in that and a lot of, uh, a lot of interesting conversations like the one that we started with about.

275
00:21:52,660 --> 00:21:53,440
Yeah, yeah, yeah.

276
00:21:54,240 --> 00:21:56,660
A customer with the ESB problem.

277
00:21:56,820 --> 00:21:57,940
Yeah, well, that makes sense.

278
00:21:58,320 --> 00:21:58,660
Well, good.

279
00:21:58,760 --> 00:22:00,200
Well, thanks for giving me that overview.

280
00:22:00,520 --> 00:22:01,720
That was, uh, that was good.

281
00:22:01,860 --> 00:22:02,340
It's my pleasure.

282
00:22:02,480 --> 00:22:02,700
Yeah.

283
00:22:02,840 --> 00:22:04,020
We'll see everyone next time.