1
00:00:00,000 --> 00:00:01,800
Well, you're back here on Tanzu Talk.

2
00:00:02,040 --> 00:00:02,960
Why don't you introduce yourself?

3
00:00:03,400 --> 00:00:05,300
Yes, happy to be back, Coté.

4
00:00:05,920 --> 00:00:07,000
Purnima Padmanabhan,

5
00:00:07,200 --> 00:00:09,420
General Manager for Tanzu Division at Broadcom.

6
00:00:09,700 --> 00:00:13,640
So last time you allowed me to take you

7
00:00:13,640 --> 00:00:15,840
on a walk down memory lane of like our,

8
00:00:16,180 --> 00:00:19,040
all the time we've spent in the IT infrastructure area

9
00:00:19,040 --> 00:00:20,140
was delightful and fun.

10
00:00:20,440 --> 00:00:23,300
In this episode, I wanted to get more in the present day

11
00:00:23,300 --> 00:00:26,400
and specifically for like what we at Tanzu do

12
00:00:26,400 --> 00:00:27,880
and what we've been working on for a while.

13
00:00:28,060 --> 00:00:31,480
I've been recently, well, more than recently.

14
00:00:31,580 --> 00:00:32,300
I do this all the time.

15
00:00:32,360 --> 00:00:33,540
I'm always trying to figure out

16
00:00:33,540 --> 00:00:36,240
over the last 18 years or so of cloud,

17
00:00:36,500 --> 00:00:38,560
like how much public cloud there is

18
00:00:38,560 --> 00:00:40,860
and how much on-premises private cloud there is.

19
00:00:41,400 --> 00:00:44,160
And I found some stuff recently that I've been writing up

20
00:00:44,160 --> 00:00:46,580
that I think kind of gets me in the mind

21
00:00:46,580 --> 00:00:48,880
that it's pretty even at the moment.

22
00:00:49,160 --> 00:00:51,240
I mean, you know, there's always lots of it depends

23
00:00:51,240 --> 00:00:52,300
and footnotes and things.

24
00:00:52,460 --> 00:00:55,680
But my main, the main thing that I noticed

25
00:00:55,680 --> 00:00:58,620
is there's a lot more private cloud out there

26
00:00:58,620 --> 00:01:00,400
than you would assume from reading the headlines.

27
00:01:00,480 --> 00:01:03,500
And in fact, as we know firsthand, there's a lot more.

28
00:01:03,720 --> 00:01:04,720
What do you encounter out there

29
00:01:04,720 --> 00:01:06,240
when it comes to private cloud?

30
00:01:06,800 --> 00:01:07,080
Wow.

31
00:01:07,420 --> 00:01:10,360
Age-old debate of private cloud, public cloud,

32
00:01:10,760 --> 00:01:12,900
and to some extent,

33
00:01:13,200 --> 00:01:14,560
quote, it's no longer a debate.

34
00:01:15,680 --> 00:01:17,200
It is what I see is

35
00:01:17,200 --> 00:01:20,800
we have now well into 18 years of public cloud

36
00:01:20,800 --> 00:01:24,660
and we see tons of growth in public cloud,

37
00:01:25,160 --> 00:01:27,740
but we also continue to see growth

38
00:01:27,740 --> 00:01:29,620
in what we call the private cloud

39
00:01:29,620 --> 00:01:30,680
or the private infrastructure.

40
00:01:31,320 --> 00:01:34,360
And so rather than a versus debate,

41
00:01:34,600 --> 00:01:37,920
it's often in customers' mind an ant debate.

42
00:01:38,400 --> 00:01:42,080
And it is which applications do I land

43
00:01:42,080 --> 00:01:44,240
on which type of environment

44
00:01:44,240 --> 00:01:47,940
so that I get the best advantage for my business.

45
00:01:48,880 --> 00:01:51,340
And in fact, the goal of Tanzu

46
00:01:51,340 --> 00:01:53,140
is to really make that decision

47
00:01:53,140 --> 00:01:56,380
for a customer as seamless as possible, right?

48
00:01:56,720 --> 00:01:58,020
Where do you land an application,

49
00:01:58,180 --> 00:01:59,500
whether it's public cloud or private cloud,

50
00:01:59,620 --> 00:02:01,460
based on the needs?

51
00:02:02,480 --> 00:02:06,220
Now, when we look at private in cloud,

52
00:02:06,440 --> 00:02:08,560
often people start not with private cloud.

53
00:02:08,880 --> 00:02:10,040
They start with private infrastructure.

54
00:02:10,980 --> 00:02:12,260
It's compute virtualization

55
00:02:12,260 --> 00:02:13,800
that is often passed off as,

56
00:02:14,000 --> 00:02:16,160
or even sometimes just a Kubernetes runtime

57
00:02:16,160 --> 00:02:17,720
that is passed off as private cloud.

58
00:02:18,600 --> 00:02:20,560
And what we have done, of course,

59
00:02:20,620 --> 00:02:22,740
at Broadcom with our VMware Cloud Foundation,

60
00:02:22,840 --> 00:02:24,720
etc., has truly laid the foundation

61
00:02:24,720 --> 00:02:26,080
for a private cloud.

62
00:02:26,540 --> 00:02:28,240
And I talk to many customers about this.

63
00:02:28,340 --> 00:02:30,360
Why do you still want to invest in private cloud?

64
00:02:31,080 --> 00:02:32,340
And actually, why do you want to invest

65
00:02:32,340 --> 00:02:32,860
in public cloud?

66
00:02:32,940 --> 00:02:34,660
What I find about private cloud

67
00:02:34,660 --> 00:02:36,420
is there are a few big reasons that stand out.

68
00:02:36,860 --> 00:02:39,080
One is, hey, my application is already there.

69
00:02:39,500 --> 00:02:40,340
It works seamlessly.

70
00:02:40,920 --> 00:02:42,700
It may be running on private infrastructure.

71
00:02:43,420 --> 00:02:44,320
And to get more agility,

72
00:02:44,560 --> 00:02:46,160
I want to move it to a private cloud.

73
00:02:46,660 --> 00:02:47,420
But it's all there.

74
00:02:47,800 --> 00:02:51,400
Second one is often about data gravity.

75
00:02:52,420 --> 00:02:55,360
People underestimate how much data

76
00:02:55,360 --> 00:02:58,020
is there about their businesses.

77
00:02:58,680 --> 00:03:01,140
And often these applications need to use the data.

78
00:03:01,260 --> 00:03:02,680
And this world of AI, ML now,

79
00:03:03,060 --> 00:03:03,740
they need to use it.

80
00:03:03,920 --> 00:03:05,180
It's hungry for data.

81
00:03:05,440 --> 00:03:06,560
So you're grabbing all that data.

82
00:03:07,060 --> 00:03:09,340
And trying to move all of that back and forth

83
00:03:09,340 --> 00:03:11,680
between clouds is a very hard proposition.

84
00:03:12,520 --> 00:03:15,420
So data gravity, AI, ML.

85
00:03:16,080 --> 00:03:18,640
And I would say tied to AI, ML and data gravity

86
00:03:18,640 --> 00:03:21,360
is also being able to access the ecosystem

87
00:03:21,360 --> 00:03:22,980
of existing applications

88
00:03:22,980 --> 00:03:25,220
that I already have in the environment.

89
00:03:26,000 --> 00:03:28,560
You know, no application sits in an island.

90
00:03:28,720 --> 00:03:31,040
It's often talking to an ERP system,

91
00:03:31,120 --> 00:03:32,640
maybe talking to a supply chain system,

92
00:03:32,700 --> 00:03:34,080
maybe talking to an ordering system.

93
00:03:34,660 --> 00:03:36,340
How do you bring all of that together

94
00:03:36,340 --> 00:03:37,620
with high performance?

95
00:03:37,980 --> 00:03:39,780
And I would say the last pillar

96
00:03:39,780 --> 00:03:42,640
often tends to be security, privacy, and governance.

97
00:03:43,340 --> 00:03:45,480
I don't want to take all my information

98
00:03:45,480 --> 00:03:47,280
and put it out somewhere else.

99
00:03:47,360 --> 00:03:48,540
I want to still have control.

100
00:03:48,660 --> 00:03:50,260
I want to have control of data locality.

101
00:03:50,400 --> 00:03:52,560
I want to be able to do compliance better.

102
00:03:53,140 --> 00:03:54,480
So there are many reasons

103
00:03:54,480 --> 00:03:58,980
why people prefer the private cloud.

104
00:03:59,100 --> 00:03:59,880
But again, as I said,

105
00:03:59,920 --> 00:04:00,760
it's not an either or.

106
00:04:01,180 --> 00:04:01,840
Many times,

107
00:04:02,260 --> 00:04:04,020
and often the primary reason I see

108
00:04:04,020 --> 00:04:05,600
for public cloud, on the other hand,

109
00:04:05,940 --> 00:04:07,340
is velocity.

110
00:04:07,720 --> 00:04:10,380
Hey, I've already got an easy environment.

111
00:04:10,740 --> 00:04:12,560
I've got a simple API for my IaaS.

112
00:04:13,100 --> 00:04:14,120
I've got a set of services

113
00:04:14,120 --> 00:04:15,880
and I can have the developer

114
00:04:15,880 --> 00:04:16,920
be off to the races

115
00:04:16,920 --> 00:04:18,740
in terms of consumption,

116
00:04:18,960 --> 00:04:19,700
ease of consumption

117
00:04:19,700 --> 00:04:21,160
of these infrastructure services.

118
00:04:21,380 --> 00:04:22,620
As you were going through that,

119
00:04:23,300 --> 00:04:24,720
you know, the term data gravity,

120
00:04:25,080 --> 00:04:26,160
that's been a good one

121
00:04:26,160 --> 00:04:27,060
for a long time.

122
00:04:27,120 --> 00:04:27,560
Very clever.

123
00:04:27,940 --> 00:04:28,420
I forget.

124
00:04:29,520 --> 00:04:30,780
I should remember who came up with it.

125
00:04:30,860 --> 00:04:32,780
But you brought up the idea of,

126
00:04:33,000 --> 00:04:33,200
you know,

127
00:04:33,260 --> 00:04:34,640
you have these existing,

128
00:04:35,100 --> 00:04:36,220
let's call them services,

129
00:04:36,940 --> 00:04:37,780
whether it's, you know,

130
00:04:37,820 --> 00:04:38,740
your supply chain stuff

131
00:04:38,740 --> 00:04:39,220
or ERP

132
00:04:39,220 --> 00:04:40,820
or just other existing applications.

133
00:04:41,060 --> 00:04:41,820
And, you know,

134
00:04:41,860 --> 00:04:43,080
maybe there's sort of like

135
00:04:43,080 --> 00:04:45,240
that like services gravity

136
00:04:45,240 --> 00:04:45,940
that you have,

137
00:04:46,140 --> 00:04:47,680
like all the other existing things

138
00:04:47,680 --> 00:04:48,120
to integrate.

139
00:04:48,600 --> 00:04:50,300
which I think gravity, yes.

140
00:04:50,500 --> 00:04:50,960
Yeah, exactly.

141
00:04:51,060 --> 00:04:52,480
And it's your own applications,

142
00:04:52,900 --> 00:04:54,040
ones that you might have

143
00:04:54,040 --> 00:04:55,880
with your partners

144
00:04:55,880 --> 00:04:56,840
in a business sense,

145
00:04:57,240 --> 00:04:58,840
like people, suppliers

146
00:04:58,840 --> 00:05:00,040
and people that you work with.

147
00:05:00,180 --> 00:05:01,540
And then also just whatever,

148
00:05:01,780 --> 00:05:02,120
you know,

149
00:05:03,080 --> 00:05:03,680
caught software

150
00:05:03,680 --> 00:05:04,580
and things like that.

151
00:05:05,140 --> 00:05:06,780
But that does seem also,

152
00:05:07,100 --> 00:05:07,300
you know,

153
00:05:07,360 --> 00:05:08,620
it kind of adds to,

154
00:05:09,220 --> 00:05:10,060
if I were to summarize

155
00:05:10,060 --> 00:05:11,340
a lot of what you're saying,

156
00:05:11,660 --> 00:05:12,480
it's the old phrase,

157
00:05:12,580 --> 00:05:13,860
like if it ain't broke,

158
00:05:13,940 --> 00:05:14,560
don't fix it,

159
00:05:14,880 --> 00:05:15,580
which I think is

160
00:05:15,580 --> 00:05:16,960
maybe not like

161
00:05:16,960 --> 00:05:18,800
the flashiest thing,

162
00:05:19,140 --> 00:05:19,660
right?

163
00:05:19,740 --> 00:05:20,900
But it's sort of like

164
00:05:20,900 --> 00:05:21,880
this works

165
00:05:21,880 --> 00:05:23,200
and it's cost effective

166
00:05:23,200 --> 00:05:24,140
and it's achieving

167
00:05:24,140 --> 00:05:25,220
what we want, right?

168
00:05:25,320 --> 00:05:27,020
And so we don't necessarily

169
00:05:27,020 --> 00:05:28,260
need to gratuitously

170
00:05:28,260 --> 00:05:29,320
move something around.

171
00:05:29,960 --> 00:05:30,400
And I think,

172
00:05:30,620 --> 00:05:31,820
I think,

173
00:05:31,860 --> 00:05:32,280
I think when I,

174
00:05:32,320 --> 00:05:33,140
when I've been looking through

175
00:05:33,140 --> 00:05:33,940
like where,

176
00:05:33,940 --> 00:05:34,440
you know,

177
00:05:34,840 --> 00:05:35,780
this kind of equilibrium

178
00:05:35,780 --> 00:05:36,560
between private

179
00:05:36,560 --> 00:05:37,300
and public cloud,

