1
00:00:00,000 --> 00:00:03,140
Hey there. I wanted to tell you about a new podcast we got going over here at Pivotal.

2
00:00:03,260 --> 00:00:06,900
It's called That Moment. Don't get confused like I was initially. It's not the moment.

3
00:00:07,160 --> 00:00:10,280
It's called That Moment. That Moment explores the pivot that changes everything,

4
00:00:10,580 --> 00:00:14,780
moments that open doors for discovery and growth, but also brings the looming possibility of

5
00:00:14,780 --> 00:00:18,720
failure. Each show features different leaders and innovators sharing their stories and taking

6
00:00:18,720 --> 00:00:23,640
risks in business life. It's, you know, classic Pivotal stories. Also, it's fancy with all the

7
00:00:23,640 --> 00:00:27,840
crossfading music and optimized editing. It's really some good pro stuff. So if you're interested

8
00:00:27,840 --> 00:00:31,980
in those kinds of stories about how people are wangling their way through all this digital

9
00:00:31,980 --> 00:00:36,240
transformation, DevOps cloud native stuff, go subscribe to That Moment wherever you get your

10
00:00:36,240 --> 00:00:40,680
podcast. But, you know, for your weekly dose of unprofessional old school podcast rambling,

11
00:00:40,980 --> 00:00:46,060
let's get on with the show. You know, as time goes on, Richard, I'm finding it harder and harder to

12
00:00:46,060 --> 00:00:52,020
find about useful, funny things to just start to ask you about at the beginning. Sometimes I just give

13
00:00:52,020 --> 00:00:57,580
up and I just totally tank it. I had a great thing in mind and I almost wrote it down here.

14
00:00:57,680 --> 00:01:02,460
But I totally have forgotten what it is. But I want to ask you and, and, and guest, you can chime in as

15
00:01:02,460 --> 00:01:07,680
well. This morning, I want to, I want to, I want to get some consulting because you do a lot with,

16
00:01:07,780 --> 00:01:14,100
you read the internet and link to it. So I've been trying this maybe yearlong experiment that I should

17
00:01:14,100 --> 00:01:19,780
use my blog. You remember blogs? Those are fun, right? So I have my blog over at Coté.io because

18
00:01:19,780 --> 00:01:25,940
I'm trying to be cool. And every now and then over the past year, I'll try to like put all of my links

19
00:01:25,940 --> 00:01:30,960
on there with a little excerpt and then maybe put that in Twitter. Now I've been studying the traffic

20
00:01:30,960 --> 00:01:37,140
at my blog and it's like, it's like a red letter day if I get like 180 views and those aren't even

21
00:01:37,140 --> 00:01:42,740
unique. Those are probably just me checking on it. That's me hitting refresh. Yeah. And so this

22
00:01:42,740 --> 00:01:48,540
morning I thought this weekend, I've been thinking like, I've been, I've been, uh, uh, observing again

23
00:01:48,540 --> 00:01:52,680
for quite some time how like James Watters uses Twitter, right? Cause he's one of these people

24
00:01:52,680 --> 00:01:57,580
where I'm like, he has a lot of followers. What's going on there. Right. And not that he

25
00:01:57,580 --> 00:02:00,560
shouldn't, I'm just trying to study. And then you got, uh, you got that New York times reporter,

26
00:02:00,680 --> 00:02:07,120
Maggie, Maggie Haberman, Haberman, whoever. And, uh, and she seems to be a big deal. Right. And,

27
00:02:07,220 --> 00:02:11,400
and then you got monk chips, James governor, who we'll talk about in a little bit. And I think the

28
00:02:11,400 --> 00:02:16,900
thing they all do is they basically just dump any link they're interested in, into Twitter. And in

29
00:02:16,900 --> 00:02:21,480
addition to being, you know, sort of like, you know, famous, you got that interesting. So my new

30
00:02:21,480 --> 00:02:27,040
theory is just like, clearly I've done a, uh, I wouldn't call it a lean startup. Let's call it a fat

31
00:02:27,040 --> 00:02:33,820
startup model on, on my blog usage, a, a medium batch process. The blog is just ridiculous. You don't

32
00:02:33,820 --> 00:02:38,520
want to waste time on that. Right. So, so this is, this is what I need some consulting on is I've

33
00:02:38,520 --> 00:02:43,020
decided I'm just going to start putting links just directly into Twitter. You think that's going to

34
00:02:43,020 --> 00:02:47,920
work out for me? I mean, I used to, I mean, I still, I've been blogging since mid two thousands.

35
00:02:47,920 --> 00:02:52,440
I still at least blog once a month, but I don't do the link farm stuff anymore. I used to kind of do

36
00:02:52,440 --> 00:02:55,460
that. Like, Hey, here's interesting stuff. And now I don't need to do that anymore. That's what

37
00:02:55,460 --> 00:02:59,660
Twitter's for. So I use it for long form and I'm sure you too, right. You're not going to do,

38
00:02:59,880 --> 00:03:03,740
please don't, don't tweet storm the Coté takes. Like I really don't want to read the

39
00:03:03,740 --> 00:03:09,180
slash 15 all of your opinions. That's horrible. So yeah, I think using it for straight up links

40
00:03:09,180 --> 00:03:12,660
is probably the right call. And I've also learned that people suggest that when you do include

41
00:03:12,660 --> 00:03:17,120
images in your tweets, you get significantly more engagement. And I've anecdotally seen that to be

42
00:03:17,120 --> 00:03:21,360
true. Now, you know, the topic we're going to get to is like, like, uh, some more enterprise

43
00:03:21,360 --> 00:03:26,980
architecture talk. The next logical thing, if you were, if, if, you know, in consulting would be

44
00:03:26,980 --> 00:03:30,280
like, well, what is your goal? I don't know what my goal is. Right. You know what, you know what I

45
00:03:30,280 --> 00:03:33,620
think my goal is Richard? I just want to have a lot of followers. Cause it makes me feel good.

46
00:03:33,720 --> 00:03:40,200
That's all. Hey, admit it. That's right. And I, I think, I think maybe by my birthday,

47
00:03:40,200 --> 00:03:44,880
uh, you know, this little security risk on the 1st of January, I might finally reach 10,000

48
00:03:44,880 --> 00:03:49,060
followers. I don't know. I don't know. We'll see. I'm at like, not that I'm counting, but I'm at

49
00:03:49,060 --> 00:03:58,080
9,918 or so today. So that's a good shape there. Yeah. Yeah. 10 years ago, I had a fairly popular

50
00:03:58,080 --> 00:04:06,160
blog. It wasn't that popular, I guess it was 2006 era. And it amazed me how much influence you could

51
00:04:06,160 --> 00:04:11,780
get with, I guess back then there weren't that many tech blogs or something, but I, I think it just

52
00:04:11,780 --> 00:04:17,000
amazed me that you could, uh, I mean, I got invited to conferences, I got job interviews, you know,

53
00:04:17,000 --> 00:04:24,600
cause I was part of the rest community, which was a bit of a posse that we formed 2004 ish to, uh,

54
00:04:24,600 --> 00:04:32,540
to fight against the, the web services death star. And, uh, you know, it was all blog people. And I

55
00:04:32,540 --> 00:04:37,860
think, you know, eventually you make the arguments and you, and you get tired of it. And now all I get

56
00:04:37,860 --> 00:04:41,940
is complaints on Twitter that my blog's down cause they, they're referencing things over 10 years ago.

57
00:04:43,280 --> 00:04:48,660
Uh, man, you know, I am exactly the same way I got, I got my, uh, well, I got a bunch of minor breaks

58
00:04:48,660 --> 00:04:54,680
when I was still a programmer via my blog. And then I got my big break to be, uh, uh, a red monk,

59
00:04:54,920 --> 00:04:59,860
the first red monk employee, like because of my blog and my pod, my podcast to a limited extent,

60
00:04:59,880 --> 00:05:04,820
but I think that's why I've held onto it so long. It's just this fantasy, this fantasy of like the blog.

61
00:05:05,020 --> 00:05:09,940
You remember, anyways, it's a fantasy that I mean, my career, I think came from my blog as well. So

62
00:05:09,940 --> 00:05:14,480
I mean, I think the takeaway is it, we should all transport back to 2006 and start blogs. If you

63
00:05:14,480 --> 00:05:18,700
don't have one, that would be nice. Then, then, then instead of talking about enterprise architecture

64
00:05:18,700 --> 00:05:25,080
with our guests, we could talk about, uh, registries, UDDI, and, uh, maybe one of the

65
00:05:25,080 --> 00:05:30,680
preferred ways for automotive, uh, automotive. Well, I guess it would be for, uh, train maintenance

66
00:05:30,680 --> 00:05:35,300
people to send, uh, messages back and forth about the kind of wheels and trucks and that

67
00:05:35,300 --> 00:05:41,280
they needed in, uh, some of what they were in Ontario, but, uh, we won't be talking about

68
00:05:41,280 --> 00:05:48,780
you. Is it UUDI or UDDI? UDDI. UDDI. Yeah. I told people to avoid it then. I would say avoid

69
00:05:48,780 --> 00:05:53,660
it now. No, it's coming back. Well, speaking of what, why don't you introduce yourself guest?

70
00:05:55,040 --> 00:06:00,640
Hello. Um, my name is Stuart Charlton. I am an advisory platform architect at

71
00:06:00,640 --> 00:06:08,120
Pivotal. I live in sunny Calgary, Canada, and, uh, I have been, uh, doing various forms

72
00:06:08,120 --> 00:06:13,140
of cloud and enterprise architecture and development for about 20 years.

73
00:06:13,560 --> 00:06:17,980
Mm. You see, that's a long span. It's going to make Richard and I feel comfortable. We got

74
00:06:17,980 --> 00:06:25,960
a fellow old with us. We'll talk about learning how to program, you know, in Pascal or something

75
00:06:25,960 --> 00:06:30,400
like that. That's what I learned in college. Yeah. Pascal. Yeah. First year Waterloo.

76
00:06:30,600 --> 00:06:35,080
Good old Pascal. Uh, well, we've got, as always, we've got a little bit of news and then, uh,

77
00:06:35,080 --> 00:06:39,720
we're going to talk, uh, some more EA stuff. So, uh, you know, I was excited. I forgot about

78
00:06:39,720 --> 00:06:44,340
this until I looked at your show notes. That's how effervescent my brain is sometimes speaking

79
00:06:44,340 --> 00:06:48,460
of putting links on Twitter, but it's actually very exciting because I've talked about the