180
00:05:37,520 --> 00:05:39,060
that's a lot of what you're saying

181
00:05:39,060 --> 00:05:39,640
and that notion

182
00:05:39,640 --> 00:05:40,980
is what I've come back to a lot

183
00:05:40,980 --> 00:05:41,280
is

184
00:05:41,280 --> 00:05:43,020
the applications

185
00:05:43,020 --> 00:05:43,700
have kind of

186
00:05:43,700 --> 00:05:44,620
sorted themselves

187
00:05:44,620 --> 00:05:45,680
into where they belong

188
00:05:45,680 --> 00:05:46,640
by the criteria

189
00:05:46,640 --> 00:05:49,160
that you would have

190
00:05:49,160 --> 00:05:50,420
for selecting where they are,

191
00:05:50,540 --> 00:05:50,720
which,

192
00:05:51,080 --> 00:05:51,540
which I,

193
00:05:51,540 --> 00:05:52,520
I think works out well.

194
00:05:52,560 --> 00:05:53,320
And the other thing

195
00:05:53,320 --> 00:05:54,540
that I think is,

196
00:05:54,600 --> 00:05:55,280
is worth

197
00:05:55,280 --> 00:05:56,720
bringing up

198
00:05:56,720 --> 00:05:57,240
is,

199
00:05:57,620 --> 00:05:58,200
of course,

200
00:05:58,540 --> 00:06:00,200
our concerns

201
00:06:00,200 --> 00:06:01,300
for the most part

202
00:06:01,300 --> 00:06:02,000
are scoped down

203
00:06:02,000 --> 00:06:02,660
to applications

204
00:06:02,660 --> 00:06:03,500
that people write.

205
00:06:03,800 --> 00:06:04,520
Like you were saying,

206
00:06:04,580 --> 00:06:05,820
if you're only concerned

207
00:06:05,820 --> 00:06:06,620
with infrastructure,

208
00:06:06,620 --> 00:06:08,180
it's kind of

209
00:06:08,180 --> 00:06:09,440
a different set

210
00:06:09,440 --> 00:06:09,920
of thinking,

211
00:06:10,220 --> 00:06:10,480
right?

212
00:06:10,620 --> 00:06:10,980
And,

213
00:06:11,060 --> 00:06:11,200
you know,

214
00:06:11,200 --> 00:06:11,800
you might end up

215
00:06:11,800 --> 00:06:12,600
on either side

216
00:06:12,600 --> 00:06:13,100
of the firewall,

217
00:06:13,460 --> 00:06:15,820
but for software developers

218
00:06:15,820 --> 00:06:16,360
and the people

219
00:06:16,360 --> 00:06:17,220
supporting them,

220
00:06:17,780 --> 00:06:18,860
like,

221
00:06:19,060 --> 00:06:19,780
what is it

222
00:06:19,780 --> 00:06:20,560
they're looking for

223
00:06:20,560 --> 00:06:21,500
to layer on top

224
00:06:21,500 --> 00:06:22,240
of that infrastructure?

225
00:06:22,740 --> 00:06:22,920
I mean,

226
00:06:23,000 --> 00:06:23,260
look,

227
00:06:23,640 --> 00:06:24,580
maybe the way

228
00:06:24,580 --> 00:06:25,140
I would

229
00:06:25,140 --> 00:06:26,780
talk about this

230
00:06:26,780 --> 00:06:27,080
is,

231
00:06:27,700 --> 00:06:28,840
you brought up

232
00:06:28,840 --> 00:06:29,720
a very interesting thing.

233
00:06:30,260 --> 00:06:31,020
Nobody should go

234
00:06:31,020 --> 00:06:32,220
to any environment

235
00:06:32,220 --> 00:06:32,940
just for the sake

236
00:06:32,940 --> 00:06:33,280
of it,

237
00:06:33,320 --> 00:06:33,480
right?

238
00:06:33,740 --> 00:06:34,000
Oh,

239
00:06:34,000 --> 00:06:34,680
I have an edict

240
00:06:34,680 --> 00:06:35,600
to go to public cloud

241
00:06:35,600 --> 00:06:36,220
or I have an edict

242
00:06:36,220 --> 00:06:37,620
to go to private cloud,

243
00:06:37,680 --> 00:06:37,820
right?

244
00:06:38,100 --> 00:06:39,540
You have to go back,

245
00:06:40,060 --> 00:06:40,540
unfortunately,

246
00:06:40,780 --> 00:06:41,340
and look at

247
00:06:41,340 --> 00:06:42,820
some more mundane things.

248
00:06:43,140 --> 00:06:44,120
What am I trying to drive?

249
00:06:44,220 --> 00:06:44,880
Am I trying to drive

250
00:06:44,880 --> 00:06:45,540
business velocity?

251
00:06:45,740 --> 00:06:46,460
Am I trying to drive

252
00:06:46,460 --> 00:06:47,080
better ROI?

253
00:06:47,360 --> 00:06:48,080
Am I trying to drive

254
00:06:48,080 --> 00:06:48,680
better security,

255
00:06:48,820 --> 00:06:49,400
better governance?

256
00:06:50,060 --> 00:06:50,420
And so,

257
00:06:51,040 --> 00:06:52,860
and can I,

258
00:06:53,180 --> 00:06:54,320
if something is missing,

259
00:06:54,980 --> 00:06:55,220
how do,

260
00:06:55,320 --> 00:06:56,160
what is my fastest

261
00:06:56,160 --> 00:06:58,060
and most economical way

262
00:06:58,060 --> 00:06:59,500
to get to the right answer?

263
00:07:00,100 --> 00:07:02,200
And often when you look

264
00:07:02,200 --> 00:07:04,260
at this type of questioning,

265
00:07:04,760 --> 00:07:05,900
which is an apps down

266
00:07:05,900 --> 00:07:07,020
or a business down

267
00:07:07,020 --> 00:07:07,500
questioning,

268
00:07:08,560 --> 00:07:09,600
then you say,

269
00:07:09,680 --> 00:07:09,760
okay,

270
00:07:09,780 --> 00:07:10,540
there is one choice

271
00:07:10,540 --> 00:07:11,100
which is probably

272
00:07:11,100 --> 00:07:11,900
called private cloud,

273
00:07:11,980 --> 00:07:12,900
but the second one is,

274
00:07:13,280 --> 00:07:13,960
how do I get

275
00:07:13,960 --> 00:07:15,060
the business velocity

276
00:07:15,060 --> 00:07:15,620
that I want?

277
00:07:15,880 --> 00:07:17,960
And many times

278
00:07:17,960 --> 00:07:19,780
people make the move

279
00:07:19,780 --> 00:07:20,420
to,

280
00:07:20,880 --> 00:07:21,220
let us say,

281
00:07:21,300 --> 00:07:21,480
they are,

282
00:07:21,700 --> 00:07:22,980
they've got a good platform

283
00:07:22,980 --> 00:07:23,740
running on-prem

284
00:07:23,740 --> 00:07:24,620
and then they move

285
00:07:24,620 --> 00:07:25,440
to a public cloud

286
00:07:25,440 --> 00:07:25,700
and say,

287
00:07:25,760 --> 00:07:25,840
oh,

288
00:07:25,860 --> 00:07:26,620
I moved to EKS,

289
00:07:26,740 --> 00:07:27,540
I moved to EKS

290
00:07:27,540 --> 00:07:28,580
and I've opened

291
00:07:28,580 --> 00:07:29,240
the floodgates

292
00:07:29,240 --> 00:07:29,980
to my developers,

293
00:07:30,360 --> 00:07:32,080
but now the developers

294
00:07:32,080 --> 00:07:33,080
instead of writing code

295
00:07:33,080 --> 00:07:33,680
are managing

296
00:07:33,680 --> 00:07:34,480
public cloud

297
00:07:34,480 --> 00:07:35,440
infrastructure components.

298
00:07:35,600 --> 00:07:36,340
They're trying to figure out

299
00:07:36,340 --> 00:07:37,380
how to patch and update it.

300
00:07:37,580 --> 00:07:38,300
They're trying to figure out

301
00:07:38,300 --> 00:07:38,920
how to scale it,

302
00:07:38,960 --> 00:07:40,540
how to do availability zones

303
00:07:40,540 --> 00:07:41,120
and regions.

304
00:07:42,080 --> 00:07:43,980
So what you do is

305
00:07:43,980 --> 00:07:46,260
you still throw

306
00:07:46,260 --> 00:07:47,180
a lot of complexity

307
00:07:47,180 --> 00:07:48,220
and so from a business

308
00:07:48,220 --> 00:07:49,140
goal perspective,

309
00:07:50,140 --> 00:07:51,080
when you start

310
00:07:51,080 --> 00:07:51,820
measuring yourself,

311
00:07:51,940 --> 00:07:52,780
did you achieve

312
00:07:52,780 --> 00:07:53,400
that velocity?

313
00:07:54,000 --> 00:07:55,200
How long does it take

314
00:07:55,200 --> 00:07:56,700
from the time

315
00:07:56,700 --> 00:07:57,340
you write code

316
00:07:57,340 --> 00:07:58,460
to getting into production?

317
00:07:59,180 --> 00:08:00,180
Be it public cloud cloud

318
00:08:00,180 --> 00:08:00,880
or private cloud?

319
00:08:01,260 --> 00:08:02,280
What we find is

320
00:08:02,280 --> 00:08:03,140
often there is

321
00:08:03,140 --> 00:08:04,600
a missing element.

322
00:08:05,300 --> 00:08:07,160
developers should not,

323
00:08:07,920 --> 00:08:08,740
whether self-service

324
00:08:08,740 --> 00:08:09,280
or not,

325
00:08:09,860 --> 00:08:10,620
be managing

326
00:08:10,620 --> 00:08:11,740
the underlying infrastructure

327
00:08:11,740 --> 00:08:13,080
because when they

328
00:08:13,080 --> 00:08:14,020
have to do that,

329
00:08:14,660 --> 00:08:15,180
that is when

330
00:08:15,180 --> 00:08:16,040
they lose velocity.

331
00:08:16,580 --> 00:08:17,360
Imagine if all

332
00:08:17,360 --> 00:08:17,840
the developers

333
00:08:17,840 --> 00:08:18,380
had to do

334
00:08:18,380 --> 00:08:19,520
was write the business logic,

335
00:08:19,660 --> 00:08:20,240
write the code,

336
00:08:20,940 --> 00:08:22,360
specify their intent

337
00:08:22,360 --> 00:08:23,600
on how the code

338
00:08:23,600 --> 00:08:24,080
should run

339
00:08:24,080 --> 00:08:25,220
and walk away.

340
00:08:25,780 --> 00:08:26,920
When I say intent,

341
00:08:27,140 --> 00:08:27,320
hey,

342
00:08:27,460 --> 00:08:28,380
I built an application

343
00:08:28,380 --> 00:08:29,320
this is the business logic,

344
00:08:29,660 --> 00:08:30,880
I wanted to run HA,

345
00:08:31,420 --> 00:08:32,220
I wanted to have

346
00:08:32,220 --> 00:08:32,540
high,

347
00:08:32,960 --> 00:08:34,620
low latency networking,

348
00:08:35,180 --> 00:08:35,940
connectivity,

349
00:08:36,460 --> 00:08:37,140
I wanted to

350
00:08:37,140 --> 00:08:38,040
automatically do

351
00:08:38,040 --> 00:08:39,100
PII data filtering

352
00:08:39,100 --> 00:08:40,460
and by the way,

353
00:08:40,880 --> 00:08:42,620
when it hits

354
00:08:42,620 --> 00:08:43,020
more than

355
00:08:43,020 --> 00:08:44,040
X number of transactions,

356
00:08:44,180 --> 00:08:44,560
I want to

357
00:08:44,560 --> 00:08:45,340
automatically scale.

358
00:08:46,360 --> 00:08:47,300
These might be

359
00:08:47,300 --> 00:08:48,500
the kinds of intent

360
00:08:48,500 --> 00:08:49,220
that the developer

361
00:08:49,220 --> 00:08:50,220
does,

362
00:08:50,600 --> 00:08:51,460
but today instead,

363
00:08:51,580 --> 00:08:52,280
a developer is sitting

364
00:08:52,280 --> 00:08:52,820
and managing

365
00:08:52,820 --> 00:08:53,500
YAML files

366
00:08:53,500 --> 00:08:54,120
and configurations,

367
00:08:54,580 --> 00:08:55,160
so they took

368
00:08:55,160 --> 00:08:55,740
a whole bunch

369
00:08:55,740 --> 00:08:56,300
of workloads,

370
00:08:56,920 --> 00:08:57,580
moved it to,

371
00:08:58,000 --> 00:08:58,300
let us say,

372
00:08:58,400 --> 00:08:59,460
a public cloud,

373
00:08:59,720 --> 00:09:00,420
but still on the

374
00:09:00,420 --> 00:09:01,100
raw infrastructure,

375
00:09:01,240 --> 00:09:01,800
be it Kubernetes

376
00:09:01,800 --> 00:09:02,620
or VMs,

377
00:09:02,680 --> 00:09:03,200
and they are sitting

378
00:09:03,200 --> 00:09:04,060
and managing those.

379
00:09:05,120 --> 00:09:06,120
And that is where

380
00:09:06,120 --> 00:09:07,940
the debate

381
00:09:07,940 --> 00:09:09,300
changes course

382
00:09:09,300 --> 00:09:10,140
or directions

383
00:09:10,140 --> 00:09:10,900
and it becomes

384
00:09:10,900 --> 00:09:11,620
less of,

385
00:09:12,220 --> 00:09:12,340
hey,

386
00:09:12,400 --> 00:09:13,240
you will get a cloud

387
00:09:13,240 --> 00:09:14,080
and an IaaS layer