80
00:06:48,460 --> 00:06:52,760
rack space, uh, managed service thing with pivotal cloud foundry. And every time I talk

81
00:06:52,760 --> 00:06:55,860
about this stuff, I'm always a little worried being a pivotal employee that I'm going to get

82
00:06:55,860 --> 00:07:00,820
it wrong that I don't have the official propaganda, but now wouldn't it be handy if we had like

83
00:07:00,820 --> 00:07:06,980
the head of pivotal product marketing to come explain it to us? Take it away, Richard.

84
00:07:07,860 --> 00:07:11,820
Yeah, it was a good thing last week. They had their, uh, rack space had this event that,

85
00:07:11,820 --> 00:07:16,540
uh, our own Ian Andrews was on stage and we did some press and talked about announcing a

86
00:07:16,540 --> 00:07:20,680
managed service for pivotal cloud foundry by rack space and rack space, you know, even before

87
00:07:20,680 --> 00:07:25,880
they got into the cloudy stuff, uh, I don't know, eight, 10 years ago, started offering

88
00:07:25,880 --> 00:07:30,180
IAS sort of capabilities. They offered managed hosting, they offered sort of managed services.

89
00:07:30,180 --> 00:07:33,960
And, you know, after the IAS thing kind of petered out for most everybody, but the big

90
00:07:33,960 --> 00:07:37,960
three, I think it seems like rack space really did a nice correction saying, look, we're going

91
00:07:37,960 --> 00:07:42,660
to also manage AWS. We're going to measure, manage Azure. And so they also just announced

92
00:07:42,660 --> 00:07:49,160
they're going to manage GCP, but this PCF on, on any of those clouds is pretty exciting

93
00:07:49,160 --> 00:07:53,320
stuff. So the ability to say, look, we're going to manage PCF, not just in public cloud,

94
00:07:53,320 --> 00:07:56,380
but you can even run it in your data center and rack space will manage it for you. So

95
00:07:56,380 --> 00:08:01,260
it's a really cool offering. Now at the same time, what's always weird, Coté, you probably

96
00:08:01,260 --> 00:08:05,400
know this too, is we, you know, we talk about, look, I can run these giant PCF environments

97
00:08:05,400 --> 00:08:10,300
with five people. And so your thought is, gosh, why do I need to use a managed service? I only

98
00:08:10,300 --> 00:08:13,980
need like five folks to do this thing. Is it really that hard? And I think the answer

99
00:08:13,980 --> 00:08:16,940
is it's not that hard. It always comes down to where do you want to put your investment?

100
00:08:17,380 --> 00:08:20,360
And you still may say, look, we don't want to deal with upgrades. We don't want to,

101
00:08:20,820 --> 00:08:24,800
you know, even put those five people on it or 10 people or whatever. We'd rather have

102
00:08:24,800 --> 00:08:28,960
them embedded in teams. And so I think this is a good story for folks who like the idea

103
00:08:28,960 --> 00:08:33,240
of truly running platform as a service and have someone else taking care of all of it.

104
00:08:33,720 --> 00:08:37,200
You know, and at the same time, then you just get to do all your fun DevOps stuff down to

105
00:08:37,200 --> 00:08:37,980
the platform layer.

106
00:08:38,480 --> 00:08:43,020
Yeah. Instead of, uh, instead of like, uh, four to 10 people to manage your entire, uh,

107
00:08:43,020 --> 00:08:48,640
platform, you could have zero, just have, uh, have Johnson over in finance, send the invoice

108
00:08:48,640 --> 00:08:50,440
and then, then you're fine.

109
00:08:50,440 --> 00:08:51,620
So easy.

110
00:08:53,220 --> 00:08:54,140
Anybody could do it.

111
00:08:54,400 --> 00:08:58,480
Yeah. And then, and then there was another, uh, another, there was a double piece speak,

112
00:08:58,580 --> 00:09:02,680
uh, as I mentioned, speaking of, of, of our red monk buddies, I think, uh, I think, I think

113
00:09:02,680 --> 00:09:07,940
that in the, in this, in this, uh, pair up, you saw the, uh, the, uh, what would you call

114
00:09:07,940 --> 00:09:11,520
it? The classic, I don't know if there's a good version of a hydra. Have you ever noticed

115
00:09:11,520 --> 00:09:16,680
if you have multiple heads, you're always a monster, but it was a good, uh, um, uh, uh,

116
00:09:17,140 --> 00:09:22,220
multi-faceted. There you go. Even, see, even Janice is bad, right? Anyways, you, you

117
00:09:22,220 --> 00:09:22,720
saw Steve.

118
00:09:22,720 --> 00:09:23,580
Cerberus is good, isn't it?

119
00:09:23,740 --> 00:09:30,720
Yes. I mean, Cerberus is, is cool, but yeah. Anyways, let, let's call it, let's call it a

120
00:09:30,720 --> 00:09:36,680
friendly Cerberus, Cerberus, right? And that's, uh, there we go. Uh, yeah. Anyways, if, if

121
00:09:36,680 --> 00:09:44,200
listeners know of a positive two-headed creature, please send it to us. Yeah. Fluffy. Exactly.

122
00:09:44,400 --> 00:09:48,620
Fluffy from Harry Potter, right? Exactly. He was bad. Wasn't that, it was a bad guy, kind

123
00:09:48,620 --> 00:09:55,880
of. Yeah. Yeah. Yeah. Anyways, so you saw both, uh, Stephen O'Grady and James Governor

124
00:09:55,880 --> 00:10:01,620
writing the age old question, what's up with microservices and isn't it just SOA? And I

125
00:10:01,620 --> 00:10:05,900
think, I think, uh, what you saw from Stephen O'Grady there was good. It was, it was, uh, I

126
00:10:05,900 --> 00:10:09,780
summarized it kind of snarkily in a tweet that like, well, the developers didn't like

127
00:10:09,780 --> 00:10:15,820
it, which I think is a point that he made. Well, speaking of UDDI and, uh, also he had,

128
00:10:15,880 --> 00:10:20,240
uh, I mean, this is kind of a, um, I kind of first saw Red Monk doing this trick and other

129
00:10:20,240 --> 00:10:23,680
people do it. And by trick, I don't mean to belittle it, but you know, just charting the

130
00:10:23,680 --> 00:10:28,300
interest in Google trends of SOA versus microservices. And, and there's also some sort

131
00:10:28,300 --> 00:10:33,040
of scatterplot things on there to add extra science to it. Um, kind of like, you know,

132
00:10:33,040 --> 00:10:37,780
sprinkles on a cupcake. Uh, but like, yeah, it was, and then, and then, uh, I think, I

133
00:10:37,780 --> 00:10:42,460
think James Governor gave his sort of like, uh, qualitative history of SOA and all of that

134
00:10:42,460 --> 00:10:47,200
stuff happening, but it was, it was one of the better. Isn't this just SOA write-ups, uh,

135
00:10:47,200 --> 00:10:51,160
that's out there that kind of explain some of the dynamics. And, you know, I also, I'm

136
00:10:51,160 --> 00:10:55,660
always curious with things like this to go back and look at, um, uh, what, what the market

137
00:10:55,660 --> 00:11:01,360
size for stuff is. And, and I was very lazy. I didn't actually log into Gartner to look up

138
00:11:01,360 --> 00:11:06,600
recent numbers, but you can find some old things that basically the SOA space around 2011 or so

139
00:11:06,600 --> 00:11:14,280
was like 19 or $20 billion in, in revenue, which is, uh, that's a sizable chunk of, of

140
00:11:14,280 --> 00:11:18,840
spend in it that, uh, I don't know. It'd be interesting to see what it is nowadays, but,

141
00:11:18,920 --> 00:11:23,940
but it definitely has waned in at least developer popularity. Sure. At least, I mean,

142
00:11:23,960 --> 00:11:28,740
at least a third of that was revenue from my book about SOA patterns. So that's most of

143
00:11:28,740 --> 00:11:33,420
that billion went, uh, these were really good pieces. I mean, it Stevens was good cause it

144
00:11:33,420 --> 00:11:38,500
looked at like, look, I mean, web microservices seem to have staying power because developers

145
00:11:38,500 --> 00:11:41,860
are, you know, it's more grassroots. Like this makes sense to how we should be building

146
00:11:41,860 --> 00:11:48,500
software. It's not this sort of consortium based WS star mayhem of what SOA became. But

147
00:11:48,500 --> 00:11:51,980
then I liked James's piece because at the same time, we always have revisionist history.

148
00:11:52,460 --> 00:11:55,420
I think sometimes when we think about things like this and James looked back and said, what

149
00:11:55,420 --> 00:11:59,960
was life like in that mid two thousands where we weren't doing test driven development that

150
00:11:59,960 --> 00:12:03,400
same way we weren't doing CI, you know, we didn't have containers, we didn't have public

151
00:12:03,400 --> 00:12:08,100
cloud. And so the world was different. You wouldn't have maybe done microservices 10, 12

152
00:12:08,100 --> 00:12:12,160
years ago. It just, you know, SOA was a start of saying that we shouldn't have big monolithic

153
00:12:12,160 --> 00:12:16,620
systems. We should have decomposed set of services, but some of the other things weren't

154
00:12:16,620 --> 00:12:18,580
as mature yet. I think it's important to remember that.

155
00:12:19,180 --> 00:12:19,200
Yeah.

156
00:12:19,300 --> 00:12:25,380
I think the biggest barrier I saw was we did all this work to decompose systems, but then

157
00:12:25,380 --> 00:12:30,220
we couldn't deploy them. And so we had, we wound up with the same monoliths that we were

158
00:12:30,220 --> 00:12:34,880
trying to get rid of. And therefore cloud came out, which was really just dogfooding SOA

159
00:12:34,880 --> 00:12:40,140
for it. It was like, okay, so we can't actually deploy this stuff. All right, let's pause and

160
00:12:40,140 --> 00:12:46,680
SOA our world of computers and disks and stuff. And then maybe we'll be able to SOA the business.

161
00:12:46,780 --> 00:12:48,140
How about that? Let's just wait 10 years.

162
00:12:48,900 --> 00:12:52,540
No, it's a great point. I mean, that was before we were really thinking of continuous deployment,

163
00:12:52,700 --> 00:12:56,440
DevOps teams and actually pushing it all the way through. So that was good. You know, the other

164
00:12:56,700 --> 00:13:01,740
quick bring up related to that, Coté, your point earlier about your blog, Governor, James

165
00:13:01,740 --> 00:13:07,480
Governor started writing every single day. And, you know, it just reminds you that as much as we all love