388
00:09:14,080 --> 00:09:14,440
anywhere,

389
00:09:14,860 --> 00:09:16,480
but that is insufficient

390
00:09:16,480 --> 00:09:17,800
to truly drive

391
00:09:17,800 --> 00:09:18,620
business value.

392
00:09:19,260 --> 00:09:20,020
What you need

393
00:09:20,020 --> 00:09:20,700
is that

394
00:09:20,700 --> 00:09:22,460
platform layer

395
00:09:22,460 --> 00:09:23,740
that sits on top

396
00:09:23,740 --> 00:09:24,560
of any IaaS,

397
00:09:24,580 --> 00:09:27,260
and that abstracts

398
00:09:27,260 --> 00:09:27,900
that infrastructure

399
00:09:27,900 --> 00:09:29,100
so that a developer

400
00:09:29,100 --> 00:09:30,480
can just write code,

401
00:09:31,900 --> 00:09:32,520
say a command

402
00:09:32,520 --> 00:09:33,400
saying deploy it

403
00:09:33,400 --> 00:09:34,240
with all my intent

404
00:09:34,240 --> 00:09:34,840
and walk.

405
00:09:36,000 --> 00:09:37,060
And that is where

406
00:09:37,060 --> 00:09:38,120
Tanzu fits in.

407
00:09:38,740 --> 00:09:39,360
And we have fit in

408
00:09:39,360 --> 00:09:40,220
there always,

409
00:09:40,300 --> 00:09:40,460
right?

410
00:09:40,580 --> 00:09:41,120
You know that.

411
00:09:41,380 --> 00:09:41,760
The thinking,

412
00:09:42,020 --> 00:09:42,360
you know,

413
00:09:42,640 --> 00:09:43,140
you're kind of,

414
00:09:43,200 --> 00:09:44,360
you're putting in my head,

415
00:09:44,720 --> 00:09:46,380
not forcefully,

416
00:09:46,640 --> 00:09:47,020
but you know,

417
00:09:47,120 --> 00:09:48,920
through what you're saying

418
00:09:48,920 --> 00:09:50,060
is scopes down

419
00:09:50,060 --> 00:09:50,800
to developers

420
00:09:50,800 --> 00:09:51,460
and, you know,

421
00:09:51,460 --> 00:09:52,340
your own applications

422
00:09:52,340 --> 00:09:53,520
to put it in air quotes

423
00:09:53,520 --> 00:09:54,520
like the cloud,

424
00:09:54,580 --> 00:09:55,460
is less important

425
00:09:55,460 --> 00:09:56,540
than the platform,

426
00:09:56,940 --> 00:09:57,180
right?

427
00:09:57,260 --> 00:09:57,480
Like,

428
00:09:57,880 --> 00:09:59,900
if your idea is

429
00:09:59,900 --> 00:10:01,640
we're going to move

430
00:10:01,640 --> 00:10:04,080
to the public cloud

431
00:10:04,080 --> 00:10:05,980
and that there's a period

432
00:10:05,980 --> 00:10:06,340
at the end

433
00:10:06,340 --> 00:10:07,720
of that annual strategy,

434
00:10:07,960 --> 00:10:08,740
right?

435
00:10:08,860 --> 00:10:09,000
Like,

436
00:10:09,220 --> 00:10:09,900
like you need

437
00:10:09,900 --> 00:10:11,780
for app,

438
00:10:11,860 --> 00:10:13,040
for some workloads

439
00:10:13,040 --> 00:10:13,800
that might make sense,

440
00:10:13,860 --> 00:10:14,600
for infrastructure,

441
00:10:15,080 --> 00:10:15,380
you know,

442
00:10:15,440 --> 00:10:16,860
if it works out for it,

443
00:10:16,900 --> 00:10:17,340
then sure,

444
00:10:17,740 --> 00:10:18,540
and there might be good

445
00:10:18,540 --> 00:10:19,400
on-premises reasons

446
00:10:19,400 --> 00:10:19,880
as well,

447
00:10:19,880 --> 00:10:21,220
but there's more nuance

448
00:10:21,220 --> 00:10:21,840
when it comes to

449
00:10:21,840 --> 00:10:22,860
application developers

450
00:10:22,860 --> 00:10:24,720
and they don't

451
00:10:24,720 --> 00:10:25,880
necessarily benefit

452
00:10:25,880 --> 00:10:27,800
from infrastructure

453
00:10:27,800 --> 00:10:28,520
as a service.

454
00:10:28,700 --> 00:10:29,760
They want a platform,

455
00:10:30,160 --> 00:10:30,440
right?

456
00:10:30,540 --> 00:10:30,960
And so,

457
00:10:31,060 --> 00:10:32,160
that's really like

458
00:10:32,160 --> 00:10:32,880
where the conversation

459
00:10:32,880 --> 00:10:33,420
for developers is important.

460
00:10:33,420 --> 00:10:34,460
We need a platform.

461
00:10:34,520 --> 00:10:35,020
cloud parts.

462
00:10:35,820 --> 00:10:36,260
Exactly,

463
00:10:36,520 --> 00:10:36,660
right?

464
00:10:36,680 --> 00:10:36,940
Otherwise,

465
00:10:37,100 --> 00:10:37,640
as you're saying,

466
00:10:37,760 --> 00:10:38,500
you end up being

467
00:10:38,500 --> 00:10:39,400
a YAML programmer

468
00:10:39,400 --> 00:10:40,500
or whatever else

469
00:10:40,500 --> 00:10:41,100
comes along,

470
00:10:41,300 --> 00:10:41,560
right?

471
00:10:41,660 --> 00:10:43,880
And I think you're right.

472
00:10:44,000 --> 00:10:46,440
That's what I've seen

473
00:10:46,440 --> 00:10:47,000
a lot of people

474
00:10:47,000 --> 00:10:47,860
lose sight of

475
00:10:47,860 --> 00:10:49,380
when they're figuring out

476
00:10:49,380 --> 00:10:50,560
whatever infrastructure

477
00:10:50,560 --> 00:10:51,240
they want,

478
00:10:51,500 --> 00:10:52,600
wherever it might be run,

479
00:10:52,720 --> 00:10:54,040
is to kind of lose sight

480
00:10:54,040 --> 00:10:56,260
of that developer experience

481
00:10:56,260 --> 00:10:58,340
that you get

482
00:10:58,340 --> 00:10:59,080
with a platform.

483
00:10:59,400 --> 00:10:59,700
True,

484
00:10:59,820 --> 00:10:59,980
true.

485
00:11:00,180 --> 00:11:01,240
And this is where,

486
00:11:01,740 --> 00:11:03,120
you know,

487
00:11:03,500 --> 00:11:04,680
we often have to spend

488
00:11:04,680 --> 00:11:05,380
some time

489
00:11:05,380 --> 00:11:06,560
talking about,

490
00:11:06,700 --> 00:11:06,800
okay,

491
00:11:07,220 --> 00:11:08,700
so what does that platform do?

492
00:11:08,920 --> 00:11:09,920
What does that platform

493
00:11:09,920 --> 00:11:10,780
need to do?

494
00:11:11,400 --> 00:11:12,500
And if you say that,

495
00:11:12,580 --> 00:11:12,680
look,

496
00:11:12,720 --> 00:11:13,520
it's all about

497
00:11:13,520 --> 00:11:14,340
velocity,

498
00:11:14,760 --> 00:11:15,780
application velocity

499
00:11:15,780 --> 00:11:17,260
at scale

500
00:11:17,260 --> 00:11:18,080
with security

501
00:11:18,080 --> 00:11:19,020
with performance,

502
00:11:19,540 --> 00:11:20,460
then

503
00:11:20,460 --> 00:11:22,060
the platform

504
00:11:22,060 --> 00:11:22,680
has to have

505
00:11:22,680 --> 00:11:24,260
adhere to certain tenets.

506
00:11:24,640 --> 00:11:24,720
Now,

507
00:11:24,800 --> 00:11:24,980
look,

508
00:11:25,540 --> 00:11:25,760
Coté,

509
00:11:25,760 --> 00:11:26,280
we have been

510
00:11:26,280 --> 00:11:27,580
in the platform business

511
00:11:27,580 --> 00:11:28,540
for over 10 years.

512
00:11:28,840 --> 00:11:29,520
We've got customers

513
00:11:29,520 --> 00:11:30,060
who are running

514
00:11:30,060 --> 00:11:31,420
massive scale applications

515
00:11:31,420 --> 00:11:32,560
on top of our platform,

516
00:11:32,900 --> 00:11:33,520
be it on public

517
00:11:33,520 --> 00:11:34,280
or private cloud.

518
00:11:35,020 --> 00:11:36,140
And what we learned

519
00:11:36,140 --> 00:11:37,360
from all of that

520
00:11:37,360 --> 00:11:37,800
is

521
00:11:37,800 --> 00:11:39,800
while now

522
00:11:39,800 --> 00:11:40,900
the platform engineering

523
00:11:40,900 --> 00:11:42,360
is getting in vogue

524
00:11:42,360 --> 00:11:43,160
and I'm very happy

525
00:11:43,160 --> 00:11:43,700
for that,

526
00:11:44,620 --> 00:11:45,600
the years of experience

527
00:11:45,600 --> 00:11:46,120
have taught us

528
00:11:46,120 --> 00:11:46,680
that there are three

529
00:11:46,680 --> 00:11:47,340
simple things

530
00:11:47,340 --> 00:11:47,740
that you should

531
00:11:47,740 --> 00:11:48,380
always consider.

532
00:11:49,220 --> 00:11:50,620
If you truly want

533
00:11:50,620 --> 00:11:51,620
that business velocity,

534
00:11:52,700 --> 00:11:53,700
the developer experience

535
00:11:53,700 --> 00:11:54,760
has to be simple

536
00:11:54,760 --> 00:11:57,680
and should be abstracted

537
00:11:57,680 --> 00:11:58,480
from the infrastructure.

538
00:11:58,480 --> 00:12:00,700
It has to be tied

539
00:12:00,700 --> 00:12:01,960
to what the developer needs

540
00:12:01,960 --> 00:12:02,340
which is,

541
00:12:02,460 --> 00:12:02,560
hey,

542
00:12:02,960 --> 00:12:04,120
how can I build

543
00:12:04,120 --> 00:12:05,300
my application faster?

544
00:12:05,540 --> 00:12:07,120
How can I write

545
00:12:07,120 --> 00:12:08,200
my application faster?

546
00:12:08,520 --> 00:12:09,120
So do I have

547
00:12:09,120 --> 00:12:10,140
the right scaffolding?

548
00:12:10,580 --> 00:12:11,280
This is where

549
00:12:11,280 --> 00:12:12,920
all the pioneering work

550
00:12:12,920 --> 00:12:13,400
for example

551
00:12:13,400 --> 00:12:13,920
that we have done

552
00:12:13,920 --> 00:12:14,340
with Spring

553
00:12:14,340 --> 00:12:15,320
and Spring Framework

554
00:12:15,320 --> 00:12:16,020
really fit in.

555
00:12:16,680 --> 00:12:17,520
The second one is,

556
00:12:17,620 --> 00:12:17,660
hey,

557
00:12:17,740 --> 00:12:18,620
once I've built it,

558
00:12:19,140 --> 00:12:20,100
once I've written it,

559
00:12:20,160 --> 00:12:21,040
can I quickly build it

560
00:12:21,040 --> 00:12:21,940
into a secure container

561
00:12:21,940 --> 00:12:22,820
without worrying

562
00:12:22,820 --> 00:12:23,560
about packages

563
00:12:23,560 --> 00:12:24,300
and where

564
00:12:24,300 --> 00:12:24,980
the dependencies

565
00:12:24,980 --> 00:12:25,600
come from?

566
00:12:25,600 --> 00:12:27,420
Can I,

567
00:12:27,580 --> 00:12:28,580
with a single command,

568
00:12:28,660 --> 00:12:29,180
deploy it?

569
00:12:29,880 --> 00:12:30,180
Can I,

570
00:12:30,240 --> 00:12:30,920
with a single command,

571
00:12:31,020 --> 00:12:32,120
bind to external services

572
00:12:32,120 --> 00:12:32,700
and scale?

573
00:12:33,640 --> 00:12:34,300
That is it.

574
00:12:34,740 --> 00:12:35,600
It is interesting

575
00:12:35,600 --> 00:12:36,300
when you look at

576
00:12:36,300 --> 00:12:37,680
the sum total universe

577
00:12:37,680 --> 00:12:38,660
of what developer

578
00:12:38,660 --> 00:12:39,840
commands are needed.

579
00:12:40,060 --> 00:12:40,460
That's all.

580
00:12:41,800 --> 00:12:42,960
VM as a service,

581
00:12:43,320 --> 00:12:44,500
Kubernetes as a service,

582
00:12:44,620 --> 00:12:45,420
database as a service,

583
00:12:45,420 --> 00:12:46,900
all become subcomponents

584
00:12:46,900 --> 00:12:48,340
at the infrastructure level.

585
00:12:49,180 --> 00:12:50,760
But that is what

586
00:12:50,760 --> 00:12:51,620
a developer needs.

587
00:12:52,060 --> 00:12:52,880
So that's number one.

588
00:12:53,360 --> 00:12:54,060
Developer experience

589
00:12:54,060 --> 00:12:54,880
must be simple

590
00:12:54,880 --> 00:12:56,600
for it to be truly effective,

591
00:12:56,920 --> 00:12:57,720
safe, and secure.

592
00:12:58,480 --> 00:12:59,520
And the simplicity

593
00:12:59,520 --> 00:13:00,900
just is build,

594
00:13:01,020 --> 00:13:01,960
mine, deploy, scale.

595
00:13:02,260 --> 00:13:02,920
That's all you need.

596
00:13:03,060 --> 00:13:03,840
The second tenet

597
00:13:03,840 --> 00:13:06,080
is that the platform,

598
00:13:07,020 --> 00:13:07,940
a template-driven

599
00:13:07,940 --> 00:13:09,000
provisioning doesn't work.

600
00:13:09,200 --> 00:13:10,220
Imagine, you know,

601
00:13:10,220 --> 00:13:11,060
somebody curates

602
00:13:11,060 --> 00:13:11,360
and says,

603
00:13:11,500 --> 00:13:11,940
oh, I talked

604
00:13:11,940 --> 00:13:12,460
to the developer,

605
00:13:12,660 --> 00:13:13,260
their app

606
00:13:13,260 --> 00:13:16,020
has got a front-end,

607
00:13:16,120 --> 00:13:16,500
it has got

608
00:13:16,500 --> 00:13:17,280
a back-end database

609
00:13:17,280 --> 00:13:18,260
and it is replicated

610
00:13:18,260 --> 00:13:19,080
across two regions.

611
00:13:19,180 --> 00:13:19,700
I'm going to write

612
00:13:19,700 --> 00:13:20,980
a nice template

613
00:13:20,980 --> 00:13:22,380
to go deploy it.

614
00:13:22,520 --> 00:13:23,100
And every time

615
00:13:23,100 --> 00:13:24,200
the developer clicks

616
00:13:24,200 --> 00:13:24,540
deploy,

617
00:13:24,660 --> 00:13:25,380
the template

618
00:13:25,380 --> 00:13:26,280
will go and deploy it.

619
00:13:26,740 --> 00:13:27,880
That is completely

620
00:13:27,880 --> 00:13:29,500
a rigid model

621
00:13:29,500 --> 00:13:30,340
that breaks,

622
00:13:30,600 --> 00:13:30,980
I would say,

623
00:13:31,020 --> 00:13:31,800
within a few hours,

624
00:13:31,840 --> 00:13:32,060
right,

625
00:13:32,120 --> 00:13:32,680
when you suddenly

626
00:13:32,680 --> 00:13:33,640
decide to make a change.

627
00:13:34,240 --> 00:13:35,020
So template-driven

628
00:13:35,020 --> 00:13:35,580
provisioning

629
00:13:35,580 --> 00:13:36,500
is not what you need.

630
00:13:37,160 --> 00:13:37,900
The second tenet

631
00:13:37,900 --> 00:13:38,740
is infrastructure

632
00:13:38,740 --> 00:13:40,100
must be dynamically

633
00:13:40,100 --> 00:13:40,780
provisioned

634
00:13:40,780 --> 00:13:42,000
to meet the app needs.

635
00:13:42,580 --> 00:13:43,160
And that is where

636
00:13:43,160 --> 00:13:43,920
the platform layer

637
00:13:43,920 --> 00:13:44,340
comes in.

638
00:13:44,440 --> 00:13:45,460
It takes these commands,

639
00:13:45,780 --> 00:13:46,360
takes the intent

640
00:13:46,360 --> 00:13:46,960
of developer

641
00:13:46,960 --> 00:13:48,180
and translates

642
00:13:48,180 --> 00:13:48,980
it dynamically

643
00:13:48,980 --> 00:13:49,660
into what

644
00:13:49,660 --> 00:13:50,420
the infrastructure

645
00:13:50,420 --> 00:13:51,140
needs to be.

646
00:13:51,140 --> 00:13:52,420
It may call templates

647
00:13:52,420 --> 00:13:53,700
to do it,

648
00:13:53,760 --> 00:13:54,480
but it doesn't matter.

649
00:13:54,920 --> 00:13:55,260
It is,

650
00:13:55,360 --> 00:13:55,880
you know,

651
00:13:55,920 --> 00:13:56,680
dynamically done.

652
00:13:57,060 --> 00:13:58,500
And then the last tenet

653
00:13:58,500 --> 00:13:59,060
we heard

654
00:13:59,060 --> 00:14:00,120
and we have learned

655
00:14:00,120 --> 00:14:01,440
is there are

656
00:14:01,440 --> 00:14:02,580
some boring things

657
00:14:02,580 --> 00:14:04,140
that people have

658
00:14:04,140 --> 00:14:04,480
to do

659
00:14:04,480 --> 00:14:05,500
and platform

660
00:14:05,500 --> 00:14:06,420
has to solve

661
00:14:06,420 --> 00:14:06,840
for it.

662
00:14:08,140 --> 00:14:08,700
Logging,

663
00:14:09,300 --> 00:14:09,740
auditing,

664
00:14:10,560 --> 00:14:11,580
credential management

665
00:14:11,580 --> 00:14:12,200
and rotation

666
00:14:12,200 --> 00:14:12,960
automatically,

667
00:14:13,620 --> 00:14:14,600
automatic connection

668
00:14:14,600 --> 00:14:15,200
and brokering

669
00:14:15,200 --> 00:14:15,220
and brokering

670
00:14:15,220 --> 00:14:15,700
to external

671
00:14:15,700 --> 00:14:16,340
services,

672
00:14:17,240 --> 00:14:17,420
right?

673
00:14:17,940 --> 00:14:18,460
Automatic

674
00:14:18,460 --> 00:14:19,120
repaving

675
00:14:19,120 --> 00:14:19,760
of your

676
00:14:19,760 --> 00:14:20,320
underlying

677
00:14:20,320 --> 00:14:21,000
infrastructure

678
00:14:21,000 --> 00:14:21,460
that app

679
00:14:21,460 --> 00:14:21,980
runs on

680
00:14:21,980 --> 00:14:22,920
and automatic

681
00:14:22,920 --> 00:14:23,780
repair of app.

682
00:14:24,340 --> 00:14:25,420
If all of this

683
00:14:25,420 --> 00:14:26,260
is not taken

684
00:14:26,260 --> 00:14:26,720
care of,

685
00:14:26,760 --> 00:14:27,600
this boring stuff

686
00:14:27,600 --> 00:14:28,360
and you just

687
00:14:28,360 --> 00:14:29,020
do a flashy

688
00:14:29,020 --> 00:14:29,900
nice deployment

689
00:14:29,900 --> 00:14:30,880
and then

690
00:14:30,880 --> 00:14:31,820
let the

691
00:14:31,820 --> 00:14:32,400
communities

692
00:14:32,400 --> 00:14:32,920
do the load

693
00:14:32,920 --> 00:14:33,300
balancing

694
00:14:33,300 --> 00:14:33,780
but really

695
00:14:33,780 --> 00:14:34,280
none of the

696
00:14:34,280 --> 00:14:34,820
other stuff

697
00:14:34,820 --> 00:14:35,180
is done,

698
00:14:35,940 --> 00:14:36,580
you still

699
00:14:36,580 --> 00:14:37,140
have an

700
00:14:37,140 --> 00:14:37,560
incomplete

701
00:14:37,560 --> 00:14:38,100
solution.

702
00:14:38,880 --> 00:14:39,760
So the platform

703
00:14:39,760 --> 00:14:40,420
has to meet

704
00:14:40,420 --> 00:14:40,780
these three

705
00:14:40,780 --> 00:14:41,140
tenets.

706
00:14:41,800 --> 00:14:42,160
Simple

707
00:14:42,160 --> 00:14:42,500
developer

708
00:14:42,500 --> 00:14:43,100
experience,

709
00:14:43,760 --> 00:14:44,160
dynamically

710
00:14:44,160 --> 00:14:44,680
provisioned

711
00:14:44,680 --> 00:14:45,080
infrastructure

712
00:14:45,080 --> 00:14:46,220
and

713
00:14:46,220 --> 00:14:46,720
something

714
00:14:46,720 --> 00:14:47,000
that

715
00:14:47,000 --> 00:14:47,240
does

716
00:14:47,240 --> 00:14:47,460
day

717
00:14:47,460 --> 00:14:47,640
two

718
00:14:47,640 --> 00:14:48,160
boring

719
00:14:48,160 --> 00:14:48,760
operations

720
00:14:48,760 --> 00:14:49,200
like

721
00:14:49,200 --> 00:14:49,680
repair,

722
00:14:49,840 --> 00:14:50,160
rotate,

723
00:14:51,060 --> 00:14:51,320
you know,

724
00:14:51,720 --> 00:14:52,460
rebave.

725
00:14:53,020 --> 00:14:53,920
And that is

726
00:14:53,920 --> 00:14:54,380
what we have

727
00:14:54,380 --> 00:14:54,820
done with

728
00:14:54,820 --> 00:14:55,180
tons of

729
00:14:55,180 --> 00:14:55,600
platform,

730
00:14:55,860 --> 00:14:56,160
which as we

731
00:14:56,160 --> 00:14:56,340
said,

732
00:14:56,420 --> 00:14:56,560
look,

733
00:14:57,180 --> 00:14:57,620
it is,

734
00:14:58,100 --> 00:14:59,140
and since

735
00:14:59,140 --> 00:15:00,260
this is still

736
00:15:00,260 --> 00:15:01,140
in people's

737
00:15:01,140 --> 00:15:01,480
minds,

738
00:15:01,600 --> 00:15:01,980
it's still

739
00:15:01,980 --> 00:15:02,340
a new

740
00:15:02,340 --> 00:15:02,740
area.

741
00:15:03,240 --> 00:15:03,720
What it

742
00:15:03,720 --> 00:15:04,620
does is

743
00:15:04,620 --> 00:15:05,520
instead of

744
00:15:05,520 --> 00:15:06,040
issuing,

745
00:15:06,300 --> 00:15:06,780
I want a

746
00:15:06,780 --> 00:15:07,580
cluster or

747
00:15:07,580 --> 00:15:07,980
I want

748
00:15:07,980 --> 00:15:08,480
Kubernetes,

749
00:15:08,740 --> 00:15:08,860
this,

750
00:15:08,940 --> 00:15:09,120
that,

751
00:15:09,200 --> 00:15:09,540
etc.,

752
00:15:09,540 --> 00:15:09,920
which people

753
00:15:09,920 --> 00:15:10,200
are very

754
00:15:10,200 --> 00:15:10,580
enamored

755
00:15:10,580 --> 00:15:10,880
of,

756
00:15:11,520 --> 00:15:11,820
you say,

757
00:15:11,900 --> 00:15:12,040
hey,

758
00:15:12,520 --> 00:15:13,120
you go get

759
00:15:13,120 --> 00:15:13,420
me the

760
00:15:13,420 --> 00:15:13,720
Kubernetes

761
00:15:13,720 --> 00:15:14,360
clusters I

762
00:15:14,360 --> 00:15:14,540
need.

763
00:15:14,700 --> 00:15:15,080
I just

764
00:15:15,080 --> 00:15:15,380
want to

765
00:15:15,380 --> 00:15:15,800
say I

766
00:15:15,800 --> 00:15:15,980
want to

767
00:15:15,980 --> 00:15:16,420
deploy this

768
00:15:16,420 --> 00:15:16,720
app at

769
00:15:16,720 --> 00:15:16,960
scale.

770
00:15:17,720 --> 00:15:18,840
That is

771
00:15:18,840 --> 00:15:19,400
the big

772
00:15:19,400 --> 00:15:20,580
change or

773
00:15:20,580 --> 00:15:21,200
transformation.

774
00:15:21,920 --> 00:15:22,280
And often

775
00:15:22,280 --> 00:15:22,840
when business

776
00:15:22,840 --> 00:15:23,500
decisions are

777
00:15:23,500 --> 00:15:23,840
made,

778
00:15:24,740 --> 00:15:25,120
these are

779
00:15:25,120 --> 00:15:25,580
not understood.

780
00:15:25,820 --> 00:15:26,500
So I

781
00:15:26,500 --> 00:15:27,040
get a

782
00:15:27,040 --> 00:15:27,520
perplexing

783
00:15:27,520 --> 00:15:27,980
conversation

784
00:15:27,980 --> 00:15:28,480
sometimes,

785
00:15:28,560 --> 00:15:28,840
which is

786
00:15:28,840 --> 00:15:29,040
like,

787
00:15:29,100 --> 00:15:29,240
yep,

788
00:15:30,300 --> 00:15:31,600
we have a

789
00:15:31,600 --> 00:15:32,200
great platform

790
00:15:32,200 --> 00:15:32,760
on-prem and

791
00:15:32,760 --> 00:15:33,020
we are going

792
00:15:33,020 --> 00:15:33,260
to go to

793
00:15:33,260 --> 00:15:33,760
a platform

794
00:15:33,760 --> 00:15:34,340
in cloud.

795
00:15:34,460 --> 00:15:34,660
I said,

796
00:15:34,720 --> 00:15:34,880
great,

797
00:15:35,000 --> 00:15:35,320
what is a

798
00:15:35,320 --> 00:15:35,780
platform in

799
00:15:35,780 --> 00:15:35,920
cloud?

800
00:15:36,920 --> 00:15:37,140
Oh,

801
00:15:37,240 --> 00:15:37,680
platform in

802
00:15:37,680 --> 00:15:37,980
cloud is

803
00:15:37,980 --> 00:15:38,320
Kubernetes.

804
00:15:39,060 --> 00:15:39,240
I said,

805
00:15:39,300 --> 00:15:39,900
Kubernetes is

806
00:15:39,900 --> 00:15:40,500
infrastructure,

807
00:15:40,960 --> 00:15:41,400
it's not

808
00:15:41,400 --> 00:15:41,800
platform.

809
00:15:42,500 --> 00:15:43,760
So even

810
00:15:43,760 --> 00:15:44,160
when you go

811
00:15:44,160 --> 00:15:44,520
to cloud,

812
00:15:44,640 --> 00:15:45,540
you need a