166
00:13:07,480 --> 00:13:11,720
hot takes on Twitter and kind of quick briefings and things, there's nothing more viral and interesting

167
00:13:11,720 --> 00:13:15,760
than long form thought. And I think that Red Monk's actually gotten a higher profile these last few

168
00:13:15,760 --> 00:13:20,440
months because they've put more content out there that people consume, not just quick takes. So I

169
00:13:20,440 --> 00:13:24,120
think it's a good reminder. We should be writing things down, not just always talking about it.

170
00:13:24,120 --> 00:13:27,700
Yeah. Yeah. So let's continue talking about it in the podcast, but

171
00:13:27,700 --> 00:13:28,200
Absolutely.

172
00:13:28,640 --> 00:13:36,740
No, you're right. I've appreciated the turning on the blogging there. That's good stuff. It reminds me of

173
00:13:36,740 --> 00:13:43,900
the old days of Red Monk stuff. We used to, I remember we used to go to, I'll give you a little

174
00:13:43,900 --> 00:13:49,160
anecdote, Grandpa Coté here. I remember the first few months I was working at Red Monk. I was trying

175
00:13:49,160 --> 00:13:54,260
to figure out what to, you know, how to blog and what to do. And of all things, I went to a BEA

176
00:13:54,260 --> 00:13:59,280
conference. Now, two things, one distraction. The badges they had, this is when they had, you remember

177
00:13:59,280 --> 00:14:04,900
their, I bet both of you remember this, they had their liquid architecture or something. There's

178
00:14:04,900 --> 00:14:09,140
something about it. Yeah, there you go. So the badges they had, they were one of these, it was

179
00:14:09,140 --> 00:14:13,100
like a normal badge, but they had one of those little pockets with like that blue, squishy,

180
00:14:13,260 --> 00:14:18,920
oily water stuff. Right. I was at that conference. Oh yeah. At the, uh, the palace. Now a starwood

181
00:14:18,920 --> 00:14:24,140
joint. Oh yeah, man. That was, that was fun stuff. But I remember I kept that badge for way too

182
00:14:24,140 --> 00:14:29,480
long. Cause I was like, this is pretty awesome. But I still have my thick liquid mug. Oh man,

183
00:14:29,520 --> 00:14:33,640
you'll have to send us a picture of that. That's, that's good stuff. But, uh, I remember I had

184
00:14:33,640 --> 00:14:39,020
written some like raw notes from that and I posted that as a blog entry. Cause you know, to my mind,

185
00:14:39,020 --> 00:14:43,260
it'd be like, I just want to see everything that someone like me does. But, but James Wright was like,

186
00:14:43,260 --> 00:14:52,120
you know, you might try to string those into sentences. So so also, also, you know, I, I, um,

187
00:14:52,820 --> 00:14:57,220
I guess it's not coincidental because Kubernetes stuff comes up all the time, but there was, there's,

188
00:14:57,300 --> 00:15:02,140
there's a rumor that finally the last holdout for sort of like official Kubernetes stuff,

189
00:15:02,140 --> 00:15:07,120
or is it, or, is there a rumor or report report is just a fancy word for rumor. Is that the same

190
00:15:07,120 --> 00:15:12,480
number of characters in it? But it was saying that, uh, AWS might have some, uh, Kubernetes stuff built

191
00:15:12,480 --> 00:15:19,180
into it. Yeah. I mean, you know, there's a slow march to people adopting that at least as a container

192
00:15:19,180 --> 00:15:24,400
plumbing component, which I think our belief, even with pivotal and doing Kubo is this is great

193
00:15:24,400 --> 00:15:28,180
technology that should underpin a platform. It shouldn't be something you necessarily have to

194
00:15:28,180 --> 00:15:32,280
mess with all the time or you're probably not spending the right time, but yeah, I mean, Amazon

195
00:15:32,280 --> 00:15:36,260
may be playing with this. They've been the holdout, you know, I think to some extent, cause folks see

196
00:15:36,260 --> 00:15:41,060
Kubernetes is a great way for all the workloads to move to Google at some point. And if I'm Amazon,

197
00:15:41,060 --> 00:15:45,640
that doesn't sound like a great idea, but at the same time, you know, arguably no one's better in

198
00:15:45,640 --> 00:15:49,500
cloud at giving the customers what they want or even the things they didn't realize they wanted

199
00:15:49,500 --> 00:15:54,300
than Amazon. So if they see the groundswell for it, then they'd be dumb not to do something there.

200
00:15:54,700 --> 00:15:58,760
And, and I'll, I'll put a link to these two in the show notes, but there's also a good, uh,

201
00:15:58,760 --> 00:16:02,560
sort of historic thing. You know, I think it's something like two years of Kubernetes being

202
00:16:02,560 --> 00:16:06,300
independent. And then, you know, I need to go reread this again, but because it looks like it was

203
00:16:06,300 --> 00:16:10,680
like sort of an interview with a, an interested party. There was, there was a fun little write

204
00:16:10,680 --> 00:16:15,440
up in the register talking about how, uh, you know, you could use Kubernetes to like run middleware

205
00:16:15,440 --> 00:16:20,500
and do all these platformy things, which, which that, that sounds, that sounds like a good idea.

206
00:16:20,880 --> 00:16:26,360
People, people should have a platform, but, uh, anyhow. Uh, and then, uh, there was also last

207
00:16:26,360 --> 00:16:30,780
week was Microsoft's, uh, announcement. What they're at like, uh, what is it about a, about

208
00:16:30,780 --> 00:16:35,800
a $19 billion run rate. What's a hundred million dollars between quarters, right?

209
00:16:35,940 --> 00:16:41,000
That's right. Yeah. Now the cloud business is going nuts over there. And so, I mean, obviously

210
00:16:41,000 --> 00:16:45,120
it buries the lead on some other stuff like windows stuff is just kind of okay. And obviously

211
00:16:45,120 --> 00:16:50,060
things like windows phone have cratered completely, but you know, and being ads are up a little bit,

212
00:16:50,120 --> 00:16:54,380
but I mean, cloud is the top line thing and clouds generating a ton of money. So that's,

213
00:16:54,380 --> 00:16:58,780
that's good news for, I think the market, because you always want to get, not have a monopolistic

214
00:16:58,780 --> 00:17:03,600
single provider for your cloud stuff. If you're not betting on Microsoft or putting them in your

215
00:17:03,600 --> 00:17:07,600
RFPs, you're probably doing yourself a disservice. So, so give me, give me a little, and, and,

216
00:17:07,680 --> 00:17:12,820
and if you have, uh, I mean, you, you too, Stuart would be good, but like what at this,

217
00:17:12,880 --> 00:17:19,100
this, as of now is a July 24th, 2017. What would you say the state of like, let's call it

218
00:17:19,100 --> 00:17:24,360
loosely.net, but Microsoft world development, what do you say this with the state of that

219
00:17:24,360 --> 00:17:28,340
stuff is going to the cloud? Where, where are we with all of that? Is it just like just a hundred

220
00:17:28,340 --> 00:17:32,300
percent gonzo doing it? Or like, how, how's the, the migration going?

221
00:17:33,640 --> 00:17:38,980
I mean, last week in Denver, I taught a, uh, a class to a bunch of developers who are teaching

222
00:17:38,980 --> 00:17:43,460
them.net cloud, native.net. Like, what does it mean to modernize your.net? So we had 40 something

223
00:17:43,460 --> 00:17:48,700
people in the room and you know, this was financial services mostly for the attendees. And for them,

224
00:17:48,700 --> 00:17:53,000
I think it was still new stuff to think of moving this to.net core, which is that new flavor

225
00:17:53,000 --> 00:17:57,620
that runs on Linux and windows and other stuff. And they're almost entirely on-prem still with

226
00:17:57,620 --> 00:18:02,580
their.net workloads. So, you know, I think like everything else kind of making its way to the

227
00:18:02,580 --> 00:18:07,380
cloud, but I think.net workloads are moving more slowly, just anecdotally since those shops have

228
00:18:07,380 --> 00:18:11,500
been, it's, it's more enterprise, a little more conservative. It's staying on-prem unless it's

229
00:18:11,500 --> 00:18:16,600
going to Azure, which is a, the sort of, you know, there's a stack overflow analytics last week

230
00:18:16,600 --> 00:18:21,100
that showed, Hey, if you're using Azure, you're probably writing C sharp. And if you're using,

231
00:18:21,220 --> 00:18:24,700
if you're in the Netherlands, somehow Azure is your preferred cloud, but every other place,

232
00:18:24,760 --> 00:18:29,760
the most questions for a country goes to Amazon in terms of a tag. So it was just interesting to see,

233
00:18:29,880 --> 00:18:33,940
you know, you can only extrapolate so much from those things and stack overflow questions,

234
00:18:33,940 --> 00:18:39,060
but it's real data from, you know, tens of thousands of users. So, you know, it's interesting.

235
00:18:39,220 --> 00:18:43,740
Most languages are going to the other clouds more prominently, but C sharp and .net obviously

236
00:18:43,740 --> 00:18:48,160
going to Azure. Yeah. We got to get those red monk folks to start slicing up their language thing

237
00:18:48,160 --> 00:18:52,860
by cloud. Not only that, but that would be an interesting, uh, what do they call that? A cut,

238
00:18:53,100 --> 00:18:56,960
a slice. How about, how about yourself? Uh, how about yourself, Stuart? What up there in trailer

239
00:18:56,960 --> 00:19:02,080
park boy land, what's, what's, what's the state of Microsoft stack stuff? Trailer park boy land.

240
00:19:02,160 --> 00:19:09,100
Wow. Uh, it's there, there, so there's tremendous, um, uh, install base and they're not

241
00:19:09,100 --> 00:19:15,320
going anywhere. Um, there's a lot of passionate Microsoft developers and customers I see across,

242
00:19:15,320 --> 00:19:22,360
um, Canada and New England and New York. And what I, what I see the barriers to cloud for

243
00:19:22,360 --> 00:19:27,380
Microsoft are kind of the same barriers we saw in other languages. It's about, uh, security

244
00:19:27,380 --> 00:19:31,540
and it's about integration. And I find that they're, they've lagged a little bit. Like

245
00:19:31,540 --> 00:19:36,420
there's a lot of things in Microsoft land that assumed, well, you naturally have an active

246
00:19:36,420 --> 00:19:41,120
directory or controller. And naturally that sits next to you. And naturally you're installing this

247
00:19:41,120 --> 00:19:48,440
on a windows machine that has a name after a Lord of the Rings character or some it centric,