813
00:15:45,540 --> 00:15:46,600
platform and

814
00:15:46,600 --> 00:15:46,940
even when

815
00:15:46,940 --> 00:15:47,460
you're on-prem,

816
00:15:47,540 --> 00:15:47,880
you need a

817
00:15:47,880 --> 00:15:48,260
platform.

818
00:15:49,040 --> 00:15:49,880
And the

819
00:15:49,880 --> 00:15:50,720
value of

820
00:15:50,720 --> 00:15:51,320
the platform

821
00:15:51,320 --> 00:15:53,180
is not

822
00:15:53,180 --> 00:15:53,820
measured

823
00:15:53,820 --> 00:15:55,180
based on

824
00:15:55,180 --> 00:15:55,980
the bean

825
00:15:55,980 --> 00:15:56,520
counting of

826
00:15:56,520 --> 00:15:56,840
how many

827
00:15:56,840 --> 00:15:57,400
VMs I'm

828
00:15:57,400 --> 00:15:57,700
managing,

829
00:15:57,800 --> 00:15:58,060
how many

830
00:15:58,060 --> 00:15:58,640
clusters I'm

831
00:15:58,640 --> 00:15:58,960
managing,

832
00:15:59,180 --> 00:15:59,880
but rather

833
00:15:59,880 --> 00:16:01,040
it's managed

834
00:16:01,040 --> 00:16:01,640
in terms of

835
00:16:01,640 --> 00:16:01,980
business

836
00:16:01,980 --> 00:16:02,460
outcomes.

837
00:16:03,320 --> 00:16:04,060
how much

838
00:16:04,060 --> 00:16:04,580
time did

839
00:16:04,580 --> 00:16:04,940
it take

840
00:16:04,940 --> 00:16:05,500
for me to

841
00:16:05,500 --> 00:16:06,020
get code

842
00:16:06,020 --> 00:16:06,540
to production

843
00:16:06,540 --> 00:16:07,260
before and

844
00:16:07,260 --> 00:16:07,520
after?

845
00:16:08,320 --> 00:16:08,880
If it is

846
00:16:08,880 --> 00:16:09,960
six months,

847
00:16:10,100 --> 00:16:10,500
does it go

848
00:16:10,500 --> 00:16:10,800
in six

849
00:16:10,800 --> 00:16:11,080
days?

850
00:16:12,200 --> 00:16:12,740
If it is

851
00:16:12,740 --> 00:16:13,100
six days,

852
00:16:13,160 --> 00:16:13,380
does it

853
00:16:13,380 --> 00:16:13,720
happen in

854
00:16:13,720 --> 00:16:14,080
six hours?

855
00:16:15,040 --> 00:16:15,960
How many

856
00:16:15,960 --> 00:16:17,000
security issues

857
00:16:17,000 --> 00:16:17,300
have I

858
00:16:17,300 --> 00:16:17,860
automatically

859
00:16:17,860 --> 00:16:18,580
avoided

860
00:16:18,580 --> 00:16:19,160
because of

861
00:16:19,160 --> 00:16:19,820
repaving and

862
00:16:19,820 --> 00:16:20,340
automatic

863
00:16:20,340 --> 00:16:20,880
repair?

864
00:16:21,600 --> 00:16:22,240
How many

865
00:16:22,240 --> 00:16:23,200
times have

866
00:16:23,200 --> 00:16:23,840
I managed

867
00:16:23,840 --> 00:16:24,780
to make

868
00:16:24,780 --> 00:16:25,200
sure that

869
00:16:25,200 --> 00:16:25,860
no external

870
00:16:25,860 --> 00:16:26,400
service,

871
00:16:27,600 --> 00:16:27,940
and we

872
00:16:27,940 --> 00:16:28,260
know many

873
00:16:28,260 --> 00:16:28,620
of those

874
00:16:28,620 --> 00:16:29,300
recent cases,

875
00:16:29,660 --> 00:16:30,320
impacts my

876
00:16:30,320 --> 00:16:31,060
application because

877
00:16:31,060 --> 00:16:31,380
I have

878
00:16:31,380 --> 00:16:31,580
got

879
00:16:31,580 --> 00:16:32,160
automatic

880
00:16:32,160 --> 00:16:32,940
credential

881
00:16:32,940 --> 00:16:33,580
timeout and

882
00:16:33,580 --> 00:16:33,880
credential

883
00:16:33,880 --> 00:16:34,320
rotation?

884
00:16:35,240 --> 00:16:35,600
And when

885
00:16:35,600 --> 00:16:36,020
you start

886
00:16:36,020 --> 00:16:36,680
measuring

887
00:16:36,680 --> 00:16:37,960
TCO this

888
00:16:37,960 --> 00:16:38,260
way,

889
00:16:39,040 --> 00:16:39,660
the value

890
00:16:39,660 --> 00:16:40,200
is just

891
00:16:40,200 --> 00:16:40,900
pretty

892
00:16:40,900 --> 00:16:41,780
immense,

893
00:16:42,100 --> 00:16:42,720
but more

894
00:16:42,720 --> 00:16:43,260
importantly,

895
00:16:43,580 --> 00:16:44,460
it becomes

896
00:16:44,460 --> 00:16:45,200
very clear to

897
00:16:45,200 --> 00:16:45,620
the business

898
00:16:45,620 --> 00:16:45,960
owners,

899
00:16:46,500 --> 00:16:47,000
and that is

900
00:16:47,000 --> 00:16:47,460
kind of what

901
00:16:47,460 --> 00:16:47,880
we have to

902
00:16:47,880 --> 00:16:48,460
do better as

903
00:16:48,460 --> 00:16:48,920
an industry.

904
00:16:49,420 --> 00:16:49,980
I like the

905
00:16:49,980 --> 00:16:50,280
distinction

906
00:16:50,280 --> 00:16:50,740
you made

907
00:16:50,740 --> 00:16:53,160
of a lot

908
00:16:53,160 --> 00:16:53,540
of people

909
00:16:53,540 --> 00:16:54,260
think of

910
00:16:54,260 --> 00:16:54,480
their

911
00:16:54,480 --> 00:16:55,120
infrastructure

912
00:16:55,120 --> 00:16:55,860
as their

913
00:16:55,860 --> 00:16:56,460
platform,

914
00:16:57,020 --> 00:16:57,500
and I

915
00:16:57,500 --> 00:16:58,660
think that

916
00:16:58,660 --> 00:16:59,340
thinking comes

917
00:16:59,340 --> 00:16:59,780
from,

918
00:17:00,440 --> 00:17:00,800
you know,

919
00:17:00,840 --> 00:17:01,480
you listed

920
00:17:01,480 --> 00:17:01,880
kind of the

921
00:17:01,880 --> 00:17:02,420
three things

922
00:17:02,420 --> 00:17:02,660
that a

923
00:17:02,660 --> 00:17:02,920
platform

924
00:17:02,920 --> 00:17:03,320
needs to

925
00:17:03,320 --> 00:17:03,580
do,

926
00:17:04,120 --> 00:17:04,460
and,

927
00:17:05,100 --> 00:17:05,340
you know,

928
00:17:05,380 --> 00:17:05,960
even using

929
00:17:05,960 --> 00:17:06,280
the word

930
00:17:06,280 --> 00:17:07,080
boring to

931
00:17:07,080 --> 00:17:07,860
describe that

932
00:17:07,860 --> 00:17:08,580
third bucket,

933
00:17:09,020 --> 00:17:09,760
it emphasizes

934
00:17:09,760 --> 00:17:10,440
the point,

935
00:17:10,780 --> 00:17:11,560
it emphasizes

936
00:17:11,560 --> 00:17:12,160
the point

937
00:17:12,160 --> 00:17:12,480
that a

938
00:17:12,480 --> 00:17:13,040
platform

939
00:17:13,040 --> 00:17:14,600
thinks like

940
00:17:14,600 --> 00:17:15,280
a developer,

941
00:17:15,720 --> 00:17:15,940
right?

942
00:17:15,980 --> 00:17:16,460
So you take

943
00:17:16,460 --> 00:17:16,740
on the

944
00:17:16,740 --> 00:17:17,320
developer's

945
00:17:17,320 --> 00:17:17,720
point of

946
00:17:17,720 --> 00:17:18,100
view and

947
00:17:18,100 --> 00:17:18,240
their

948
00:17:18,240 --> 00:17:18,660
perspective

949
00:17:18,660 --> 00:17:19,100
of what

950
00:17:19,100 --> 00:17:19,520
they,

951
00:17:20,280 --> 00:17:20,780
of course,

952
00:17:20,840 --> 00:17:21,060
what they

953
00:17:21,060 --> 00:17:21,380
would like

954
00:17:21,380 --> 00:17:21,740
to do,

955
00:17:21,920 --> 00:17:22,340
but what

956
00:17:22,340 --> 00:17:23,040
fits best

957
00:17:23,040 --> 00:17:23,360
to their

958
00:17:23,360 --> 00:17:23,880
skills.

959
00:17:24,520 --> 00:17:24,740
Yeah,

960
00:17:25,040 --> 00:17:26,020
what they

961
00:17:26,020 --> 00:17:26,320
would like

962
00:17:26,320 --> 00:17:26,620
to throw

963
00:17:26,620 --> 00:17:26,880
over the

964
00:17:26,880 --> 00:17:27,140
wall.

965
00:17:27,460 --> 00:17:27,760
Exactly,

966
00:17:27,980 --> 00:17:28,460
and that's

967
00:17:28,460 --> 00:17:29,060
where this

968
00:17:29,060 --> 00:17:29,500
disconnect

969
00:17:29,500 --> 00:17:29,880
of,

970
00:17:30,060 --> 00:17:30,140
like,

971
00:17:30,180 --> 00:17:30,460
if we

972
00:17:30,460 --> 00:17:30,860
just

973
00:17:30,860 --> 00:17:31,940
give

974
00:17:31,940 --> 00:17:32,840
the

975
00:17:32,840 --> 00:17:33,200
development

976
00:17:33,200 --> 00:17:33,900
organization

977
00:17:33,900 --> 00:17:34,880
cloud,

978
00:17:35,320 --> 00:17:36,600
and that

979
00:17:36,600 --> 00:17:37,040
cloud is

980
00:17:37,040 --> 00:17:37,720
infrastructure,

981
00:17:38,140 --> 00:17:39,440
we haven't

982
00:17:39,440 --> 00:17:40,020
given them

983
00:17:40,020 --> 00:17:40,460
enough,

984
00:17:40,700 --> 00:17:40,880
right?

985
00:17:40,880 --> 00:17:41,140
There's

986
00:17:41,140 --> 00:17:41,420
something

987
00:17:41,420 --> 00:17:41,760
missing,

988
00:17:41,820 --> 00:17:42,120
which is

989
00:17:42,120 --> 00:17:42,300
that

990
00:17:42,300 --> 00:17:42,820
platform,

991
00:17:42,820 --> 00:17:43,920
and it's

992
00:17:43,920 --> 00:17:46,360
always nice

993
00:17:46,360 --> 00:17:46,640
to talk

994
00:17:46,640 --> 00:17:46,820
about

995
00:17:46,820 --> 00:17:47,280
platforms

996
00:17:47,280 --> 00:17:47,460
and

997
00:17:47,460 --> 00:17:47,800
platform

998
00:17:47,800 --> 00:17:48,100
as a

999
00:17:48,100 --> 00:17:48,380
service

1000
00:17:48,380 --> 00:17:48,620
because

1001
00:17:48,620 --> 00:17:48,920
for

1002
00:17:48,920 --> 00:17:49,140
many

1003
00:17:49,140 --> 00:17:49,580
years

1004
00:17:49,580 --> 00:17:50,680
that

1005
00:17:50,680 --> 00:17:50,980
hasn't

1006
00:17:50,980 --> 00:17:51,120
been

1007
00:17:51,120 --> 00:17:51,280
the

1008
00:17:51,280 --> 00:17:51,640
discussion.

1009
00:17:51,640 --> 00:17:52,040
It's

1010
00:17:52,040 --> 00:17:52,480
all been

1011
00:17:52,480 --> 00:17:53,140
infrastructure

1012
00:17:53,140 --> 00:17:53,720
kind of

1013
00:17:53,720 --> 00:17:54,240
at this

1014
00:17:54,240 --> 00:17:54,760
Kubernetes

1015
00:17:54,760 --> 00:17:55,240
layer,

1016
00:17:55,360 --> 00:17:55,520
and I

1017
00:17:55,520 --> 00:17:55,700
think

1018
00:17:55,700 --> 00:17:56,420
now we've

1019
00:17:56,420 --> 00:17:56,760
kind of

1020
00:17:56,760 --> 00:17:57,500
finished

1021
00:17:57,500 --> 00:17:58,280
out the

1022
00:17:58,280 --> 00:17:58,800
infrastructure

1023
00:17:58,800 --> 00:17:59,220
layer,

1024
00:17:59,380 --> 00:18:00,540
and people

1025
00:18:00,540 --> 00:18:00,980
are hungry

1026
00:18:00,980 --> 00:18:01,360
for that

1027
00:18:01,360 --> 00:18:01,740
platform

1028
00:18:01,740 --> 00:18:02,160
stuff,

1029
00:18:02,220 --> 00:18:02,360
right?

1030
00:18:02,380 --> 00:18:02,640
They want

1031
00:18:02,640 --> 00:18:02,840
to see

1032
00:18:02,840 --> 00:18:03,160
those.

1033
00:18:03,160 --> 00:18:03,560
They're

1034
00:18:03,560 --> 00:18:03,980
building it

1035
00:18:03,980 --> 00:18:04,080
to

1036
00:18:04,080 --> 00:18:04,460
themselves,