248
00:19:48,440 --> 00:19:54,860
crazy naming convention, it one, two, three PR East, something like that. Right. And so the whole

249
00:19:54,860 --> 00:20:01,420
system is based on that mindset of you deploy something and it stays there forever. And all

250
00:20:01,420 --> 00:20:05,080
the security is based on that. And so I think only recently you're starting to see, for example,

251
00:20:05,760 --> 00:20:12,060
uh, like Kerberos in Docker for windows and it requires like four pages of PowerShell to make

252
00:20:12,060 --> 00:20:16,500
it work. Right. So we're, we're going to get there, but there's a whole lot of technical

253
00:20:16,500 --> 00:20:20,880
and knowledge that has to develop. So it's a bit lagging, but I think it's going to happen.

254
00:20:21,160 --> 00:20:23,720
It's just, uh, Microsoft's got their head in half around it.

255
00:20:23,720 --> 00:20:28,060
They got to, they got to tell that Snover guy, you can't retire yet. First, you have to move

256
00:20:28,060 --> 00:20:34,260
all the workloads. Once you do that, you can retire. But, uh, that, that guy's great. So,

257
00:20:34,320 --> 00:20:38,660
uh, also what's that, you know, I, I don't know anything about networking. So what's, what's

258
00:20:38,660 --> 00:20:40,120
this, uh, this congestion thing.

259
00:20:40,620 --> 00:20:44,340
I almost included that just for you. Cause I know you like to say you don't know the networking

260
00:20:44,340 --> 00:20:48,500
stuff. So I was, I was, I was just throwing you, just trolling you a bit with Google news.

261
00:20:48,500 --> 00:20:54,520
Now they ship this, uh, yeah, success, uh, BBR, which is not bash, uh, Bosch backup and

262
00:20:54,520 --> 00:20:59,960
restore, which is our BBR. It's bottleneck bandwidth and round trip is a new congestion control thing

263
00:20:59,960 --> 00:21:03,580
that Google created. And really the takeaway is, gosh, if you're a cloud provider, you have

264
00:21:03,580 --> 00:21:07,660
to continue to show differentiation. I just can't be a me too. Cause at some point that's

265
00:21:07,660 --> 00:21:12,540
just not interesting. And so how do I differentiate in this case, Google owns a giant network and

266
00:21:12,540 --> 00:21:16,740
they can ship now these new sort of algorithms that say, if you're running in Google cloud connectivity

267
00:21:16,740 --> 00:21:22,460
to our services, like big table or spanner or whatever is faster, you know, less bandwidth,

268
00:21:22,460 --> 00:21:27,260
and then even reaching down to the end user using their load balancer, their CDN is actually

269
00:21:27,260 --> 00:21:33,700
faster. So customers using Google products and Google cloud actually can get a faster network

270
00:21:33,700 --> 00:21:37,280
experience because of what they've built into that. So that's something it's just harder to

271
00:21:37,280 --> 00:21:40,760
do if you're Amazon or you're Microsoft, cause you don't own the fiber and you can't do some

272
00:21:40,760 --> 00:21:44,660
of those things. So that kind of a cool example, some great engineering to have a good blog

273
00:21:44,660 --> 00:21:48,980
post on that that we'll link to in the show notes here, but it's a, again, I like when people take

274
00:21:48,980 --> 00:21:53,840
advantage of their assets and make those competitive advantages and don't just dumb it down and make

275
00:21:53,840 --> 00:21:54,380
it a commodity.

276
00:21:55,180 --> 00:22:16,220
It's a huge deal. Almost every major customer that's on a public cloud, whether Azure or AWS or GCP, and I've stood up all three for Pivotal Cloud boundary. The number one challenge is networking and getting that right and getting that fast and dealing with all the bugs. So that, yeah, I saw that. That's going to be a big deal.

277
00:22:16,700 --> 00:22:17,160
That's exciting.

278
00:22:17,160 --> 00:22:22,340
Yeah, that does seem like a problem. Hence, hence my continued ignorance of it.

279
00:22:23,420 --> 00:22:24,580
Leave that to other people.

280
00:22:24,880 --> 00:22:25,340
That's right.

281
00:22:28,880 --> 00:22:55,080
Hey, it's interstitial mid-roll stuff. I just wanted to promote a few upcoming Pivotal things here. Through June, July, and August, we have the Cloud Native Roadshow coming to all sorts of cities. This is a free day-long event we do with Google that goes over what exactly Cloud Native is and how our customers are using Pivotal and Google technologies and approaches. The cities, and this is a long list, so get ready. The cities are Stuttgart, Dallas, Denver, LA, Seattle, San Francisco, Amsterdam, Seoul, Hong Kong, Sydney, and Singapore.

282
00:22:55,580 --> 00:23:04,460
There's a big list of dates that you can look at. You can check out the show notes for a link to it, or if you just want to go and Google for Pivotal Cloud Native Roadshow, you'll find it pretty easily.

283
00:23:04,780 --> 00:23:17,280
We also have Spring Days Atlanta coming up July 18th and 19th. It's chock full of sessions for developers who want to learn more about the Spring Framework, Cloud Native style development, and of course, to be fully buzzword compliant, microservices.

284
00:23:17,280 --> 00:23:27,560
If you go to springdays.io, you can get more info. And that's the last Spring Days we're having so far that we have scheduled this year. So get that one in if you're over in grits and pork land. It'll be good stuff.

285
00:23:27,760 --> 00:23:38,060
Finally, while it's way in the future, we also have SpringOne platform coming up December 4th and 5th. Now, registration just opened recently for this. I think you might have missed the early bird thing for it, but that's fine.

286
00:23:38,060 --> 00:23:47,820
There's also still the CFP open. It closes on September 1st. Now, what goes on at this conference? Well, it's full of what I would call the suit track and the technology track.

287
00:23:48,020 --> 00:24:02,160
In the suit track, you've got case studies and managers and developers as well, but organizations talking about how they've transformed their company and what they're doing with Cloud Native and their organizations, how they're getting good results by switching over to doing things in more of a pivotal way.

288
00:24:02,160 --> 00:24:28,400
Then there's also plenty of events for those of you out there who enjoy more nerding out and doing technical things to check out. I'm one of the chairs of the DevOps pipeline and monitoring track that we informally call it. We've already got lots of excellent talks queued out from the likes of Home Depot, Express Scripts, Allstate Northern Trust, and of course, plenty of pivotal people. I'll be speaking in that track if that's anything. So come on there. Again, it's in San Francisco, December 4th and 5th.

289
00:24:28,400 --> 00:24:34,580
And if you just go to springplatform.io, you can check it all out. And with that, enjoy the episode this week.

290
00:24:38,100 --> 00:24:49,320
Well, so I don't know. You know, last week we were talking about enterprise architecture and I'm trying to figure out how it maps in the cloud native world.

291
00:24:49,320 --> 00:24:58,240
And since then, you know, we had our episode last week. I also have I've done an episode with with a former pivotal person, Matt Walburn, where we talked about it.

292
00:24:58,740 --> 00:25:04,540
We'll do a second one. I think that'll be fun. And then also, I guess on Friday or maybe it was Thursday. I don't know.

293
00:25:05,260 --> 00:25:10,940
I had a recording with Matt Curry of Allstate and our very own Andrew Clay Schaefer just talking about it more.

294
00:25:11,020 --> 00:25:19,780
And I think I think in that episode, I or the three of us, if you will, sort of forced ourselves to finally trot out a complete theory of it.

295
00:25:19,780 --> 00:25:29,180
But I'll put links to those in the show notes. They're over in my my my weird bucket podcast called the Coté Show Variety Podcast over at Coté.

296
00:25:29,180 --> 00:25:37,140
Coté Show. But when I was kind of speaking of trolling, when I was casting out a net of people to talk to on this topic, Stuart chimed in.

297
00:25:37,760 --> 00:25:46,980
And so so we have him on now to to kind of pontificate and eludicate and other Cates about cloud native enterprise architecture.

298
00:25:46,980 --> 00:25:50,440
But before that, so you were kind of going over your background. We were talking earlier.

299
00:25:50,680 --> 00:25:55,460
Give people a sense of your your relevant background for this topic.

300
00:25:57,300 --> 00:26:11,700
Sure. So I started out doing consulting and in Wall Street and and the dot com thing around the 90s, mostly startup stuff and then shifted into the enterprise.

301
00:26:12,360 --> 00:26:22,520
Did quite a bit. I was actually part of the founding enterprise architecture team at at Rogers Communications, which is the biggest telco wireless, wireless telco and cable company in Canada.

302
00:26:23,180 --> 00:26:29,340
And that was around 2002 when we did, you know, enterprise architecture things early.

303
00:26:29,340 --> 00:26:39,700
So actually, you know, really predating the the market groundswell, I'd say, in the 2003 timeframe and starting to get into more DevOps, the agile things, too.

304
00:26:40,520 --> 00:26:46,660
And from there, I worked at BA systems for about five years.

305
00:26:46,680 --> 00:26:58,580
I was a lead architect across Canada and we did a lot for enterprise architecture consulting and SOA across the country, trying to convince people, no, don't throw everything into a single ESB.

306
00:26:58,680 --> 00:27:02,560
That's not the architecture we tried to recommend, but people didn't want to listen.

307
00:27:03,180 --> 00:27:13,840
And then on there, I did a couple I did a cloud startup in San Francisco for a few years that tragically all I got was a T-shirt at the end.

308
00:27:15,060 --> 00:27:19,060
I think I think what they say is there were a lot of learnings that you had, right?

309
00:27:19,340 --> 00:27:21,180
Yeah, there was a lot of learnings.

310
00:27:21,260 --> 00:27:21,420
Yeah.

311
00:27:23,660 --> 00:27:25,660
Yeah, definitely did everything we could do wrong.

312
00:27:26,520 --> 00:27:40,500
And then after that, I actually became the lead architect for a set of services at Canadian Pacific Railway that eventually led me to become general manager of IT operations, mainly because I was I knew the CIO who used to be my boss at Rogers.

313
00:27:40,500 --> 00:27:55,500
And so we did a major transformation there in sourcing, starting to do some early cloud and some EA work moving towards SAP as well as keeping some services around for the actual operational railway side, which SAP couldn't really run.

314
00:27:56,660 --> 00:28:03,840
And then from there, I went on to to work for Pivotal, which I've been trying to work for for a number of years, actually, when it was first formed.

315
00:28:04,640 --> 00:28:15,180
So most of my my background is I've been vendor side, I've been IT executive side, I've been IT developer, you know, and consultant and trainer side.

316
00:28:15,180 --> 00:28:25,920
So I've kind of seen every piece of this and I've interacted with, you know, a dozen plus EA groups being part of them or just fighting them or, you know, cooperating with them, depending on the context, I guess.

317
00:28:26,460 --> 00:28:26,560
Yeah.

318
00:28:26,680 --> 00:28:31,980
So, yeah, you just need to go be a an industry analyst now and you'll have achieved tech career bingo.

319
00:28:32,140 --> 00:28:34,940
Like, like, you'll, you'll, you'll covered all the bases.

320
00:28:35,180 --> 00:28:36,960
No, yeah, that's, that's interesting.

321
00:28:37,100 --> 00:28:39,020
So, and, and highly relevant.

322
00:28:39,180 --> 00:28:50,620
So, I mean, let's start off with like, given, given that experience, like how without, without sort of like, you know, jabbing some spears of cloud native into it, like, like, what is it?

323
00:28:50,700 --> 00:28:52,260
What does an enterprise architect do?

324
00:28:52,460 --> 00:28:53,220
Like, how do they come up?

325
00:28:53,260 --> 00:28:57,440
What are their responsibilities and what does it end up looking like in practice?

326
00:28:58,120 --> 00:29:00,540
And, you know, just how would you describe what it is?

327
00:29:01,680 --> 00:29:06,460
I think it varies from company to company, depending on how IT focused the EAs are.

328
00:29:06,560 --> 00:29:07,420
I think mostly they are.

329
00:29:07,660 --> 00:29:12,100
There are some folks that are more interested in the business side, especially SAP shops.

330
00:29:12,240 --> 00:29:18,600
You tend to have enterprise architects that aren't super technical, but they understand a business domain and the process is really, really well.

331
00:29:18,840 --> 00:29:25,520
So those do exist, but I think most EA groups are responsible for, I guess, three things.

332
00:29:26,020 --> 00:29:31,900
There's the, the do and do not list of here are the things you are allowed and not to do technically within the company.

333
00:29:32,100 --> 00:29:32,900
There's the buy list.

334
00:29:32,980 --> 00:29:38,060
If you're the products you're allowed to buy or use, and then there is the, they know where the bodies are buried.

335
00:29:38,560 --> 00:29:41,880
They're, they're, they're, they sort of are the, the corporate memory.

336
00:29:41,880 --> 00:29:45,780
Like if you, if anybody's a Game of Thrones fan, there's the Citadel and the Maesters.

337
00:29:46,160 --> 00:29:47,100
They're, they're that.

338
00:29:47,360 --> 00:29:54,360
They, they, they kind of remember what happened and, and, and which projects died and which ones survived and what works around here.

339
00:29:54,520 --> 00:30:04,920
Uh, how does this place actually get things done or, um, you know, we, you know, what is something that's going to fall over if you look at it funny, uh, in the existing systems, right?

340
00:30:05,080 --> 00:30:06,160
So I think it's those three things.

341
00:30:06,220 --> 00:30:07,740
The last one is probably the most important.

342
00:30:08,400 --> 00:30:24,360
Um, because, you know, very often the enterprise architects, I think for the last 10 to 15 years, at least have been really focused on how do I actually get things done quicker, uh, and better with, with safety.

343
00:30:24,520 --> 00:30:24,880
Right.

344
00:30:25,040 --> 00:30:26,800
Which is the same thing we talk about with cloud native.

345
00:30:26,840 --> 00:30:42,880
We just talk about it in a different way, but they've all been trying to find ways that in a very ordered structured way that, um, allows them to centralize the decision making, create something that makes people move faster, which seems to be a bit of an oxymoron, but that seems to be the case.

346
00:30:42,880 --> 00:30:43,040
Right.

347
00:30:43,040 --> 00:30:51,020
And this is why they're, they're, they're always looking for that new tool or they're looking for that new, um, model that allows them to say, ah, I have something.

348
00:30:51,020 --> 00:31:00,980
And this will be the thing that will allow us to me to not have to, you know, handhold everybody, but I can give them a set of constraints or a tool and that will make them go faster.

349
00:31:00,980 --> 00:31:08,680
And, um, while staying safe, I think that's been kind of the Holy grail that they've been looking for, at least it architects from what I've seen.

350
00:31:08,980 --> 00:31:22,220
Um, and it's this kind of iterative cycle of, you know, trying to control things, failing, getting totally irrelevant, watching things fail, getting more relevant again, coming up with a new idea or a new, you know, paper to explain a new idea.

351
00:31:22,220 --> 00:31:26,940
And iterating on that over, over a series of 10, 20 years is what I see EA doing.

352
00:31:27,200 --> 00:31:27,420
Yeah.

353
00:31:27,460 --> 00:31:31,120
You know, it's a very like helpful, not helpful, hopeful sort of definition.

354
00:31:31,120 --> 00:31:37,880
It's almost like the, the enterprise architect is, is the, uh, I don't know what, what word am I looking for?

355
00:31:37,880 --> 00:31:47,220
The one who's always ensuring that, well, let me use some BS terms that, that the business has enough agility with its IT, right?

356
00:31:47,260 --> 00:31:57,100
That, that, that you're always using the, the best stuff to, uh, the best process and technology and everything to just help out, help the business out, uh, if you will, versus.

357
00:31:57,460 --> 00:31:58,040
That's the intent.

358
00:31:58,240 --> 00:31:58,420
Yeah.

359
00:31:58,420 --> 00:31:58,520
Yeah.

360
00:31:58,520 --> 00:31:59,040
That's the intent.

361
00:31:59,100 --> 00:32:00,240
That doesn't mean they actually do it.

362
00:32:00,860 --> 00:32:06,100
Um, so where does that, I mean, so those are three good categories.

363
00:32:06,200 --> 00:32:06,680
I like that.

364
00:32:06,740 --> 00:32:08,120
So, but where does that come from?

365
00:32:08,160 --> 00:32:10,580
So where do I get my list of do's and don'ts?

366
00:32:10,580 --> 00:32:11,360
I mean, is that patterns?

367
00:32:11,360 --> 00:32:13,720
Where do I get my list of tech I should or shouldn't use?

368
00:32:14,100 --> 00:32:19,500
And how do I become a successful matchmaker or understand that there was this being embedded in projects?

369
00:32:19,620 --> 00:32:22,620
Is this where you see there's a lot of innovation lab sort of work happening?

370
00:32:22,740 --> 00:32:27,160
Kind of, how do I get, how am I capable of doing those three things as a successful EA?

371
00:32:28,220 --> 00:32:30,800
Well, there's the old school way and then there's the new school way.

372
00:32:30,920 --> 00:32:31,220
Right.

373
00:32:31,320 --> 00:32:34,000
Uh, and they're very, very different, right?

374
00:32:34,000 --> 00:32:50,080
The old way you used to do it was, it was a combination of, um, you know, classic first principles of design and, um, you know, just history of learning the hard way of things that did and didn't work in a particular context.

375
00:32:50,080 --> 00:32:50,360
Right.

376
00:32:50,600 --> 00:32:58,140
So, you know, everybody's interested in, you know, if you like data architecture, you're, you have familiarity with the history of how data evolved.

377
00:32:58,220 --> 00:33:00,740
You have a bit history of, of how middleware evolved, right?

378
00:33:00,740 --> 00:33:04,980
Originally it was these trans, these crazy mainframe transaction processors.

379
00:33:04,980 --> 00:33:11,120
Then it was, you know, app servers and now it's lightweight containers and microservices.

380
00:33:11,420 --> 00:33:11,600
Right.

381
00:33:11,940 --> 00:33:19,580
And so you have a bit of history and you understand, okay, well, um, uh, I think you were talking last week about enterprise architecture strategy, right?

382
00:33:19,600 --> 00:33:23,260
Which is that book that was in 2006 with, with real and Ross.

383
00:33:23,600 --> 00:33:23,880
Right.

384
00:33:23,900 --> 00:33:26,420
And their whole point is, okay, our business is trying to do X.

385
00:33:26,640 --> 00:33:29,640
We make shoes or we run trains.

386
00:33:30,080 --> 00:33:35,020
Um, we don't have 50 business units that all run differently.

387
00:33:35,020 --> 00:33:36,080
We do one thing.

388
00:33:36,080 --> 00:33:45,580
So that lends itself to saying, okay, a list of at least high level do's and don'ts in terms of, you know, we really don't need 15 email servers.

389
00:33:45,580 --> 00:33:47,940
We really don't need 15 ERP systems.

390
00:33:47,940 --> 00:33:48,240
Right.

391
00:33:48,560 --> 00:33:51,420
And yet this is what we see time and time again.

392
00:33:51,420 --> 00:33:57,620
I mean, there's, um, organizations, even in Canada that have like a hundred ERP systems in the federal government.

393
00:33:58,120 --> 00:34:02,940
Um, just because they just let them proliferate and they never actually said, no, you can't actually do that.

394
00:34:03,020 --> 00:34:04,280
That's, that's not right.

395
00:34:04,520 --> 00:34:08,040
So I think there's, there's just a basic history and learning things.

396
00:34:08,040 --> 00:34:15,980
And then there's the, um, I think all architect enterprise architects, at least they've been around 10 years have an allergy to duplication.

397
00:34:15,980 --> 00:34:28,080
It seems like their mission in life is to eliminate all duplication of effort and all, uh, anybody that might possibly be doing something that has already been done, which is a bit misguided.

398
00:34:28,740 --> 00:34:29,100
Yeah.

399
00:34:29,140 --> 00:34:29,620
But that's trouble.

400
00:34:29,680 --> 00:34:33,400
I mean, I, I, again, I experienced that in my own role with that, but yeah.

401
00:34:33,400 --> 00:34:36,180
How do you find to make sure that you don't accidentally stifle innovation?

402
00:34:36,180 --> 00:34:36,860
Because you know what?

403
00:34:36,900 --> 00:34:37,820
We're a vSphere shop.

404
00:34:37,880 --> 00:34:41,220
Stop screwing around with cloud or, Hey, you know, we have X.

405
00:34:41,280 --> 00:34:41,940
It's worked fine.

406
00:34:41,980 --> 00:34:43,460
It's this relational database for years.

407
00:34:43,560 --> 00:34:44,800
Stop screwing around with no SQL.

408
00:34:45,200 --> 00:34:51,760
I mean, obviously it's not always that black and white, but how do you sometimes encourage reusability as long as it are not reusable using, right?