1037
00:18:04,620 --> 00:18:04,800
right?

1038
00:18:04,840 --> 00:18:05,140
Without

1039
00:18:05,140 --> 00:18:05,540
knowing,

1040
00:18:05,800 --> 00:18:05,960
they're

1041
00:18:05,960 --> 00:18:06,360
building it

1042
00:18:06,360 --> 00:18:06,640
themselves.

1043
00:18:06,840 --> 00:18:08,520
Well,

1044
00:18:08,600 --> 00:18:10,720
next week

1045
00:18:10,720 --> 00:18:11,760
as we

1046
00:18:11,760 --> 00:18:12,420
record this,

1047
00:18:12,820 --> 00:18:13,260
we'll be

1048
00:18:13,260 --> 00:18:13,380
in

1049
00:18:13,380 --> 00:18:13,840
Barcelona

1050
00:18:13,840 --> 00:18:14,980
if

1051
00:18:14,980 --> 00:18:15,860
everything

1052
00:18:15,860 --> 00:18:16,320
goes well.

1053
00:18:16,400 --> 00:18:16,600
Hopefully

1054
00:18:16,600 --> 00:18:17,020
our planes

1055
00:18:17,020 --> 00:18:17,280
will get

1056
00:18:17,280 --> 00:18:17,560
there on

1057
00:18:17,560 --> 00:18:18,340
time and

1058
00:18:18,340 --> 00:18:18,740
we'll get

1059
00:18:18,740 --> 00:18:19,120
checked in.

1060
00:18:19,220 --> 00:18:19,800
But we'll

1061
00:18:19,800 --> 00:18:20,280
be in

1062
00:18:20,280 --> 00:18:20,740
Barcelona

1063
00:18:20,740 --> 00:18:22,360
at the

1064
00:18:22,360 --> 00:18:22,700
EU,

1065
00:18:22,800 --> 00:18:23,140
the Europe

1066
00:18:23,140 --> 00:18:23,580
version of

1067
00:18:23,580 --> 00:18:24,320
our big

1068
00:18:24,320 --> 00:18:24,880
conference

1069
00:18:24,880 --> 00:18:25,380
explorer.

1070
00:18:26,000 --> 00:18:26,180
And,

1071
00:18:26,260 --> 00:18:26,920
you know,

1072
00:18:27,400 --> 00:18:28,080
you'll be up

1073
00:18:28,080 --> 00:18:28,580
on stage.

1074
00:18:28,680 --> 00:18:29,180
What are we

1075
00:18:29,180 --> 00:18:29,420
going to be

1076
00:18:29,420 --> 00:18:29,860
talking about

1077
00:18:29,860 --> 00:18:29,980
there?

1078
00:18:30,060 --> 00:18:30,560
Give us

1079
00:18:30,560 --> 00:18:30,960
a sense,

1080
00:18:31,100 --> 00:18:31,300
a little

1081
00:18:31,300 --> 00:18:31,680
preview.

1082
00:18:32,560 --> 00:18:33,240
You know,

1083
00:18:33,380 --> 00:18:33,820
exciting.

1084
00:18:34,080 --> 00:18:34,220
So,

1085
00:18:34,460 --> 00:18:34,680
look,

1086
00:18:34,900 --> 00:18:35,780
we have

1087
00:18:35,780 --> 00:18:36,040
done,

1088
00:18:36,200 --> 00:18:36,520
as you

1089
00:18:36,520 --> 00:18:36,700
said,

1090
00:18:36,780 --> 00:18:37,500
Tanzu has

1091
00:18:37,500 --> 00:18:37,760
been in

1092
00:18:37,760 --> 00:18:37,860
the

1093
00:18:37,860 --> 00:18:38,140
platform

1094
00:18:38,140 --> 00:18:38,500
business,

1095
00:18:38,620 --> 00:18:38,880
especially

1096
00:18:38,880 --> 00:18:39,200
with the

1097
00:18:39,200 --> 00:18:39,620
Pivotal

1098
00:18:39,620 --> 00:18:40,220
legacy and

1099
00:18:40,220 --> 00:18:40,800
Cloud Foundry

1100
00:18:40,800 --> 00:18:41,720
legacy for

1101
00:18:41,720 --> 00:18:42,000
a long

1102
00:18:42,000 --> 00:18:42,280
time.

1103
00:18:42,900 --> 00:18:43,460
And we

1104
00:18:43,460 --> 00:18:43,760
have made

1105
00:18:43,760 --> 00:18:44,120
it very

1106
00:18:44,120 --> 00:18:44,620
easy for

1107
00:18:44,620 --> 00:18:45,040
developers

1108
00:18:45,040 --> 00:18:45,460
with Cloud

1109
00:18:45,460 --> 00:18:46,880
Foundry and

1110
00:18:46,880 --> 00:18:47,420
for container

1111
00:18:47,420 --> 00:18:48,060
based modern

1112
00:18:48,060 --> 00:18:48,660
application,

1113
00:18:49,220 --> 00:18:49,340
right?

1114
00:18:49,580 --> 00:18:49,980
12-factor

1115
00:18:49,980 --> 00:18:50,260
apps,

1116
00:18:50,380 --> 00:18:50,640
et cetera.

1117
00:18:51,200 --> 00:18:51,660
But what

1118
00:18:51,660 --> 00:18:51,980
has been

1119
00:18:51,980 --> 00:18:53,060
missing in

1120
00:18:53,060 --> 00:18:53,560
the industry

1121
00:18:53,560 --> 00:18:54,760
is that

1122
00:18:54,760 --> 00:18:55,620
same type

1123
00:18:55,620 --> 00:18:56,340
of seamless

1124
00:18:56,340 --> 00:18:56,820
developer

1125
00:18:56,820 --> 00:18:57,620
experience with

1126
00:18:57,620 --> 00:18:58,020
that build,

1127
00:18:58,120 --> 00:18:58,240
buy,

1128
00:18:58,280 --> 00:18:58,560
and deploy

1129
00:18:58,560 --> 00:19:00,300
update and

1130
00:19:00,300 --> 00:19:01,140
scale on

1131
00:19:01,140 --> 00:19:02,580
Kubernetes.

1132
00:19:03,180 --> 00:19:03,660
Kubernetes

1133
00:19:03,660 --> 00:19:04,340
has tended

1134
00:19:04,340 --> 00:19:06,020
to be this

1135
00:19:06,020 --> 00:19:06,720
alpha

1136
00:19:06,720 --> 00:19:07,360
bit soup of

1137
00:19:07,360 --> 00:19:07,580
little

1138
00:19:07,580 --> 00:19:08,400
projects that

1139
00:19:08,400 --> 00:19:08,960
go around

1140
00:19:08,960 --> 00:19:09,200
it,

1141
00:19:09,280 --> 00:19:09,660
a separate

1142
00:19:09,660 --> 00:19:10,120
networking

1143
00:19:10,120 --> 00:19:10,440
layer,

1144
00:19:10,560 --> 00:19:10,860
a separate

1145
00:19:10,860 --> 00:19:11,260
compute

1146
00:19:11,260 --> 00:19:11,580
layer.

1147
00:19:11,920 --> 00:19:12,240
Now I

1148
00:19:12,240 --> 00:19:12,740
stitch together

1149
00:19:12,740 --> 00:19:13,240
pipelines,

1150
00:19:13,360 --> 00:19:13,620
now I

1151
00:19:13,620 --> 00:19:14,060
stitch together

1152
00:19:14,060 --> 00:19:14,560
my build,

1153
00:19:14,720 --> 00:19:15,000
et cetera.

1154
00:19:15,780 --> 00:19:16,240
And so,

1155
00:19:16,740 --> 00:19:17,440
what we are

1156
00:19:17,440 --> 00:19:18,580
announcing is

1157
00:19:18,580 --> 00:19:18,920
Tanzu

1158
00:19:18,920 --> 00:19:19,660
Platform 10,

1159
00:19:20,200 --> 00:19:21,160
it gives you

1160
00:19:21,160 --> 00:19:21,600
three main

1161
00:19:21,600 --> 00:19:21,920
things.

1162
00:19:21,920 --> 00:19:23,220
One is it

1163
00:19:23,220 --> 00:19:24,040
extends that

1164
00:19:24,040 --> 00:19:24,460
simple

1165
00:19:24,460 --> 00:19:24,880
developer

1166
00:19:24,880 --> 00:19:25,520
experience

1167
00:19:25,520 --> 00:19:26,480
now,

1168
00:19:26,900 --> 00:19:27,360
not just

1169
00:19:27,360 --> 00:19:28,420
from Cloud

1170
00:19:28,420 --> 00:19:28,840
Foundry-like

1171
00:19:28,840 --> 00:19:29,140
developer

1172
00:19:29,140 --> 00:19:29,520
experience,

1173
00:19:29,640 --> 00:19:30,100
also to

1174
00:19:30,100 --> 00:19:30,480
Kubernetes.

1175
00:19:31,140 --> 00:19:31,580
So you

1176
00:19:31,580 --> 00:19:32,080
are not

1177
00:19:32,080 --> 00:19:32,880
building the

1178
00:19:32,880 --> 00:19:33,180
furniture

1179
00:19:33,180 --> 00:19:33,800
yourself with

1180
00:19:33,800 --> 00:19:34,080
your own

1181
00:19:34,080 --> 00:19:34,560
screwdrivers,

1182
00:19:34,620 --> 00:19:34,940
you actually

1183
00:19:34,940 --> 00:19:35,240
get the

1184
00:19:35,240 --> 00:19:35,680
whole desk

1185
00:19:35,680 --> 00:19:36,140
and the

1186
00:19:36,140 --> 00:19:36,580
chair and

1187
00:19:36,580 --> 00:19:36,940
so on,

1188
00:19:36,940 --> 00:19:37,100
right?

1189
00:19:37,440 --> 00:19:37,700
You are

1190
00:19:37,700 --> 00:19:37,960
getting

1191
00:19:37,960 --> 00:19:38,440
everything

1192
00:19:38,440 --> 00:19:39,040
you need.

1193
00:19:39,160 --> 00:19:39,580
The second

1194
00:19:39,580 --> 00:19:40,400
thing is,

1195
00:19:41,280 --> 00:19:41,540
look,

1196
00:19:41,600 --> 00:19:42,180
we are all

1197
00:19:42,180 --> 00:19:42,820
about helping

1198
00:19:42,820 --> 00:19:44,140
people build

1199
00:19:44,140 --> 00:19:44,700
apps and

1200
00:19:44,700 --> 00:19:45,100
build apps

1201
00:19:45,100 --> 00:19:45,500
faster.

1202
00:19:46,460 --> 00:19:46,860
Spring

1203
00:19:46,860 --> 00:19:48,500
continues to

1204
00:19:48,500 --> 00:19:49,280
amaze me

1205
00:19:49,280 --> 00:19:49,600
with the

1206
00:19:49,600 --> 00:19:50,000
power of

1207
00:19:50,000 --> 00:19:50,560
the community

1208
00:19:50,560 --> 00:19:51,640
and we

1209
00:19:51,640 --> 00:19:51,960
are doubling

1210
00:19:51,960 --> 00:19:52,520
down further

1211
00:19:52,520 --> 00:19:52,940
on Spring

1212
00:19:52,940 --> 00:19:53,260
but we

1213
00:19:53,260 --> 00:19:53,560
have also

1214
00:19:53,560 --> 00:19:54,100
enhanced

1215
00:19:54,100 --> 00:19:54,640
Spring

1216
00:19:54,640 --> 00:19:55,400
with some

1217
00:19:55,400 --> 00:19:55,780
powerful

1218
00:19:55,780 --> 00:19:56,300
libraries

1219
00:19:56,300 --> 00:19:56,960
that make

1220
00:19:56,960 --> 00:19:57,500
Spring

1221
00:19:57,500 --> 00:19:58,220
run faster

1222
00:19:58,220 --> 00:19:58,640
on our

1223
00:19:58,640 --> 00:19:59,080
platform,

1224
00:19:59,220 --> 00:19:59,360
make

1225
00:19:59,360 --> 00:19:59,580
run

1226
00:19:59,580 --> 00:19:59,920
Spring

1227
00:19:59,920 --> 00:20:00,740
more secure

1228
00:20:00,740 --> 00:20:01,160
with FIPS

1229
00:20:01,160 --> 00:20:01,680
compliance,

1230
00:20:02,000 --> 00:20:02,780
as well as

1231
00:20:02,780 --> 00:20:04,140
make it

1232
00:20:04,140 --> 00:20:05,340
easier for

1233
00:20:05,340 --> 00:20:06,500
Java developers

1234
00:20:06,500 --> 00:20:07,060
to write

1235
00:20:07,060 --> 00:20:08,360
AI ML

1236
00:20:08,360 --> 00:20:09,740
based

1237
00:20:09,740 --> 00:20:11,020
applications

1238
00:20:11,020 --> 00:20:11,560
on our

1239
00:20:11,560 --> 00:20:12,040
platform,

1240
00:20:12,560 --> 00:20:12,740
right?

1241
00:20:13,040 --> 00:20:14,100
And not

1242
00:20:14,100 --> 00:20:14,780
only easily

1243
00:20:14,780 --> 00:20:15,560
write applications

1244
00:20:15,560 --> 00:20:16,040
with Spring

1245
00:20:16,040 --> 00:20:16,280
AI,

1246
00:20:16,460 --> 00:20:17,520
but very

1247
00:20:17,520 --> 00:20:17,980
easily

1248
00:20:17,980 --> 00:20:18,920
deploy it

1249
00:20:18,920 --> 00:20:20,220
to these

1250
00:20:20,220 --> 00:20:20,880
cloud

1251
00:20:20,880 --> 00:20:21,480
environments