409
00:34:51,860 --> 00:34:55,280
Starting fresh as long as you allowed you some quick learning and some quick feedback.

410
00:34:55,880 --> 00:35:01,540
Well, I had this conversation with the head of SAP architecture at a bank, uh, here in Canada, uh, a while ago.

411
00:35:01,540 --> 00:35:10,300
And I, I was explaining that the new model, I mean, if you're thinking about digital transformation and the, the whole onus on, look, we got to change our customer experience.

412
00:35:10,300 --> 00:35:20,000
We got to become, uh, more quicker responding to kind of, you know, not only just, uh, fixing our mobile apps or our website to look better.

413
00:35:20,000 --> 00:35:22,960
It's, it's, it's, you know, it's design isn't how it looks, it's how it works.

414
00:35:22,960 --> 00:35:28,280
We have to actually change our backend systems and this isn't something we can just sit and stare at the ceiling and come up with.

415
00:35:28,420 --> 00:35:32,820
We actually have to experiment and we have to do it in a decentralized way with fast feedback.

416
00:35:33,480 --> 00:35:37,880
And not only are these teams iterating, we have to iterate as architects too.

417
00:35:38,000 --> 00:35:41,300
So now it's about, oh, all about duplication of effort.

418
00:35:41,340 --> 00:35:42,840
It's all about, let's try a few experiments.

419
00:35:43,140 --> 00:35:46,640
Let's make sure that they are, uh, can succeed or fail quick.

420
00:35:46,640 --> 00:35:59,660
They're funded, fairly contained, and they're, uh, something that can be run by a team without having to require the entire organization to do steering committees or, or all these kinds of checkpoints and whatnot.

421
00:35:59,660 --> 00:36:05,160
You want to have, um, this kind of more decentralized focus model than we have in the past.

422
00:36:05,160 --> 00:36:15,140
If you think of it is kind of like this, this pendulum that swings politically between decentralization and centralization, it's always about the balance of power.

423
00:36:15,140 --> 00:36:16,700
It's not about one or the other.

424
00:36:16,840 --> 00:36:35,100
And I think we're, we're swinging back away from centralization towards decentralization radically now with microservices and with, um, you know, with cloud native, which is a way of saying, even if you are a unified company, even if you are having one mission, there is no way one group can actually solve all these problems.

425
00:36:35,100 --> 00:36:36,480
You're, I mean, nobody's that smart.

426
00:36:36,480 --> 00:36:51,760
We have to, um, you know, uh, uh, technical people with, uh, uh, actual users getting feedback and using that to learn.

427
00:36:51,760 --> 00:36:59,140
So it's a little bit, it's a bit of a, the test a little, um, you know, build a little and then architect a little, um, I think matters.

428
00:36:59,140 --> 00:37:14,680
So the intent really now for the EA is about how do I get out of their way and provide constraints so that they're maximizing all these little, you know, these little pockets that are, um, going to be able to come up with these ideas.

429
00:37:14,680 --> 00:37:22,000
But we have a, uh, kind of a standard way of ensuring, you know, what's really important to the enterprise.

430
00:37:22,180 --> 00:37:24,660
Well, I want to mitigate, mitigate risk on my data to some degree.

431
00:37:24,760 --> 00:37:26,680
So I'm going to have some standards around my data.

432
00:37:27,260 --> 00:37:29,040
Um, but they're not going to be technical standards.

433
00:37:29,040 --> 00:37:30,280
It's not going to be, you must use Oracle.

434
00:37:30,540 --> 00:37:43,680
I'm going to let a little more freedom on my teams to say, well, use the data standard or tool you want within some relative bound, uh, as long as you can run it, um, and operate it with what the business wants.

435
00:37:43,680 --> 00:37:47,740
But, you know, here's what the data standards are or some, something like that.

436
00:37:47,740 --> 00:37:47,960
Right.

437
00:37:48,140 --> 00:37:54,020
I think having a much lighter touch on the standardization, um, is, is the real key.

438
00:37:54,020 --> 00:37:57,180
And then, and learning from that and evolving from that is what I'm saying.

439
00:37:57,180 --> 00:38:00,000
So, and also making sure that you realize there's no one size fits all.

440
00:38:00,760 --> 00:38:13,500
So, so I think, I think, I think Richard has zoomed in on perhaps the, uh, I don't know if it's the, uh, pivotal, if you will, the, the, uh, the, the, the pivotal conflict that scurries around between like cloud native and enterprise architects.

441
00:38:13,500 --> 00:38:15,420
But you, you've, you've, you've talked about it quite a bit.

442
00:38:15,440 --> 00:38:21,180
And so I wonder how you would explain, well, I wonder, I wonder how you would explain what I'm about to say, so to speak.

443
00:38:21,360 --> 00:38:29,620
But it seems like going back to that book, the, uh, enterprise architecture is strategy, which, uh, uh, maybe I need to read more books, but man, that book's pretty good.

444
00:38:29,620 --> 00:38:31,540
Now that I think of it, keep mentioning it.

445
00:38:31,540 --> 00:38:49,000
But in that book, the, the task of a circa 2006 enterprise architect, in my view was to guide the company, not just it, but guide the company along the gradient of decentralized it.

446
00:38:49,000 --> 00:39:01,740
And the first way that they decided to do that is basically like, uh, you've got these four types of business models or ways that businesses operate.

447
00:39:01,740 --> 00:39:08,400
Um, and based on how the business operates, highly siloed or highly centralized, you shoot, you're on that gradient somewhere.

448
00:39:09,140 --> 00:39:13,700
And I don't know, it's starting to feel like, I don't know how strong this is.

449
00:39:13,700 --> 00:39:31,620
Maybe you can tell me on a scale of one to 10, how, how true this is or how deep it goes that a lot of the proposition of, of cloud native stuff is that we used to have this constraint where you would have to think about standardizing and centralizing versus not doing that.

450
00:39:31,920 --> 00:39:39,380
But now there's like this third option where you can get all of these efficiencies by having a more siloed approach.

451
00:39:39,380 --> 00:39:46,020
I don't know, but by somehow you allow people to be a lot more independent and not be told exactly how to operate.

452
00:39:46,020 --> 00:39:57,100
And it removes a lot of the, well, a lot of the dangers of having a sort of a, a, what, what you might've called a cowboy approach back then, perhaps now you call it a cow person approach.

453
00:39:57,580 --> 00:40:06,740
Uh, but you know, having more of a, each team deciding what they should do is actually not necessarily, I mean, not that it's better, but it's a lot safer to go about that path.

454
00:40:06,740 --> 00:40:07,100
I don't know.

455
00:40:07,100 --> 00:40:14,920
I mean, that's all jumbled up and weird, but that's the kind of the notion that I keep coming back to again and again, that that's a lot of what cloud native stuff does for enterprise architecture.

456
00:40:14,920 --> 00:40:16,660
What, what, what do you think of that mess?

457
00:40:18,920 --> 00:40:26,500
Yeah, I think that the, there's been a fundamental misunderstanding about what centralization actually should be.

458
00:40:26,600 --> 00:40:34,600
Um, I think we forgot about things like lean and about all the lessons we're learning in business about, you don't want to insert yourself in the process.

459
00:40:34,600 --> 00:40:36,160
You don't want to be a bottleneck.

460
00:40:36,480 --> 00:40:44,260
And what was happening is we were inserting a human process of, uh, you know, checks and balances and making sure things are right.

461
00:40:44,260 --> 00:40:46,580
And, or, oh, that's not on the buy list.

462
00:40:46,660 --> 00:40:53,820
You can't do that as opposed to a more trust-based approach that is, okay, let's allow some experimentation.

463
00:40:54,620 --> 00:41:03,760
And in, you know, we'll have kind of this convergent engineering approach where eventually we'll come, we'll come up with some insights about, all right, don't do that anymore.

464
00:41:03,760 --> 00:41:05,480
Or, or, or no, this is a good idea.

465
00:41:05,660 --> 00:41:10,280
And I think that the standardization doesn't go away.

466
00:41:10,340 --> 00:41:11,780
I think standardization is important.

467
00:41:11,780 --> 00:41:21,640
If you think about what we say in cloud native, um, it's about creating a standard set of patterns and processes and automation that gives you a pipeline.

468
00:41:21,640 --> 00:41:26,840
It gives you a way it's a, it's a very, you know, it's like a, it's not a single lane highway.

469
00:41:26,960 --> 00:41:34,580
It's like a 10 lane highway of here are the 10 ways in which you can get something deployed, you know, develop, delivered, tested into production quickly.

470
00:41:35,340 --> 00:41:43,520
Um, as opposed to, um, the, the, the two extremes that are, that tend to be kind of done in a lot of enterprises.

471
00:41:43,520 --> 00:41:53,260
One is there is only one way and it's SAP or this, there's only one way and it's using our existing monolithic platform or whatever that we built in house 10 years ago.

472
00:41:53,260 --> 00:41:56,800
And the guy left for Google five years ago, and we don't know how to maintain it.

473
00:41:56,800 --> 00:41:56,940
Right.

474
00:41:56,940 --> 00:42:06,720
The other opposite opposite is, um, you know, the, the quote unquote, um, enterprise DevOps approach where you're basically chasing taillights.

475
00:42:06,720 --> 00:42:10,880
You're paving the road behind the developers, hoping that somebody will use it in the future.

476
00:42:11,180 --> 00:42:17,240
Development teams are off doing something and you're using shepherd puppet or whatnot to automate what they did.

477
00:42:17,320 --> 00:42:20,500
And it's not exactly generic.

478
00:42:20,500 --> 00:42:23,880
It's kind of like, Hey, look, I can turn the crank on the thing that you did.

479
00:42:24,180 --> 00:42:24,740
That's great.

480
00:42:25,320 --> 00:42:26,560
Next project comes around.

481
00:42:26,680 --> 00:42:35,540
I might be able to read pieces of that, but I can't actually apply it as opposed to, no, let's actually build a set of capabilities or, you know, purchase or some combination.

482
00:42:36,000 --> 00:42:43,560
That is a standard that forces a certain set of practices and constraints, or at least really encourages you to think in a certain way.

483
00:42:44,320 --> 00:42:51,700
Um, and I think that the, you know, that enforces enterprise architecture.

484
00:42:51,860 --> 00:42:53,240
It's having it in the software.

485
00:42:53,240 --> 00:43:05,400
I mean, if you think of like something like ITIL, these standards for operations, it's basically a bureaucratic process to enforce things through Excel spreadsheets and ticketing systems, which really should just be in the software to begin with.