1252
00:20:21,480 --> 00:20:22,480
with the

1253
00:20:22,480 --> 00:20:23,080
right type

1254
00:20:23,080 --> 00:20:23,580
of Gen

1255
00:20:23,580 --> 00:20:24,540
AI broker,

1256
00:20:25,000 --> 00:20:25,200
right?

1257
00:20:25,260 --> 00:20:25,580
So what

1258
00:20:25,580 --> 00:20:25,960
you want

1259
00:20:25,960 --> 00:20:26,600
is as

1260
00:20:26,600 --> 00:20:26,760
you're

1261
00:20:26,760 --> 00:20:26,980
building

1262
00:20:26,980 --> 00:20:27,300
apps,

1263
00:20:27,340 --> 00:20:27,580
you may

1264
00:20:27,580 --> 00:20:28,000
be changing

1265
00:20:28,000 --> 00:20:29,260
models and

1266
00:20:29,260 --> 00:20:29,880
you don't

1267
00:20:29,880 --> 00:20:30,120
want to

1268
00:20:30,120 --> 00:20:30,460
change your

1269
00:20:30,460 --> 00:20:31,120
APIs and

1270
00:20:31,120 --> 00:20:31,700
your application

1271
00:20:31,700 --> 00:20:32,200
every time

1272
00:20:32,200 --> 00:20:32,520
you change

1273
00:20:32,520 --> 00:20:32,880
a model.

1274
00:20:33,260 --> 00:20:33,460
So we

1275
00:20:33,460 --> 00:20:33,960
have created

1276
00:20:33,960 --> 00:20:34,440
a simple

1277
00:20:34,440 --> 00:20:35,280
API surface

1278
00:20:35,280 --> 00:20:36,540
within what

1279
00:20:36,540 --> 00:20:36,960
I call

1280
00:20:36,960 --> 00:20:37,600
an AI

1281
00:20:37,600 --> 00:20:38,820
API broker

1282
00:20:38,820 --> 00:20:39,860
that then

1283
00:20:39,860 --> 00:20:40,320
takes it

1284
00:20:40,320 --> 00:20:40,800
and brokers

1285
00:20:40,800 --> 00:20:41,300
it to any

1286
00:20:41,300 --> 00:20:42,160
external models,

1287
00:20:42,360 --> 00:20:42,960
takes care of

1288
00:20:42,960 --> 00:20:43,360
governance,

1289
00:20:43,580 --> 00:20:44,180
takes care of

1290
00:20:44,180 --> 00:20:45,140
token management,

1291
00:20:45,280 --> 00:20:45,740
takes care of

1292
00:20:45,740 --> 00:20:46,200
security,

1293
00:20:46,460 --> 00:20:47,440
and really

1294
00:20:47,440 --> 00:20:48,780
the entire

1295
00:20:48,780 --> 00:20:49,640
build to

1296
00:20:49,640 --> 00:20:50,580
deploy of

1297
00:20:50,580 --> 00:20:51,880
applications

1298
00:20:51,880 --> 00:20:53,520
embedded with

1299
00:20:53,520 --> 00:20:54,280
Gen AI becomes

1300
00:20:54,280 --> 00:20:54,820
much easier.

1301
00:20:55,000 --> 00:20:55,460
So that's kind

1302
00:20:55,460 --> 00:20:56,220
of, so I would

1303
00:20:56,220 --> 00:20:56,620
say that those

1304
00:20:56,620 --> 00:20:57,180
are the three,

1305
00:20:57,640 --> 00:20:57,900
you know,

1306
00:20:58,360 --> 00:20:59,040
big extending

1307
00:20:59,040 --> 00:20:59,620
the power of

1308
00:20:59,620 --> 00:21:00,040
Kubernetes,

1309
00:21:00,380 --> 00:21:00,900
extending the

1310
00:21:00,900 --> 00:21:01,520
power of simple

1311
00:21:01,520 --> 00:21:02,380
developer experience

1312
00:21:02,380 --> 00:21:03,860
to Kubernetes

1313
00:21:03,860 --> 00:21:05,040
technologies and

1314
00:21:05,040 --> 00:21:05,540
making it

1315
00:21:05,540 --> 00:21:06,540
available seamlessly

1316
00:21:06,540 --> 00:21:07,060
by the way

1317
00:21:07,060 --> 00:21:08,360
on VCF,

1318
00:21:08,700 --> 00:21:08,860
right?

1319
00:21:08,960 --> 00:21:09,500
That is a big

1320
00:21:09,500 --> 00:21:10,240
one for

1321
00:21:10,240 --> 00:21:11,740
private cloud

1322
00:21:11,740 --> 00:21:12,220
environments,

1323
00:21:12,340 --> 00:21:12,680
air-gapped

1324
00:21:12,680 --> 00:21:13,120
environments.

1325
00:21:13,620 --> 00:21:14,180
Number two

1326
00:21:14,180 --> 00:21:15,600
is really

1327
00:21:15,600 --> 00:21:18,120
fuel charging,

1328
00:21:18,220 --> 00:21:18,460
right?

1329
00:21:18,860 --> 00:21:20,040
The spring

1330
00:21:20,040 --> 00:21:21,100
ecosystem with

1331
00:21:21,100 --> 00:21:22,140
even higher

1332
00:21:22,140 --> 00:21:22,860
performance and

1333
00:21:22,860 --> 00:21:23,860
higher security

1334
00:21:23,860 --> 00:21:25,080
capabilities as

1335
00:21:25,080 --> 00:21:25,620
it runs on the

1336
00:21:25,620 --> 00:21:26,060
platform.

1337
00:21:26,600 --> 00:21:26,800
And then

1338
00:21:26,800 --> 00:21:27,160
finally,

1339
00:21:27,920 --> 00:21:28,120
you know,

1340
00:21:28,180 --> 00:21:28,900
making Gen

1341
00:21:28,900 --> 00:21:29,740
AI accessible.

1342
00:21:30,340 --> 00:21:31,240
We talk a lot

1343
00:21:31,240 --> 00:21:32,020
about, you

1344
00:21:32,020 --> 00:21:32,240
know, the

1345
00:21:32,240 --> 00:21:32,840
nuts and bolts

1346
00:21:32,840 --> 00:21:33,440
of Gen AI

1347
00:21:33,440 --> 00:21:34,520
and the

1348
00:21:34,520 --> 00:21:35,240
picks and

1349
00:21:35,240 --> 00:21:35,760
shovels of

1350
00:21:35,760 --> 00:21:36,340
Gen AI as

1351
00:21:36,340 --> 00:21:36,960
they call it.

1352
00:21:37,600 --> 00:21:39,040
But, you

1353
00:21:39,040 --> 00:21:39,740
know, if I'm a

1354
00:21:39,740 --> 00:21:40,340
Java developer

1355
00:21:40,340 --> 00:21:41,020
and tomorrow I

1356
00:21:41,020 --> 00:21:41,640
just want to

1357
00:21:41,640 --> 00:21:42,900
enable, you

1358
00:21:42,900 --> 00:21:43,700
know, the

1359
00:21:43,700 --> 00:21:44,560
use case of

1360
00:21:44,560 --> 00:21:45,040
let us say a

1361
00:21:45,040 --> 00:21:45,620
chat interface

1362
00:21:45,620 --> 00:21:45,920
or a

1363
00:21:45,920 --> 00:21:46,520
summarization

1364
00:21:46,520 --> 00:21:47,300
use case or

1365
00:21:47,300 --> 00:21:48,120
a filtering

1366
00:21:48,120 --> 00:21:48,660
use case,

1367
00:21:48,900 --> 00:21:49,620
how can I do

1368
00:21:49,620 --> 00:21:50,320
that easy,

1369
00:21:50,920 --> 00:21:51,080
right?

1370
00:21:51,180 --> 00:21:52,120
While staying

1371
00:21:52,120 --> 00:21:52,700
within my

1372
00:21:52,700 --> 00:21:53,780
Java environment,

1373
00:21:53,940 --> 00:21:54,420
writing a

1374
00:21:54,420 --> 00:21:55,800
quick set of

1375
00:21:55,800 --> 00:21:56,240
APIs,

1376
00:21:56,480 --> 00:21:56,900
calling the

1377
00:21:56,900 --> 00:21:57,460
models that I

1378
00:21:57,460 --> 00:21:58,360
want and then

1379
00:21:58,360 --> 00:21:59,200
getting it deployed

1380
00:21:59,200 --> 00:22:00,220
with the safety

1381
00:22:00,220 --> 00:22:00,760
and security

1382
00:22:00,760 --> 00:22:01,080
of the

1383
00:22:01,080 --> 00:22:01,380
corporate

1384
00:22:01,380 --> 00:22:02,240
environment.

1385
00:22:02,740 --> 00:22:03,120
And that is

1386
00:22:03,120 --> 00:22:03,500
kind of the

1387
00:22:03,500 --> 00:22:03,900
third big

1388
00:22:03,900 --> 00:22:04,120
pillar.

1389
00:22:04,580 --> 00:22:05,320
So, a ton of

1390
00:22:05,320 --> 00:22:06,040
good stuff on

1391
00:22:06,040 --> 00:22:06,620
Tanzu Platform

1392
00:22:06,620 --> 00:22:06,960
10.

1393
00:22:07,520 --> 00:22:08,140
And then, you

1394
00:22:08,140 --> 00:22:09,240
know, no

1395
00:22:09,240 --> 00:22:10,120
application can

1396
00:22:10,120 --> 00:22:10,560
live without

1397
00:22:10,560 --> 00:22:10,940
data.

1398
00:22:11,580 --> 00:22:11,940
So, we

1399
00:22:11,940 --> 00:22:13,320
are also, we

1400
00:22:13,320 --> 00:22:13,820
have Tanzu

1401
00:22:13,820 --> 00:22:14,900
Data Suite and

1402
00:22:14,900 --> 00:22:16,120
we are announcing

1403
00:22:16,120 --> 00:22:16,940
enhancements to

1404
00:22:16,940 --> 00:22:18,200
Data Suite with

1405
00:22:18,200 --> 00:22:19,760
better, you

1406
00:22:19,760 --> 00:22:20,140
know, data

1407
00:22:20,140 --> 00:22:20,980
warehousing is

1408
00:22:20,980 --> 00:22:21,580
now back in

1409
00:22:21,580 --> 00:22:21,860
vogue.

1410
00:22:22,300 --> 00:22:23,180
So, Greenplum,

1411
00:22:23,620 --> 00:22:24,180
we are seeing

1412
00:22:24,180 --> 00:22:25,340
a resurgence of

1413
00:22:25,340 --> 00:22:25,900
our Greenplum

1414
00:22:25,900 --> 00:22:26,640
data warehousing

1415
00:22:26,640 --> 00:22:27,240
and analytics

1416
00:22:27,240 --> 00:22:27,740
solution.

1417
00:22:28,300 --> 00:22:28,680
We make it

1418
00:22:28,680 --> 00:22:29,320
available with

1419
00:22:29,320 --> 00:22:29,800
HA,

1420
00:22:30,100 --> 00:22:30,680
multi-data

1421
00:22:30,680 --> 00:22:30,940
center

1422
00:22:30,940 --> 00:22:31,480
replication.

1423
00:22:32,100 --> 00:22:32,320
We have

1424
00:22:32,320 --> 00:22:32,880
improved the

1425
00:22:32,880 --> 00:22:33,400
power of our

1426
00:22:33,400 --> 00:22:34,400
caching solutions

1427
00:22:34,400 --> 00:22:35,940
with 10x, the

1428
00:22:35,940 --> 00:22:37,160
power of speed

1429
00:22:37,160 --> 00:22:38,600
in terms of

1430
00:22:38,600 --> 00:22:39,220
read-write with

1431
00:22:39,220 --> 00:22:39,640
Gemfire.

1432
00:22:40,300 --> 00:22:41,320
And what we

1433
00:22:41,320 --> 00:22:42,140
also did is we

1434
00:22:42,140 --> 00:22:42,760
took some of

1435
00:22:42,760 --> 00:22:43,640
our core

1436
00:22:43,640 --> 00:22:44,800
open source

1437
00:22:44,800 --> 00:22:46,960
data solutions

1438
00:22:46,960 --> 00:22:49,340
like Postgres,

1439
00:22:49,660 --> 00:22:50,160
MySQL,

1440
00:22:50,580 --> 00:22:51,640
Valky, and

1441
00:22:51,640 --> 00:22:52,060
then we have

1442
00:22:52,060 --> 00:22:52,580
also added

1443
00:22:52,580 --> 00:22:53,200
RabbitMQ,

1444
00:22:53,320 --> 00:22:54,000
which we are

1445
00:22:54,000 --> 00:22:55,020
offering that as

1446
00:22:55,020 --> 00:22:55,420
a fully

1447
00:22:55,420 --> 00:22:56,060
supported

1448
00:22:56,060 --> 00:22:57,360
enterprise-grade

1449
00:22:57,360 --> 00:22:57,980
managed offering

1450
00:22:57,980 --> 00:22:58,500
on top of

1451
00:22:58,500 --> 00:22:59,040
BCF with

1452
00:22:59,040 --> 00:22:59,540
Tanzu data

1453
00:22:59,540 --> 00:23:00,020
services.

1454
00:23:00,740 --> 00:23:01,160
Now, the

1455
00:23:01,160 --> 00:23:01,620
Tanzu data

1456
00:23:01,620 --> 00:23:02,200
services are

1457
00:23:02,200 --> 00:23:03,460
included if

1458
00:23:03,460 --> 00:23:03,860
you buy the

1459
00:23:03,860 --> 00:23:04,400
platform or

1460
00:23:04,400 --> 00:23:05,000
the data suite,

1461
00:23:05,340 --> 00:23:05,960
but the nice

1462
00:23:05,960 --> 00:23:06,540
thing is if you

1463
00:23:06,540 --> 00:23:07,000
just want to

1464
00:23:07,000 --> 00:23:07,420
run it by

1465
00:23:07,420 --> 00:23:07,900
itself on

1466
00:23:07,900 --> 00:23:08,400
BCF, you

1467
00:23:08,400 --> 00:23:09,100
can also do

1468
00:23:09,100 --> 00:23:09,540
that now.

1469
00:23:09,540 --> 00:23:10,300
So I think

1470
00:23:10,300 --> 00:23:11,200
you went

1471
00:23:11,200 --> 00:23:11,960
through just

1472
00:23:11,960 --> 00:23:12,980
there two

1473
00:23:12,980 --> 00:23:13,940
great examples

1474
00:23:13,940 --> 00:23:16,080
of why

1475
00:23:16,080 --> 00:23:16,900
thinking about

1476
00:23:16,900 --> 00:23:17,880
a platform

1477
00:23:17,880 --> 00:23:18,800
is different

1478
00:23:18,800 --> 00:23:19,280
than thinking

1479
00:23:19,280 --> 00:23:19,960
about just

1480
00:23:19,960 --> 00:23:20,880
give them

1481
00:23:20,880 --> 00:23:21,960
cloud and

1482
00:23:21,960 --> 00:23:22,500
let them

1483
00:23:22,500 --> 00:23:23,040
sort it out,

1484
00:23:23,060 --> 00:23:23,220
right?

1485
00:23:23,280 --> 00:23:23,920
Like, you

1486
00:23:23,920 --> 00:23:24,980
know, there's,

1487
00:23:25,100 --> 00:23:25,880
you know, most

1488
00:23:25,880 --> 00:23:26,700
all applications

1489
00:23:26,700 --> 00:23:27,960
will have data

1490
00:23:27,960 --> 00:23:28,560
around it,

1491
00:23:28,600 --> 00:23:28,820
right?

1492
00:23:28,940 --> 00:23:31,020
And in

1493
00:23:31,020 --> 00:23:32,040
various different

1494
00:23:32,040 --> 00:23:33,160
ways and the

1495
00:23:33,160 --> 00:23:33,840
same benefit

1496
00:23:33,840 --> 00:23:34,720
you get from

1497
00:23:34,720 --> 00:23:35,640
managing

1498
00:23:35,640 --> 00:23:36,700
infrastructure for

1499
00:23:36,700 --> 00:23:37,380
people, for

1500
00:23:37,380 --> 00:23:38,020
developers, you

1501
00:23:38,020 --> 00:23:38,520
get from

1502
00:23:38,520 --> 00:23:39,700
managing the

1503
00:23:39,700 --> 00:23:40,180
data from

1504
00:23:40,180 --> 00:23:40,440
them and

1505
00:23:40,440 --> 00:23:40,900
making that

1506
00:23:40,900 --> 00:23:41,600
integrated and

1507
00:23:41,600 --> 00:23:42,060
part of the

1508
00:23:42,060 --> 00:23:42,380
platform.

1509
00:23:42,500 --> 00:23:43,200
And then I

1510
00:23:43,200 --> 00:23:43,640
think, you

1511
00:23:43,640 --> 00:23:44,760
know, before

1512
00:23:44,760 --> 00:23:45,240
that, right,

1513
00:23:45,300 --> 00:23:46,940
like, what's

1514
00:23:46,940 --> 00:23:47,660
interesting about

1515
00:23:47,660 --> 00:23:49,780
whatever you

1516
00:23:49,780 --> 00:23:50,120
want to call

1517
00:23:50,120 --> 00:23:50,500
it, I always

1518
00:23:50,500 --> 00:23:50,880
think of it

1519
00:23:50,880 --> 00:23:51,640
as enterprise

1520
00:23:51,640 --> 00:23:52,540
AI, but

1521
00:23:52,540 --> 00:23:54,100
using AI in

1522
00:23:54,100 --> 00:23:54,600
large

1523
00:23:54,600 --> 00:23:55,840
organizations is

1524
00:23:55,840 --> 00:23:57,660
a lot of

1525
00:23:57,660 --> 00:23:58,640
the, let's

1526
00:23:58,640 --> 00:23:59,240
say, lessons

1527
00:23:59,240 --> 00:23:59,560
that we

1528
00:23:59,560 --> 00:24:00,860
learned going

1529
00:24:00,860 --> 00:24:01,760
through kind

1530
00:24:01,760 --> 00:24:01,960
of the

1531
00:24:01,960 --> 00:24:02,860
Kubernetes era

1532
00:24:02,860 --> 00:24:04,220
of cloud are

1533
00:24:04,220 --> 00:24:04,980
pretty much the

1534
00:24:04,980 --> 00:24:05,780
same for AI.

1535
00:24:05,960 --> 00:24:06,360
Like you were

1536
00:24:06,360 --> 00:24:06,900
just saying, you

1537
00:24:06,900 --> 00:24:07,260
don't want to

1538
00:24:07,260 --> 00:24:08,500
just give

1539
00:24:08,500 --> 00:24:09,660
infrastructure or

1540
00:24:09,660 --> 00:24:10,780
just give AI

1541
00:24:10,780 --> 00:24:11,160
to the

1542
00:24:11,160 --> 00:24:12,080
developers, you

1543
00:24:12,080 --> 00:24:12,360
want to

1544
00:24:12,360 --> 00:24:13,060
appreciate their

1545
00:24:13,060 --> 00:24:13,580
point of view

1546
00:24:13,580 --> 00:24:14,180
and build a

1547
00:24:14,180 --> 00:24:14,920
platform around

1548
00:24:14,920 --> 00:24:15,260
it.

1549
00:24:15,640 --> 00:24:16,040
The platform

1550
00:24:16,040 --> 00:24:17,080
has to adapt,

1551
00:24:17,180 --> 00:24:17,720
right, to

1552
00:24:17,720 --> 00:24:18,340
these in

1553
00:24:18,340 --> 00:24:18,820
large use

1554
00:24:18,820 --> 00:24:20,080
cases and it

1555
00:24:20,080 --> 00:24:20,620
has to give

1556
00:24:20,620 --> 00:24:21,520
choice and

1557
00:24:21,520 --> 00:24:21,980
flexibility,

1558
00:24:22,180 --> 00:24:22,340
right?

1559
00:24:22,420 --> 00:24:23,400
So, again,

1560
00:24:23,900 --> 00:24:24,540
the always

1561
00:24:24,540 --> 00:24:25,520
operative word

1562
00:24:25,520 --> 00:24:26,080
is if the

1563
00:24:26,080 --> 00:24:26,980
platform is not

1564
00:24:26,980 --> 00:24:27,520
taking away

1565
00:24:27,520 --> 00:24:29,020
toil and it's

1566
00:24:29,020 --> 00:24:29,600
not taking away

1567
00:24:29,600 --> 00:24:30,100
the boring

1568
00:24:30,100 --> 00:24:31,220
parts, then

1569
00:24:31,220 --> 00:24:31,780
it's not doing

1570
00:24:31,780 --> 00:24:32,140
its job.

1571
00:24:32,360 --> 00:24:32,640
All right.

1572
00:24:32,680 --> 00:24:33,480
I think we've

1573
00:24:33,480 --> 00:24:33,860
got a good

1574
00:24:33,860 --> 00:24:35,260
notion of,

1575
00:24:35,380 --> 00:24:36,340
let's almost

1576
00:24:36,340 --> 00:24:37,020
call it thinking

1577
00:24:37,020 --> 00:24:37,880
beyond private

1578
00:24:37,880 --> 00:24:38,340
and public

1579
00:24:38,340 --> 00:24:39,420
cloud, right?

1580
00:24:39,500 --> 00:24:40,700
Like what we

1581
00:24:40,700 --> 00:24:41,280
care about and

1582
00:24:41,280 --> 00:24:41,680
I think what's

1583
00:24:41,680 --> 00:24:42,220
interesting for

1584
00:24:42,220 --> 00:24:43,240
developers is the

1585
00:24:43,240 --> 00:24:44,360
platform, right?

1586
00:24:44,360 --> 00:24:45,780
And one of the

1587
00:24:45,780 --> 00:24:46,340
aspects of the

1588
00:24:46,340 --> 00:24:46,980
platform that's

1589
00:24:46,980 --> 00:24:48,120
valuable is like

1590
00:24:48,120 --> 00:24:49,220
as a developer

1591
00:24:49,220 --> 00:24:50,000
and as the

1592
00:24:50,000 --> 00:24:50,520
people supporting

1593
00:24:50,520 --> 00:24:51,120
the developers,

1594
00:24:51,680 --> 00:24:52,400
you don't really

1595
00:24:52,400 --> 00:24:53,060
have to think too

1596
00:24:53,060 --> 00:24:53,560
much about the

1597
00:24:53,560 --> 00:24:54,060
infrastructure.

1598
00:24:54,580 --> 00:24:55,380
You can do

1599
00:24:55,380 --> 00:24:55,940
whatever works

1600
00:24:55,940 --> 00:24:56,460
out best for

1601
00:24:56,460 --> 00:24:57,120
you, right?

1602
00:24:57,240 --> 00:24:58,400
And, you

1603
00:24:58,400 --> 00:24:59,460
know, we went

1604
00:24:59,460 --> 00:25:00,040
over several of

1605
00:25:00,040 --> 00:25:00,680
the things of

1606
00:25:00,680 --> 00:25:01,460
why private cloud

1607
00:25:01,460 --> 00:25:02,000
is good, why

1608
00:25:02,000 --> 00:25:02,620
public cloud is

1609
00:25:02,620 --> 00:25:02,880
good.

1610
00:25:03,340 --> 00:25:03,680
And then I

1611
00:25:03,680 --> 00:25:04,720
think there's

1612
00:25:04,720 --> 00:25:05,500
finally that notion

1613
00:25:05,500 --> 00:25:05,940
that it'll be

1614
00:25:05,940 --> 00:25:07,200
fun to see

1615
00:25:07,200 --> 00:25:07,800
how it evolves

1616
00:25:07,800 --> 00:25:08,700
over the next

1617
00:25:08,700 --> 00:25:09,280
year or so

1618
00:25:09,280 --> 00:25:11,140
is what's the

1619
00:25:11,140 --> 00:25:11,880
return of this

1620
00:25:11,880 --> 00:25:12,640
platform notion

1621
00:25:12,640 --> 00:25:13,360
to the industry

1622
00:25:13,360 --> 00:25:14,180
and how are

1623
00:25:14,180 --> 00:25:17,120
people, not so

1624
00:25:17,120 --> 00:25:17,800
much relearning,

1625
00:25:17,920 --> 00:25:18,300
how are they

1626
00:25:18,300 --> 00:25:20,100
building on what

1627
00:25:20,100 --> 00:25:20,600
we've done in the

1628
00:25:20,600 --> 00:25:21,020
past with

1629
00:25:21,020 --> 00:25:21,480
platforms?

1630
00:25:21,980 --> 00:25:22,340
So that's

1631
00:25:22,340 --> 00:25:22,540
great.

1632
00:25:22,700 --> 00:25:23,280
Thanks for the

1633
00:25:23,280 --> 00:25:23,620
overview.

1634
00:25:25,100 --> 00:25:25,500
Thank you,

1635
00:25:25,620 --> 00:25:26,680
good to chat.

1636
00:25:27,100 --> 00:25:28,120
Yeah, I know

1637
00:25:28,120 --> 00:25:28,820
you're over there

1638
00:25:28,820 --> 00:25:29,360
in LinkedIn, I'll

1639
00:25:29,360 --> 00:25:29,820
put a link to

1640
00:25:29,820 --> 00:25:30,180
it, but of

1641
00:25:30,180 --> 00:25:30,840
course, for

1642
00:25:30,840 --> 00:25:31,460
both of us,

1643
00:25:31,560 --> 00:25:31,960
there's always

1644
00:25:31,960 --> 00:25:33,560
tonsu.vmware.com

1645
00:25:33,560 --> 00:25:34,100
where you can

1646
00:25:34,100 --> 00:25:34,900
dig deep into

1647
00:25:34,900 --> 00:25:35,300
everything.

1648
00:25:35,840 --> 00:25:36,040
All right,

1649
00:25:36,080 --> 00:25:36,440
well, this has

1650
00:25:36,440 --> 00:25:36,760
been another

1651
00:25:36,760 --> 00:25:37,400
tonsu talk.

1652
00:25:37,520 --> 00:25:37,860
You can find

1653
00:25:37,860 --> 00:25:38,300
the show notes

1654
00:25:38,300 --> 00:25:38,720
for this by

1655
00:25:38,720 --> 00:25:39,020
going to

1656
00:25:39,020 --> 00:25:40,000
tonsutalk.com

1657
00:25:40,000 --> 00:25:42,080
and hopefully

1658
00:25:42,080 --> 00:25:42,700
we'll see some

1659
00:25:42,700 --> 00:25:43,200
of our listeners

1660
00:25:43,200 --> 00:25:43,880
in Barcelona.

1661
00:25:44,160 --> 00:25:44,580
That'll be fun.

1662
00:25:44,640 --> 00:25:44,940
We'll have to

1663
00:25:44,940 --> 00:25:45,640
report back on

1664
00:25:45,640 --> 00:25:45,920
that.

1665
00:25:46,280 --> 00:25:46,560
We'll see

1666
00:25:46,560 --> 00:25:47,020
everyone next

1667
00:25:47,020 --> 00:25:47,340
time.

1668
00:25:47,600 --> 00:25:48,060
Bye-bye.

1669
00:25:48,880 --> 00:25:49,260
Bye-bye.