486
00:43:05,740 --> 00:43:08,640
And so we've inserted humans in the mix for safety sake.

487
00:43:08,920 --> 00:43:12,300
And what we're now saying is, no, the kind of robots can make this thing safe.

488
00:43:13,000 --> 00:43:16,900
Um, we don't need humans to do it so much except to operate the robots.

489
00:43:16,900 --> 00:43:28,420
We're, we're, we're, we're maintaining software to run the software rather than having humans kind of in the mix, keeping an eye on things and being panicked all the time and doing change advisory boards and other things that just slow things down.

490
00:43:28,500 --> 00:43:33,600
They don't actually, you know, make things safer necessarily when you're trying to change things at speed.

491
00:43:33,860 --> 00:43:37,500
So there's almost this, uh, sorry, sorry to overrun you there.

492
00:43:37,500 --> 00:43:45,940
There's, there's, uh, uh, there's this third way, if you will, that sounds all fancy, like some seventies, uh, self-help stuff.

493
00:43:46,100 --> 00:43:55,820
There's this like, uh, third way of enterprise architecture that is beyond the, uh, the tail light chasing the sort of cow path thing, if you will.

494
00:43:56,180 --> 00:44:00,980
Uh, and, and, and, and, and it's almost a compromise of the two things.

495
00:44:00,980 --> 00:44:05,920
It sort of, it sort of feels like, at least when I look at what, what we at pivotal would call cloud native stuff, right?

496
00:44:06,160 --> 00:44:13,400
It says we are going to incredibly standardize and centralize a certain part of the IT stack.

497
00:44:13,900 --> 00:44:17,700
And then above that, well, we'll figure out what to do, right?

498
00:44:17,720 --> 00:44:25,620
Like we might, we might all mandate the same language and mandate the same way of operating, but there's almost like, uh, it's not so clear cut.

499
00:44:25,620 --> 00:44:26,920
And that's why I always struggle with it.

500
00:44:26,920 --> 00:44:35,580
But there are in a cloud native way of operating, there's an extremely strong, almost take it or leave it sort of set of EA principles.

501
00:44:36,160 --> 00:44:39,320
Um, you know, like you should be running on cloud for first.

502
00:44:39,420 --> 00:44:47,520
Otherwise it's, I don't know, whatever native, uh, but you should be running on a highly automated cloud platform.

503
00:44:47,520 --> 00:44:54,100
Like obviously self-serving something like pivotal cloud foundry, which basically removes all choice about your infrastructure.

504
00:44:54,340 --> 00:44:59,840
And then as you get closer to, uh, you know, the, the, the pivotal James Watters value line, it's like all this stuff.

505
00:44:59,920 --> 00:45:03,400
Basically we mandate and you can't decide to do or not to do it.

506
00:45:03,740 --> 00:45:14,400
And, and so that is like extremely strong, old school, um, much not liked enterprise architecture, like mandating, you can only do this thing.

507
00:45:14,720 --> 00:45:18,320
But then in turn, it seems like, and this is, this is where all the interesting stuff happens.

508
00:45:18,320 --> 00:45:21,360
The constraint that gets lifted is like above that.

509
00:45:21,920 --> 00:45:22,920
And there's exceptions.

510
00:45:23,140 --> 00:45:25,900
You just sort of do what makes sense now.

511
00:45:26,940 --> 00:45:31,900
Oh, well, first of all, and now that there, there becomes some confusion of how do you make sure all these things coordinate.

512
00:45:31,900 --> 00:45:37,220
And it's gotta be more than that one article that Martin Fowler and that other guy, no one ever remembers wrote about microservices.

513
00:45:37,680 --> 00:45:41,600
Obviously it's more complicated than that, but there is some way of coordinating these things better.

514
00:45:41,680 --> 00:45:51,760
But one, I mean, what do you think of the, of my notion of like, you sort of have like sliced in really strict enterprise architecture at one point, and then you allow the, the cow person stuff above that.

515
00:45:52,300 --> 00:46:00,520
So that's exactly the point is that I think EA either tends to locking everything down or it tends towards locking nothing down depending on the culture.

516
00:46:00,520 --> 00:46:04,720
And what we're saying is that there's some things that need to be locked down.

517
00:46:04,720 --> 00:46:12,260
And there's some things that don't, I mean, you're always going to fight cultures where you have developers that want to, they don't trust anything that ops does or the EA does.

518
00:46:12,320 --> 00:46:14,220
And they want to compile their own gen two kernels or whatever.

519
00:46:14,800 --> 00:46:20,500
Um, and, and then you have other people that are like, they want everything spelled out and they want everything checked by a committee.

520
00:46:21,300 --> 00:46:24,280
Um, I'm a big fan of Simon Wardley's work.

521
00:46:24,280 --> 00:46:37,480
I think that his approach to, I guess, trimodal IT or his mapping approach where he says, you know, there really are, there's town planners, there's settlers, and then there's pioneers, I guess, in any organization.

522
00:46:37,700 --> 00:46:39,280
You know, just, just sort of at the meta layer.

523
00:46:39,440 --> 00:46:40,120
It's, it's odd.

524
00:46:40,180 --> 00:46:41,080
I mean, he's British, right?

525
00:46:41,200 --> 00:46:48,520
That, uh, that a very, I mean, something that, that I think when we're born up here, you know, in Canada and America, we understand that model perfectly.

526
00:46:48,740 --> 00:46:55,280
I think it's one of the, one of the doctoral procedures that like conquering the West is injected into our brains directly right after they slap us.

527
00:46:55,360 --> 00:46:57,120
So it is a, it's a good metaphor.

528
00:46:57,460 --> 00:46:59,860
Anyhow, I got excited about my little side note.

529
00:47:00,440 --> 00:47:00,640
Yeah.

530
00:47:01,560 --> 00:47:09,300
But I, and so I think that, so I'm actually dealing with a very, a very large bank, the top 10 bank, and we're, we're working through this, uh, model right now.

531
00:47:09,300 --> 00:47:11,160
And it's three different enterprise architecture patterns.

532
00:47:11,820 --> 00:47:15,100
There's a mode one, which is a legacy.

533
00:47:15,280 --> 00:47:23,840
So that is mainframe plus old school web sphere plus old school Vitria or, you know, nonsense EAI from the nineties.

534
00:47:24,320 --> 00:47:38,760
Um, there's mode two, which was, I guess, cloud 1.0, um, DevOps 1.0, um, didn't really get a DevOps culture, sort of use Jenkins, sort of use cloud foundry, sort of use, um, you know, Docker.

535
00:47:39,120 --> 00:47:43,580
Uh, but it's all kind of, they didn't standardize the middle layer.

536
00:47:43,580 --> 00:47:46,740
Like it was complete, basically use these technologies.

537
00:47:47,420 --> 00:47:49,400
Um, and, uh, that's it.

538
00:47:49,960 --> 00:47:59,880
Um, and so what wound up happening is there really isn't a lot of productivity benefits because, um, it's a bit of a mess in terms of what's actually supportable.

539
00:48:00,080 --> 00:48:03,420
Um, everybody, every team's kind of doing its own thing, et cetera.

540
00:48:03,420 --> 00:48:16,360
And then mode three is really, uh, you know, is what they're trying to be is more like what the intent of the settlers are or the pioneers where it's like, I'm not building a single lane highway, like mode one.

541
00:48:16,760 --> 00:48:25,460
I'm not building kind of like this, uh, smorgasbord, which is what they did in mode two, which really is more what pioneers want, which is give me freedom or give me death.

542
00:48:25,540 --> 00:48:27,560
I don't care if I have an SLA.

543
00:48:27,720 --> 00:48:30,140
I just want to be able to run my ACA clusters, damn it.

544
00:48:30,600 --> 00:48:36,520
Um, whereas what, what they've created is this new one, which is like, no, we're standardizing everything from here down.

545
00:48:36,700 --> 00:48:38,700
You have to use our CICD pipeline.

546
00:48:38,960 --> 00:48:40,800
It's going to be Spinnaker and Concordes.

547
00:48:40,800 --> 00:48:46,860
You have to use our way of doing, here's 10 different languages, right?

548
00:48:47,100 --> 00:48:47,960
Uh, we're going to container.

549
00:48:48,120 --> 00:48:53,900
It's going to be these, uh, Java.net, Python, Ruby, et cetera, done our way.

550
00:48:54,000 --> 00:48:57,480
And if you must use Docker, it's going to be based on our root image.

551
00:48:57,760 --> 00:48:59,440
Uh, you don't get to bring an image.

552
00:48:59,900 --> 00:49:03,200
Um, and, and it'll be deployed in this exact way.

553
00:49:03,480 --> 00:49:06,400
And on top of that, you get to do whatever you want.

554
00:49:06,700 --> 00:49:13,060
And so that, um, has had, um, a lot of traction with the development community.

555
00:49:13,500 --> 00:49:19,380
This is obviously leading to new problems in the data community and in the interoperability side of the business.

556
00:49:19,800 --> 00:49:23,080
But, you know, let's crawl before we run, I guess.

557
00:49:23,600 --> 00:49:24,540
Yeah, that's what I was going to ask you.

558
00:49:24,580 --> 00:49:31,280
Cause, you know, I think back to my EA time where we do some master data management efforts and, hey, you had to, you know, fill out a form.

559
00:49:31,280 --> 00:49:34,920
If you wanted access to the data entity, you wanted to maybe access or change.

560
00:49:34,920 --> 00:49:37,600
And, you know, to some extent that was for reasons, right?

561
00:49:37,640 --> 00:49:52,220
I mean, it's all good intentions, but as you say, just because you automate some of the infrastructure layer and your container base image and your runtime, that doesn't mean I still can't use, or I could still accidentally enforce too much on data entity definitions or messaging patterns or what have you.

562
00:49:52,220 --> 00:50:00,360
So do you just feel like that's stage two, like let's get some of the infrastructure aspects of architecture nailed down so teams can start to at least pick up velocity.

563
00:50:00,620 --> 00:50:07,640
And then we take a look at some of the data patterns, integration patterns, and the like, and figure out what kind of light touch is needed there.

564
00:50:07,740 --> 00:50:12,920
So we're not accidentally mixing too many things that make maintenance tough or make it really tough to share information.

565
00:50:12,920 --> 00:50:16,920
Or to Coté's point, is this all local optimization within your microservice?

566
00:50:17,060 --> 00:50:28,180
And if you choose to define a data entity this way, and I might choose to extend that because my business unit is not just use customer, but it has a different perspective of customer, that that's fine.

567
00:50:28,220 --> 00:50:29,500
And I just do that kind of translation.

568
00:50:29,620 --> 00:50:31,320
How do you see the data services mixing in?

569
00:50:32,340 --> 00:50:32,840
Good question.

570
00:50:32,940 --> 00:50:45,060
I think, you know, the way I always liked the way Adrian Co-Croc used to talk about microservices at Netflix and that it was, you know, the business person, the developer, but also the analytics person.

571
00:50:45,060 --> 00:50:59,980
And I think that it's important that as you're doing this, you do have to have some standards about providing a tap or an interface or something to be able to hook anything you're building into a broader analytics ecosystem, call it a data lake or whatever you want to call it.

572
00:51:00,820 --> 00:51:03,120
That at least allows me to get at your data.

573
00:51:03,220 --> 00:51:10,980
It's not, you know, you didn't, it's like, Hey, I wrote this thing using GRPC and, um, Golang and you can't get at my data.

574
00:51:11,080 --> 00:51:11,360
Ha ha.

575
00:51:11,480 --> 00:51:14,420
No, you have to have something where people can get at it right at the very least.

576
00:51:14,520 --> 00:51:17,440
But then the actual definition of, of what do you do with that?

577
00:51:17,480 --> 00:51:19,120
I think it is a bit of a phase two.

578
00:51:19,300 --> 00:51:23,440
One of the things I learned, I used to run a data team, um, at Rogers.

579
00:51:23,440 --> 00:51:34,720
We did major, we, we integrated seven different lines of business from cable video stores, the Toronto blue Jays, um, wireless, you know, trying to get customer centricity basically across the company.

580
00:51:34,800 --> 00:51:37,980
And the thing we learned very quickly is you have to, the business has to own its data.

581
00:51:38,160 --> 00:51:50,620
The business has to, and when I say the business, I mean the people that actually, you know, run the, they run their business and they can't just blame it when my data sucks or I'm capturing things.

582
00:51:50,620 --> 00:51:53,780
It's like, you know, your own employees are actually typing in things with typos.

583
00:51:53,920 --> 00:51:57,940
We can help you give you tools to, you know, spell check and stuff, but you have to actually care about this.

584
00:51:58,160 --> 00:52:09,240
So I think that very often with data governance, we've, we've, um, we've kind of overcompensated with data quality problems of the past where, you know, in the sixties, we didn't care about customers.

585
00:52:09,240 --> 00:52:11,680
We cared about accounts or we cared about addresses.

586
00:52:11,680 --> 00:52:15,480
Actually, the funniest thing in the cable business is nobody actually cares about customer.

587
00:52:15,580 --> 00:52:18,260
They care about addresses because the addresses are the persistent thing.

588
00:52:18,360 --> 00:52:19,740
It's where the drop of the cable is.

589
00:52:19,880 --> 00:52:19,940
Right.

590
00:52:20,120 --> 00:52:26,160
And so this notion of customers being the thing that is carried over was like foreign in, in the early two thousands.

591
00:52:26,600 --> 00:52:29,120
So we were like, well, let's never do that again.

592
00:52:29,220 --> 00:52:34,660
Let's overcompensate by putting all these checks on about data and whatnot, which just completely stop progress.

593
00:52:35,020 --> 00:52:39,580
Really it's about, okay, if a business person today doesn't care about that, then we don't care about that.

594
00:52:39,580 --> 00:52:40,520
We don't build that in.

595
00:52:41,000 --> 00:52:43,440
And when we do care about that, we invest in it.

596
00:52:43,920 --> 00:52:49,700
If there is, you know, if there is five different things that disagree, somebody has got to invest in that and say, okay, we're going to now make sure.

597
00:52:49,880 --> 00:52:56,220
And then we'll put a standard in place that is at least light enough to the level of investment they're willing to put in.

598
00:52:56,320 --> 00:53:00,160
Because if you slow everything down, you're angering your peers, right?

599
00:53:00,400 --> 00:53:03,740
That's why it's good to force that on kind of the business side.

600
00:53:03,840 --> 00:53:08,660
And this has been always the challenge with classic IT where it's like the business versus IT.

601
00:53:09,040 --> 00:53:12,680
I think the whole thing about cloud native is that the business and IT are completely together.

602
00:53:12,880 --> 00:53:13,900
They sat to sit together.

603
00:53:14,060 --> 00:53:19,160
If you think of it as throwing it over the wall or all those geeks are going to work on my stuff, it's not going to work.

604
00:53:19,240 --> 00:53:20,020
You're not going to move fast.

605
00:53:20,800 --> 00:53:20,860
Right.

606
00:53:20,960 --> 00:53:23,260
That's why I always hate that designation of business and IT.

607
00:53:23,480 --> 00:53:25,840
Most companies, legal is not the business either.

608
00:53:26,380 --> 00:53:28,000
So like what is the business?

609
00:53:28,100 --> 00:53:28,740
We're all the business.

610
00:53:29,780 --> 00:53:30,260
No, exactly.

611
00:53:30,560 --> 00:53:36,560
And nobody's structured that way, I think, in classic IT sense, unless they're doing like agile projects or whatnot.

612
00:53:36,880 --> 00:53:39,640
And they seem to be more like curiosities, I guess.

613
00:53:39,900 --> 00:53:42,820
But eventually it's going to permeate everything.

614
00:53:42,940 --> 00:53:47,980
And you're already seeing this with what things like Gartner and whatnot are recommending for marketing groups and whatnot,

615
00:53:48,180 --> 00:53:51,020
that they all kind of just correlate the teams together.

616
00:53:51,120 --> 00:53:51,900
They don't separate them.

617
00:53:52,280 --> 00:53:52,520
Sure.

618
00:53:53,040 --> 00:53:53,220
Yeah.

619
00:53:53,480 --> 00:53:53,740
Yeah.

620
00:53:53,740 --> 00:53:54,180
Well, that's great.

621
00:53:54,240 --> 00:53:55,760
Well, hey, thanks so much for being on.

622
00:53:55,980 --> 00:53:57,700
You volunteered.

623
00:53:58,240 --> 00:54:05,020
And I think it was a good choice to volunteer to keep on one of the minor themes in my cattle call.

624
00:54:05,400 --> 00:54:06,260
So that's great.

625
00:54:07,620 --> 00:54:07,980
Yeah.

626
00:54:08,280 --> 00:54:09,800
Well, we'll have to talk some more on these topics.

627
00:54:09,960 --> 00:54:15,220
I mean, there's a few more things I want to delve into with you and other people more.

628
00:54:15,220 --> 00:54:18,340
Like one, what's up with this mapping the business stuff?

629
00:54:18,980 --> 00:54:25,060
And then more on what the standards that get put in are like.

630
00:54:25,400 --> 00:54:35,360
And I like the notion that both you and Richard were starting to talk about where there's sort of like this five-year journey that enterprise architecture is going on.

631
00:54:35,460 --> 00:54:37,640
And we've got to sort out the infrastructure stuff.

632
00:54:38,000 --> 00:54:41,620
And then if you start it early, maybe you're in the middle phase.

633
00:54:41,620 --> 00:54:43,000
But the middle phase is something else.

634
00:54:43,120 --> 00:54:46,680
And who knows what it will sort of look like at more of a steady state of what they do.

635
00:54:46,920 --> 00:54:48,380
But that's been interesting.

636
00:54:48,580 --> 00:54:53,680
So if people want to follow you on Twitter or whatever, I mean, or maybe your blog.

637
00:54:53,840 --> 00:54:59,320
If they want a 404 on their blog, like where can people look you up?

638
00:54:59,880 --> 00:55:04,020
It's kind of like on S3 or on the Wayback Machine basically at this point.

639
00:55:05,260 --> 00:55:09,880
My Twitter is SVRC, which is my initials.

640
00:55:10,120 --> 00:55:15,140
I'm also at StuCharlton.com, which is still kind of up sort of.

641
00:55:16,280 --> 00:55:18,480
It dates back to 10 years ago.

642
00:55:18,720 --> 00:55:25,340
But it's some classic post on REST architecture and whatnot for people that are geeky about those sorts of things.

643
00:55:25,720 --> 00:55:25,760
Yeah.

644
00:55:25,920 --> 00:55:26,080
Yeah.

645
00:55:26,160 --> 00:55:27,840
You must be like me.

646
00:55:27,960 --> 00:55:30,440
You joined Twitter in like 2006 or 2007.

647
00:55:30,820 --> 00:55:31,740
You get such a short name.

648
00:55:32,300 --> 00:55:33,640
But yeah, that makes sense.

649
00:55:33,980 --> 00:55:34,180
Yeah.

650
00:55:34,480 --> 00:55:34,720
Yeah.

651
00:55:34,940 --> 00:55:35,220
All right.

652
00:55:35,260 --> 00:55:36,180
Well, great.

653
00:55:36,260 --> 00:55:38,440
As always, this has been Pivotal Conversations.

654
00:55:38,440 --> 00:55:47,080
If you want to get the most recent episode, if this is the most recent one you're listening to, find the RSS feed to subscribe to and see all the delightful other ones.

655
00:55:47,220 --> 00:55:52,400
Some of them grouped together, like where we talked with actual end users and people and other stuff.

656
00:55:52,480 --> 00:55:56,040
You can go to SoundCloud.com slash Pivotal Conversations.

657
00:55:56,180 --> 00:55:57,380
No space in there or anything.

658
00:55:57,880 --> 00:56:04,080
And every Thursday, we post the full show notes of each episode over at Pivotal.io slash podcast.

659
00:56:04,980 --> 00:56:13,000
And, you know, it's always helpful if you tweet about this in your Twitters or put it in your other social holes like LinkedIn, maybe even a Facebook.

660
00:56:13,000 --> 00:56:16,620
You can tell your junior high friends what you're up to today.

661
00:56:17,000 --> 00:56:20,180
And they'll be like, that person was always really fun at parties.

662
00:56:20,520 --> 00:56:23,180
I see they've maintained that throughout the rest of their life.

663
00:56:23,480 --> 00:56:24,060
Although, I don't know.

664
00:56:24,180 --> 00:56:26,400
Maybe it's your computer club people who follow you.

665
00:56:26,720 --> 00:56:27,340
So, whatever.

666
00:56:27,760 --> 00:56:33,140
But it's always good if you help us get the word out and if you want to write a iTunes review or anything like that.

667
00:56:33,480 --> 00:56:35,200
And with that, we'll see everyone next time.

668
00:56:35,500 --> 00:56:35,920
Bye-bye.