WEBVTT
1
00:00:08.800 --> 00:00:26.209
Myles Brown: Well welcome. Good morning, uh, or good afternoon. Good evening. Wherever you're coming from. Um! It's gonna take a couple of seconds for all the attendees to come in while we're waiting. Uh, this is the fundamentals of cloud native computing. This is a free webinar that exit certified putting on
2
00:00:26.220 --> 00:00:32.900
Myles Brown: with uh with some great help from Morantis. Uh, specifically oriented training, we have Eric Frick here.
3
00:00:33.000 --> 00:00:38.840
Myles Brown: Um. We'll give people a couple more minutes, because I see attendees will wait till it goes off.
4
00:00:40.090 --> 00:00:58.519
Myles Brown: But um, we're waiting. Uh, i'll just mention Exit Certified is A. Is an It Training Company uh mainly North America. But uh, we're one of the largest training companies in North America, and we do a lot of cloud training and cloud native and and related technologies.
5
00:00:58.530 --> 00:01:16.939
Myles Brown: And typically uh, we, you know we partnered with uh Aws or Microsoft Azure or Google Cloud. You know where there's a vendor of note. We partner with that vendor and offer authorized training. But when it comes to a lot of these open source technologies, things like docker and kubernetes
6
00:01:16.950 --> 00:01:34.989
Myles Brown: mit ctl. And you know, anybody can kind of hide, hang a sign and say, we do Kubernetes training, and so at exit certified, we find it. Our goal is to go and find what's the best of breed training out there, and we've been partnered with Morantes for a long time now, and we offer their Cloud native training and also their openstack training one hundred and fifty,
7
00:01:35.000 --> 00:01:44.150
Myles Brown: and today we have Eric Frick here to talk to us a little bit about cloud native computing. Maybe, Eric, you can tell us a little bit about yourself and about Grant us.
8
00:01:45.650 --> 00:02:04.999
Eric Frick: Sure. Um! My name is Eric Frick, and I am a uh uh, an instructor here at Morantis and I. I specialize in the Cloud native technology stack. So and over the years I've done a lot of I've probably had every role in an it team. You can imagine. I started as a programmer worked as a
9
00:02:05.510 --> 00:02:13.929
Eric Frick: a uh to the software architect, to software development manager and finally a senior. It executive Over the last ten years I've been doing a lot of education work
10
00:02:13.940 --> 00:02:28.849
Eric Frick: uh teaching both the college level and and commercial uh instructions. So Um and Marantis is is a uh, a Cloud Native Computing company. We offer consulting services. We have also developed a
11
00:02:29.510 --> 00:02:38.999
Eric Frick: Alex. They are built to open stack and kubernetes, and then finally we offer training around both uh cloud native technologies, openstack, and also our internal products,
12
00:02:39.730 --> 00:02:44.489
Myles Brown: all right, and the I guess maybe tell us what we're going to talk about today,
13
00:02:45.470 --> 00:02:52.590
Eric Frick: all right. So here's kind of the outline of of where we're headed for this. We're going to talk about kind of the beginnings or the
14
00:02:53.360 --> 00:03:08.179
Eric Frick: origins of the way back to the cloud some of the common challenges that they face, and then we we'll talk about, you know, once you get there, where do you go next? And the basics of cloud native computing, and what its advantages, and and maybe some of the disadvantages.
15
00:03:08.190 --> 00:03:16.139
Eric Frick: And What does it take to get there? The The skills needed to build and deploy cloud native architectures, you know. What do you really need to get there?
16
00:03:17.580 --> 00:03:23.160
Eric Frick: And then with some of the training that's offered by Marancis around Cloud Native technologies
17
00:03:23.180 --> 00:03:34.220
Myles Brown: All right, We said you'd start with some of the ways. Organizations might migrate to the cloud. So maybe you can tell us about some typical cloud migrations, you know. You know, as a consultancy. You must see these quite a bit.
18
00:03:34.420 --> 00:03:40.459
Eric Frick: Yeah, you know, I think typically um, especially a few years ago, maybe
19
00:03:41.170 --> 00:03:46.080
Eric Frick: less of that. Now, we're very skeptical in the cloud, especially companies that you
20
00:03:46.090 --> 00:04:04.419
Eric Frick: Oh, you know, companies like banks and financial houses, We're very skeptical about moving to the cloud, so they would start typically with a proof of concept like something, something a simple use case where they could get a win uh something like cloud storage, or maybe moving as software development environments. There things that were kind of a an e
21
00:04:05.120 --> 00:04:15.370
Eric Frick: easy when it's kind of moving up the scale. From that, Maybe the next step might be to do a lift and shift of a simple application. We're not really changing the application much
22
00:04:15.380 --> 00:04:27.830
Eric Frick: mit ctl, and you know just kind of moving it as as is without re-engineering it and doing the minimal amount of work that you can to it, to move it to the cloud again, to get another kind of wind and start building some momentum around the cloud one hundred and fifty.
23
00:04:29.310 --> 00:04:38.779
Eric Frick: But then I kind of once you get to that point is now what you know. Where do we move next we've We've got the low hanging fruit. We've got some wins,
24
00:04:38.790 --> 00:04:51.900
Eric Frick: you know. What are the next things that that we're going to take on, and you know some of the things that you know you run into our mission critical applications. Well, now, I've moved something simple. How am I going to move? Something that I run my business so one hundred and fifty
25
00:04:52.860 --> 00:04:59.010
Eric Frick: on, and then also legacy, monolith applications, and we'll talk a little bit more about monolith applications. The
26
00:04:59.030 --> 00:05:16.109
Eric Frick: and also then with with those more complex projects, how do you lay out a migration strategy? So you continue to get wins without putting your your business at risk. And finally, how do you really take advantage of all the services that the cloud offers, and all the
27
00:05:16.760 --> 00:05:23.910
Eric Frick: true advantage? And just? You know the simple use cases. So that's kind of the phases of migration that we see with our our customers.
28
00:05:25.120 --> 00:05:42.489
Myles Brown: Yeah, I think I see that a lot on the training side, as well, you know. Say uh customers that came five years ago just to take some initial cloud training, took an aws class or an azure class, and then, you know, they come back later, saying, Hey, we want to get more out of the cloud. We want to use it for a lot more stuff,
29
00:05:42.910 --> 00:05:51.690
Myles Brown: what we need a new strategy. So what what are some of the common challenges that these organizations face when they're when they're doing that cloud migration.
30
00:05:52.920 --> 00:05:54.840
Eric Frick: Well, I I I think
31
00:05:55.600 --> 00:06:03.700
Eric Frick: it's a double-edged sword with the cloud. So once you've kind of done that that proof of concept and people figure out Okay, now, it's.
32
00:06:05.060 --> 00:06:23.009
Eric Frick: I don't have to procurement necessarily now to buy hardware, and I have to have things shipped in and installed in the data center. So I can. I can. I can provision resources, you know, at light speed right before. It was a a process, you know, really, maybe even a complex process in a in a big organization.
33
00:06:23.020 --> 00:06:27.449
Eric Frick: So now maybe the challenge is, It's too easy to provision
34
00:06:28.350 --> 00:06:47.620
Eric Frick: forces in the term cloud sprawl on here. Um, I think It's a common problem that now, all of a sudden, everybody in the organization is building all kinds of dev and test servers, and all of a sudden, the next monthly Bill comes up, and the boss says, Oh, my God, you know what is all this stuff we're paying for, so so that that
35
00:06:47.630 --> 00:06:49.449
Eric Frick: developing um,
36
00:06:49.660 --> 00:06:51.269
Eric Frick: you know, new ways
37
00:06:52.180 --> 00:07:01.179
Eric Frick: just to kind of man envisioning resources and controlling expenses. That's one big challenge. Um, I think the other challenge, too, is is Okay, I've got.
38
00:07:01.190 --> 00:07:15.109
Eric Frick: I've got storage up there. I've got some simple client server applications up there. I've moved a bunch of, and maybe I've even bought some Sas products out there to support the organization. But now there's those mission critical applications where
39
00:07:16.300 --> 00:07:31.690
Eric Frick: can really get out of migrating those to the cloud. So So How do? How do I put my arms around those, and how do I tackle those? And then the other thing is getting the right training for the staff, so that they can take on those product projects that they have the
40
00:07:31.700 --> 00:07:39.250
Eric Frick: the the background. A lot of cloud development is radically different than traditional development, especially
41
00:07:40.170 --> 00:08:03.430
Eric Frick: so if you're in a company frame environment where things were very siloed. Um! And the cloud things are very highly distributed, and understanding kind of those concepts, and also that the the products and tools that are available, for example, in aws, or azure, or uh open source products. How do I take advantage of those. And really the the training comes to be key with those. And the last one i'll talk about is monologue
42
00:08:04.120 --> 00:08:21.299
Eric Frick: with applicating. Now I I think that's a discussion in and of itself. And um, you know, these large old business critical applications, and almost every organization I've ever worked for had the application where nobody wanted to touch it right. If you touched it you broke it.
43
00:08:21.310 --> 00:08:27.310
Eric Frick: You're in all kinds of trouble. So everyone was just didn't want to even breathe on it because you know that thing had been wrong
44
00:08:28.100 --> 00:08:29.450
Eric Frick: running for years.
45
00:08:30.210 --> 00:08:33.980
Myles Brown: Excellent! So um, I guess
46
00:08:34.039 --> 00:08:45.499
Myles Brown: a lot of organizations are in that kind of move where they They've been in the cloud sort of for a while, and now they're trying to get some cloud maturity, so maybe you can talk to like what it
47
00:08:45.680 --> 00:08:49.619
Myles Brown: does that mean? You know. How do you say we've got a mature cloud strategy?
48
00:08:50.010 --> 00:08:50.880
Eric Frick: Well,
49
00:08:51.930 --> 00:09:11.559
Eric Frick: I I think initially, you know, like we say, we start with that proof of concept. But then, how do you start building a roadmap? For to to you know, for example, if you're going all in with the cloud. Uh, if you want to develop a multi cloud uh strategy or a hybrid cloud strategy, So how do you? How do you get the
50
00:09:11.760 --> 00:09:14.849
Eric Frick: both the training for
51
00:09:15.990 --> 00:09:38.910
Eric Frick: development and operational uh processes as well as the financial process that I just talked about. How do you have controls on provisioning resources and operational spend. How do you have the right controls for uh operations to be releasing things into the cloud which can be an entire Hayden, for example. Then maybe having uh, you know, traditional data center harder.
52
00:09:39.670 --> 00:09:57.039
Eric Frick: We're based resources. And then also the the development and architectural aspects of that. So you know, there there's really kind of training across the board uh as well as training for management, so that they can understand what the challenges they'll be facing as they move up the scale with more complexity.
53
00:09:57.050 --> 00:10:00.000
Eric Frick: So it's a blending of developing
54
00:10:00.140 --> 00:10:02.519
Eric Frick: um, getting the right
55
00:10:03.600 --> 00:10:08.950
Eric Frick: resources at a time to move your organization forward so that you can be more agile
56
00:10:08.960 --> 00:10:26.590
Eric Frick: to, to adopt quicker to a changing environment, to be more robust, so that you don't have maybe a a problematic applications, extended downtime those kinds of things that you had, maybe in a data center where um you know, you're supporting a
57
00:10:27.420 --> 00:10:42.850
Eric Frick: a lot of the hard sources. And then also the architectural aspect of that. How do I fit all that together and tie that into a um? You know cohesive strategy that really allows you to attack. You know your core business problems and apply the right technology at the right time.
58
00:10:43.680 --> 00:10:44.680
Excellent.
59
00:10:44.960 --> 00:10:52.390
Myles Brown: Um. Well, you mentioned a little bit about monolithic applications. Maybe you can talk a little bit more about that. Some of the challenges they present.
60
00:10:54.130 --> 00:10:56.300
Eric Frick: Sure Um,
61
00:10:56.520 --> 00:11:14.479
Eric Frick: I think if anybody's worked in any organization of any size uh you come across these applications that you know they might not be mainframe based, but but they could. They certainly could be um, and they represent a large single code base that's been built up over
62
00:11:15.220 --> 00:11:30.470
Eric Frick: for years, and it's probably been built components that are maybe not supported anymore, or they've they've gone out of the of of life cycle. They might even be running on operating systems that are no longer, you know, in current support. So you might be paying extended maintenance for these things.
63
00:11:30.480 --> 00:11:38.120
Eric Frick: Um! It just becomes more and more painful the longer that these systems exist, they become more and more expensive to
64
00:11:39.110 --> 00:12:01.750
Eric Frick: support, and also become a a a huge business risk. Um, and that the longer these systems live in their life cycle uh, the more risk that's incurred that supporting them just becomes a nightmare. Uh, you might might also be tied to a particular vendor, or even a particular person. Um, you know you might
65
00:12:03.130 --> 00:12:10.879
Eric Frick: have an employee there that you have to keep him on retainer, he or she on retainer, because they're the only person who has any business knowledge left
66
00:12:10.890 --> 00:12:26.160
Eric Frick: of of how this system works. So uh, you know, it might be the case right now. If you're you're still an active cobal program, or you might have a huge market for uh supporting systems that still support critical business needs. But this is a tricky one
67
00:12:26.920 --> 00:12:42.580
Eric Frick: on because um! These systems are often very tightly coupled in in meaning that if you make a change in one part of the system, it may ripple through and have drastic effects all the way through the system. That's why people are hesitant to touch these things, and
68
00:12:42.660 --> 00:12:49.750
Eric Frick: and more often than not these, these applications are involved in mission critical functions. The the
69
00:12:50.800 --> 00:13:08.000
Eric Frick: business can, and without this application. But yet it's been propped up for years, you know, being as is. And so these in particular present a lot of challenges for organizations, and the longer that they've existed the the worst those challenges become.
70
00:13:08.960 --> 00:13:19.560
Myles Brown: Yeah. So I guess I guess the solution is to you know, tackle it one piece at a time, and maybe try and get to that cloud native architecture. Maybe you can tell us a little bit about that.
71
00:13:20.770 --> 00:13:22.060
Eric Frick: Yeah. So
72
00:13:22.390 --> 00:13:30.670
Eric Frick: So I I I think, what a lot of organizations do That's a good point is to try to take one piece at a time. If you can decompose these
73
00:13:30.770 --> 00:13:37.389
Eric Frick: highly complex applications into smaller pieces, or maybe even replace it one part at a time.
74
00:13:38.770 --> 00:13:54.879
Eric Frick: That's kind of the method rather than the you know, the kind of the grand slam. I'm going to just take a couple of years off and rewrite this thing and then launch it. I think most organizations have found that that that risk is just simply not acceptable, and and it puts a such a stress on
75
00:13:54.910 --> 00:14:01.849
Eric Frick: development teams and testing teams and operations to be able to to do that kind of grand slam,
76
00:14:02.550 --> 00:14:23.409
Eric Frick: that if you can decompose those those systems into smaller pieces, then you can start moving towards a more flexible architecture, and and the more flexible architecture we're talking about. Here is a cloud native architecture, and so, rather than what we described earlier, of having a
77
00:14:23.420 --> 00:14:25.440
Eric Frick: lift and shift architecture.
78
00:14:26.420 --> 00:14:39.589
Eric Frick: We're just taking the existence. And you, said i'm going to put it on virtual servers in aws or azure or gcp. I'm going to move the database in the same way, and i'm not going to make any changes to the code. I'm going to move it, as is when a cloud. Native approach
79
00:14:39.660 --> 00:14:49.100
Eric Frick: is a little bit different in that You're going to think more holistically about the application and say, Are there specific services offered by my provider
80
00:14:50.300 --> 00:14:57.560
Eric Frick: by aws she azure that I can really use to take this application to the next level, and and in
81
00:14:58.120 --> 00:15:13.279
Eric Frick: kind of the goals in mind is that you can maybe minimize some complexity with an application. You can improve it, scale dramatically and and optimize the performance of things that maybe were very sluggish on older systems or client server architecture.
82
00:15:14.120 --> 00:15:19.600
Eric Frick: There's we're buckling onto the load. If you can move to kind of these more cloud native approaches, you can build
83
00:15:19.700 --> 00:15:25.189
Eric Frick: highly responsive systems that scale up and down easily. Um,
84
00:15:25.390 --> 00:15:33.970
Eric Frick: but they're engineered with the cloud in mind and not not moved, you know, kind of as is. But the the whole kind of purpose of those are we thought,
85
00:15:34.320 --> 00:15:35.360
Myles Brown: Yeah,
86
00:15:35.400 --> 00:15:55.719
Myles Brown: Well, that that sounds great. I guess. Maybe the question is, you know, where do those advantages come from? What? What are maybe some of drill down into that a little bit? How does that happen with Cloud native,
87
00:15:55.730 --> 00:16:00.849
Eric Frick: that that we will pay gigantic dividends, and the in the first one is the app
88
00:16:01.840 --> 00:16:17.959
Eric Frick: applications are less built and can provide greater liability. So things like fail over um instead of having, uh, you know what would happen a lot of my career. The phone would ring in the middle of the night like, Hey, It's broken, You you know the the alarm bell went off right, and and you gotta
89
00:16:17.970 --> 00:16:24.910
Eric Frick: it, particularly if it's a mission critical system. You got to get people in the middle of the night and fix it, or on weekends or holidays. And believe me, I've
90
00:16:25.760 --> 00:16:39.189
Eric Frick: spent a few holidays adding things back together. Um! So you want to have applications that are are really uh, they can more self- healing that can can gracefully recover from from failures. And
91
00:16:39.200 --> 00:16:48.550
Eric Frick: and the other thing is is application scale. Um, I worked uh in my career on a tax filing system. Well guess what tax filing day was
92
00:16:49.580 --> 00:16:56.249
Eric Frick: like. It was a nightmare that, you know, ninety percent of our traffic came on that around those those tax filing deadlines,
93
00:16:56.260 --> 00:17:12.680
Eric Frick: and it so applications can scale up and down with with very little support or uh operational intervention is is a real thing. And um! There are so many systems that have seasonal demands on them. You know we're coming up on a big one.
94
00:17:13.630 --> 00:17:31.790
Eric Frick: So anybody who has an an online website, and and it's doing those kinds of transactions right usage will spike through the roof uh on well, hopefully, for those those people selling things will their their usage will go through the roof, but applications that can scale up and down with little or or no support, and then
95
00:17:32.010 --> 00:17:34.920
Eric Frick: also, not having a long um
96
00:17:37.280 --> 00:17:57.209
Eric Frick: active, you know, drawn out application cycle where you know some some large organizations are saying, I'm only going to really software twice a year because it's so painful. Um, you know, you want to get to the point where applications are much easier to deploy that that becomes a non-event, so that you know that application deployments are going to be sound
97
00:17:57.220 --> 00:18:00.439
Eric Frick: and they're not going to be rolling changes back as soon
98
00:18:01.150 --> 00:18:18.350
Eric Frick: as you put them out in the next day. Um, you know, or or the worst possible scenario right? You. You release a bunch of changes on Friday everyone goes home, and the system breaks for the weekend. So you really want to have systems that are easier to deploy and maintain. Um, so that again that
99
00:18:18.570 --> 00:18:24.470
Eric Frick: you you can put changes in in a seamless way and take the risk way
100
00:18:25.090 --> 00:18:43.010
Eric Frick: down for the organization and the end result of that. That all sounds great, you know, from a like a devops guy or a software development manager. My blood pressure's gone down. Life is easier. These systems are less brittle. They don't break as much they can. They can scale, and they're easier to deploy. But so what you know. So what from a business sense,
101
00:18:43.020 --> 00:18:48.359
Eric Frick: then it allows an organization to really be agile and adapt to changing
102
00:18:48.980 --> 00:19:04.190
Eric Frick: business needs. I think, behind the curve the organization can really be responsive to those changing business needs, and God knows the business, you know. Climate, right now is is chaotic at best, and so, being able to respond quickly to changes,
103
00:19:04.500 --> 00:19:12.220
Eric Frick: It's not, I think, a a a luxury anymore. It's a necessity for organizations to be able to respond
104
00:19:12.930 --> 00:19:25.340
Eric Frick: rapidly to change conditions. So all these cloud native things, all baked together, really allow our organization to be much more responsive, and uh, much more relevant really, in the marketplace,
105
00:19:26.060 --> 00:19:40.549
Myles Brown: it's th this is great. Um, I guess I guess what organizations that aren't there yet are asking is sort of. What do we have to do to set the table to be able to really jump into cloud. Native. So what are? What are some of the prerequisites? Maybe
106
00:19:41.670 --> 00:19:59.770
Eric Frick: so. So I think there's a number of things in in like everything. There's no no free lunch. You can't just wave a magic one and all the said Wow, Cloud native poof! You know. I'm here, and it's Nirvana. Um training is is the first aspect, and you know this is a training related call, but
107
00:20:00.930 --> 00:20:17.440
Eric Frick: you know to be tried here. But you need training in a couple of different areas. One is, if you're using a public cloud provider like Aws or as your Gcp. You need to have the kind of the baseline training to, so that you you're proficient with your cloud provider. And then the next one
108
00:20:17.450 --> 00:20:22.139
Eric Frick: is how to design highly distributed systems. And uh,
109
00:20:24.910 --> 00:20:42.969
Eric Frick: to truly take out these these architectures that are self healing, that that scale easily. They are highly distributed, and they have lots of different resources. And so, uh understanding how to design and support those kind of highly distributed systems is, is is a, you know, a prerequisite of of
110
00:20:42.980 --> 00:20:47.560
Eric Frick: implementing cloud native architectures, and then the next one is understanding
111
00:20:48.600 --> 00:20:59.430
Eric Frick: capabilities of systems with containers. So Docker and kubernetes, and and those types of systems and ha! What what types of advantages to those systems um
112
00:21:00.230 --> 00:21:11.450
Eric Frick: do the systems allow for, and how? How? How can you start Fielding? Some proof of concept around containerized systems and and and do it, and
113
00:21:12.390 --> 00:21:22.160
Eric Frick: kind of risky birthday. And so Kubernetes is an unbelievable system, you know, originally developed by Google, their their their board system
114
00:21:22.170 --> 00:21:35.670
Eric Frick: and and Google use that technology to to develop systems that literally have billions of users Uh uh, Gmail uses this technology, you know they have. Well, they I think, last I read: Google has seven systems that have
115
00:21:36.290 --> 00:21:48.080
Eric Frick: of over one users, you know. That's where the beat. That's incredible. I mean, that was never ever thought of as a capability. Probably even, you know, five, ten years ago that have systems in such massive scale,
116
00:21:48.400 --> 00:21:59.489
Eric Frick: but with something like kubernetes there is a learning curve. You have to understand it. It's very robust, highly capable software, but it probably employs some some technique
117
00:22:00.260 --> 00:22:20.180
Eric Frick: links and tools that are. Wouldn't be um kind of mainstream to somebody who worked in a client server environment. For example, it's just a different way of thinking about software. And so, having some training to understand the capabilities of Kubernetes getting some hands on like, so that the light bulb goes off and say, Ah, I get it um!
118
00:22:20.350 --> 00:22:23.260
Eric Frick: And then there's kind of some devops, Con.
119
00:22:24.240 --> 00:22:42.750
Eric Frick: It's kind of built rough. If to really take advantage of this, excuse me, you'll probably need uh some additional tools, something like Jenkins to to do um uh continuous integration, continuous delivery pipelines, so that when you do have those changes in what I talked about earlier
120
00:22:43.350 --> 00:22:47.329
Eric Frick: you need to do an application Deployment? That's that's repeatable,
121
00:22:48.080 --> 00:23:04.120
Eric Frick: cool and robust. And so tools like Jenkins can help you get there with those things. I've listed some others there, chef and puppet, or maybe even cloud specific tools. If you're using aws like code, build, code, deploy, or code pipeline, they they have a whole suite of tools there. But
122
00:23:04.590 --> 00:23:10.919
Eric Frick: so I I think kind of the prerequisite again to kind of summarize for for
123
00:23:11.940 --> 00:23:18.210
Eric Frick: cloud Native, are you understanding your cloud platform that you're using and having having a mastery of that,
124
00:23:18.840 --> 00:23:33.579
Eric Frick: the capability of understanding these distributed architectures, understanding containerization, and what it can bring to your application. And then how do I operationalize those containers? Maybe with uses of tools like things like Jenkins.
125
00:23:34.110 --> 00:23:49.370
Myles Brown: Right? Well, that's great, I mean at exit certified. We we obviously offer, you know, uh cloud training from all the major vendors aws as your Google Cloud Oracle Cloud. Um. And you know from that side
126
00:23:49.380 --> 00:24:18.559
Myles Brown: we see that you know you. You learn about the the the capabilities of the of the cloud itself. Now all of these cloud vendors have some sort of Kubernetes managed service, you know, so in Aws is called eks the elastic Kubernetes service Azure has Aks uh at Google, the Mg. You know. So they all have some sort of a manage, and and even if they have a class on it. What we find is that it doesn't teach them the basics of containers and kubernetes. It just says,
127
00:24:18.570 --> 00:24:21.060
Myles Brown: What can we do for your kubernetes
128
00:24:21.070 --> 00:24:51.059
Myles Brown: uh deployment, you know, like they'll basically take care of the control plane a little bit right? And so what we found was that, hey? There's there's a big hole here in that official vendors curriculum where people need to learn about containers and kubernetes. And um, you know. So that's where really we we partnered with Marantes uh, and and Marantes has great uh instructor led training, and and we have a a pretty robust public schedule. We also do private classes, if you've
129
00:24:51.070 --> 00:25:03.170
Myles Brown: like a group of people. Um. But uh also on demand. And so it's probably take a worth taking a look, maybe specifically, at the cloud native technologies. And
130
00:25:03.180 --> 00:25:11.440
Myles Brown: really the first. The first class that you might be interested in, I would say, is, is this sort of half day intro to cloud native computing
131
00:25:11.450 --> 00:25:28.960
Myles Brown: sort of the perfect follow on to this Webinar. In fact. Um! We'll see that. Uh, we have a We have a a code, so that the the first fifty people to get in there can use that code and get that on demand uh for free, and that'll get you in demand.
132
00:25:30.260 --> 00:25:58.190
Myles Brown: This is on demand system, if you like. Then you can chop around and see what other classes you're interested in, that The normal progression would be, probably to go to the Cm. One hundred, which is the one day docker containerization essentials class. And then from there, maybe into uh, either the Kubernetes application essentials. Or maybe if you're using docker swarm right? So uh when Docker first came out Um, they said, Well, maybe we need a uh a sort of an orchestration tool. And so they built docker swarm.
133
00:25:58.200 --> 00:26:13.830
Myles Brown: But then, like you said, some other opportunities popped up uh kubernetes came from Google uh Aws started to build their own, called Ecs. But you know over time what happened was it looked like Kubernetes kind of became the defective standard.
134
00:26:13.840 --> 00:26:35.919
Myles Brown: And so that's what we see, is, you know, the most popular orchestration tool these days. And so we've got a whole sort of progression here of classes. Now there's some additional options that aren't necessarily uh these sort of uh uh vendor agnostic, just learning the basics of uh docker and kubernetes. Maybe you could talk to these a little bit. These are some special miraculous glasses.
135
00:26:36.240 --> 00:26:45.790
Eric Frick: Sure. Um, you know, like you mentioned the the the courses list on the left are vendor agnostic. So our Kubernetes boot camp really is what you just
136
00:26:46.930 --> 00:26:59.799
Eric Frick: describe learning the block and tackling the basics of kubernetes, and how you can build from the ground up, from containers on up through orchestration with kubernetes, and we have hands on labs that that teach you that in in a you know, generic Kubernetes environment
137
00:26:59.810 --> 00:27:10.059
Eric Frick: we also were also a product company that I mentioned earlier. So we have built our own products around uh Kubernetes. We have our Rantes container cloud that allows you to
138
00:27:10.760 --> 00:27:16.940
Eric Frick: to uh manage kubernetes over multiple environments, so you can manage things through uh
139
00:27:16.950 --> 00:27:33.919
Eric Frick: uh on premise or bare metal aws uh azure just was released. So you can manage all those from a single footprint, you know, in the cloud, so that that's a an an interesting product. And so we have the product related training around that we to offer a
140
00:27:34.580 --> 00:27:57.519
Eric Frick: yeah uh uh uh rancis Kubernetes engine. We called Mke now, so we have training around that as well, and we have a secure registry that really allows for the the safe uh storage and delivery and integration into a Ci cd pipeline of um of containers. And so uh it. It's it's Marant to secure registry, we call it
141
00:27:58.600 --> 00:28:07.660
Eric Frick: uh Nsr. Now we have a course around that as well, and how to integrate it into your existing pipelines we have uh courses around um. Rance is openstack.
142
00:28:07.830 --> 00:28:21.550
Eric Frick: So my uh uh fellow trainer uh is is head of that that uh a set of courses, so i'm not as familiar with the hope and stack courses. But we have a wealth of courses in booting two hundred and fifty
143
00:28:22.310 --> 00:28:45.539
Eric Frick: amps around. Openstack. Um all the the the next bullet down talks about boot camps, and so these these classes can be organized into like a one week boot camp. For example, we have lots of flexibility around that. I'm. Sure you guys have have offered a a ton of those, and then we we proctor some industry certifications as well. So those are listed down below. So that's kind of the highlights of on the right, the product
144
00:28:46.200 --> 00:28:47.800
as the course.
145
00:28:48.230 --> 00:29:18.089
Myles Brown: Thanks. Um. So yeah, mentioning those boot camps. There's there's sort of two, five day boot camps that we we generally see are very popular. Uh they both kind of start off the same with the first three days being uh, you know, the the basics of docker and the basics of Kubernetes. But then, you know, the last two days depends on whether you're more of a developer or more of an operations person. And so that's why we have these two uh bumped up kind of boot camps, the Cn. Two hundred and fifty-one is the cloud Native operations, Boot, Camp,
146
00:29:18.100 --> 00:29:26.409
Myles Brown: Cn, two hundred and fifty. Two. Is the Cloud Native Development Book, and So that's that's sort of our two biggest sellers, I would say.
147
00:29:26.420 --> 00:29:46.999
Myles Brown: Um. And when we schedule these classes we schedule them as a five day class, but Also, you can just take the one or the two day classes, you know. Um, you know, in in the middle of that, if if you've already taken the one, and you want to come back for the the two day a later date. You know we we schedule them sort of concurrently, so you can do that,
148
00:29:47.010 --> 00:29:48.200
Myles Brown: and there's
149
00:29:48.600 --> 00:29:57.249
Myles Brown: some advance Kubernetes and the Kubernetes security. They'll get you ready for the cks. You know. These are some very prized industry certifications
150
00:29:57.360 --> 00:30:03.699
Myles Brown: Now I mentioned that we would, we would offer
151
00:30:03.850 --> 00:30:12.679
Myles Brown: sort of a voucher, so you could redeem for a free cn fifty. The introduction to Cloud need, of course, This is normally a two hundred and ninety nine dollar value.
152
00:30:12.690 --> 00:30:31.270
Myles Brown: And uh, I think that uh, yeah, Hillary, you put it into the chat. So there's a link there you You should also receive an email. You're you're gonna get a recording of this. Everybody who registered will get a recording of this uh uh Webinar, but you'll also get an email that has, you know, these links. Um. So that you can. You can go,
153
00:30:31.400 --> 00:30:54.279
Myles Brown: go and do that. Now, this is only available to the first fifty people to redeem. So if you're here, live you've got a a good head. Start on the people who didn't watch, and we'll. Uh, we'll just watch the recording, maybe on Monday. So so you may want to go in and redeem that code. Um, So it's a Ecc. And Webinar. And uh, you know, like I said, that that link is the uh.
154
00:30:55.030 --> 00:30:59.659
Myles Brown: It's a mirantis dot com link that that Hillary put in the chat.
155
00:31:00.170 --> 00:31:30.030
Myles Brown: So that's that's a a good place to go if you want more. Just sort of broad on cloud. Native um, if you're already ready to jump right into uh one of the deeper technical classes. And and you're looking for instructor lead training. You know that's that's really uh it's certified bread butter. Um We We have a pretty robust public schedule, and starting next week we have our winter promotion, which is basically it's like a hundred dollars off per day.
156
00:31:30.040 --> 00:31:43.839
Myles Brown: So if you take a five day day class. It's a five hundred dollars off, so it's a pretty good promotion. Um! I don't think you can use it today. It doesn't start till the twenty first, but that's that's when it goes live. So you know, if you're looking to
157
00:31:44.080 --> 00:32:02.580
Myles Brown: book something uh in the in the next few weeks you should be able to get that uh that one hundred dollars per day off. Uh, we also will give you five hundred days off of five hundred dollars off for uh a private training class as well. And so the private training, you know, Typically, if people have, maybe
158
00:32:02.650 --> 00:32:25.589
Myles Brown: at least four or five people, you know it's probably. Uh, if you have more than that, if you have ten, twelve people, then it becomes really cost effective to have a session just for your team. Then you can also kind of look at the outline and say, Hey, maybe maybe we want more of this less of this, you know you could customize things a little bit. You can also customize the timing. You know our public classes. We usually run,
159
00:32:25.600 --> 00:32:44.489
Myles Brown: say nine to five on Eastern time. Sometimes we'll run them on Pacific time. Um, but but you know, if you got a two day class and you want to split it over four half days or something. You know we're very amiable to to any of those kinds of things. So if you do want to talk about instructor led training.
160
00:32:44.630 --> 00:33:04.769
Myles Brown: You can certainly reach out um, you know, if you just go to exit certified dot com you'll see plenty on there. Uh but um, you know specifically uh any Moreantis classes, you know. Even jump into the chat on there, and they'll They'll get you to somebody. If you want to email. You can. You can send it out to this Edu Customer
161
00:33:04.780 --> 00:33:14.319
Myles Brown: mit ctl and experience at tech data dot com uh that'll get to. You know somebody in our marketing team that'll get it to the right salesperson. I'm sure One hundred and fifty,
162
00:33:14.330 --> 00:33:33.710
Myles Brown: I guess the uh the other thing we have is we we've got plenty of time if there's any questions. So we uh we didn't have the chat open, but the Q. A. A. Box is open, and so I think we have a couple of questions. Um, maybe, Hillary, if you can. Uh, you can find any of those questions and maybe ask them for us.
163
00:33:33.720 --> 00:33:52.330
ExitCertified: Eric and Eric will probably answer rather than me. Yeah. So I don't see any questions coming in right now. But to kind of just get things started. I think we can do some um couple of questions here. So, Eric, what do you think would be the single best, biggest challenge in migrating a monolith application to the cloud
164
00:33:53.270 --> 00:33:55.419
Eric Frick: A good question. Um.
165
00:33:55.600 --> 00:33:57.859
Eric Frick: So so, without a doubt,
166
00:33:57.880 --> 00:34:04.239
Eric Frick: the biggest challenge that that I've seen through my career, and I've dealt with plenty of monoliths is
167
00:34:04.250 --> 00:34:21.880
Eric Frick: is really that uh institutional knowledge. You know. How does this thing actually really work? You know. I think a lot of times it's just a black box kind of thing, and people stare at it like I don't know how it does it, but it just does it. Uh you know that, and that's a scary thing, but it It takes really
168
00:34:21.889 --> 00:34:34.409
Eric Frick: a lot of work to for people to kind of roll up their sleeves. And then, you know, reverse engineer um from the code down. What what does this thing really do, and and how does it do it? And so
169
00:34:34.620 --> 00:34:40.699
Eric Frick: so that whole institutional knowledge that the really kind of to begin the the journey of um,
170
00:34:40.810 --> 00:34:54.119
Eric Frick: you know. Decomposing a big monolith like that is reverse engineering business requirements out of it. So you know how. How, What does this thing actually do, and what does it touch? You know what are all the interface points, and that that's
171
00:34:54.130 --> 00:35:12.149
Eric Frick: sometimes as you start digging through You're like, Wow! I didn't know it. It did this. Um, you know. I didn't have any idea to had this interface that it existed So so I think that's That's by far. The biggest problem is is getting that institutional knowledge back. You know most of the time people that have worked on. These things have moved on
172
00:35:12.160 --> 00:35:22.400
Eric Frick: mit ctl, and they've retired or moved on to other companies, and they're they're long gone, and so there's nobody left to to really kind of uh fill that void of how does this thing work? So I think to me that's the biggest challenge, one hundred and fifty.
173
00:35:23.160 --> 00:35:29.639
ExitCertified: Okay? And then, in your opinion, is containerization a great strategy for all applications.
174
00:35:30.800 --> 00:35:34.860
Eric Frick: So so no, sadly no, uh!
175
00:35:35.460 --> 00:35:48.350
Eric Frick: I love containers and systems, but you know there's some complexity there, and so not all applications are are suited for that level of complexity. Um. And and also
176
00:35:48.400 --> 00:35:56.310
Eric Frick: not all applications have the operational needs of being, you know, highly resilient, highly redundant, highly available.
177
00:35:57.540 --> 00:36:12.530
Eric Frick: Um, So it's really. You know more of a case by case basis to apply like, What am I trying to get to what? What's the the criticality of this system? Um, you know what are the what are the real operational requirements? And a lot of times. Um,
178
00:36:12.580 --> 00:36:17.930
Eric Frick: you know. Sometimes you'll talk to a business user or somebody who's one of the sponsors, and they'll say,
179
00:36:18.910 --> 00:36:28.340
Eric Frick: Oh, yeah, this application absolutely critical. And then you start drilling down with them on. Well, does it need around the weekends? Well, now, it's mostly a nine to five thing.
180
00:36:28.420 --> 00:36:39.659
Eric Frick: So so I think really kind of uh. Those are the those are some of the thoughts in mind of like what? What really is a mission critical system. And what am I trying to get to? Uh
181
00:36:40.590 --> 00:36:45.800
Eric Frick: so so definitely not as i'm sorry, or uh the candidates for that kind of architecture.
182
00:36:45.940 --> 00:36:52.160
Myles Brown: Yeah, I think that's a good point. I mean like anything in architecture. There's some trade-offs, right? And so
183
00:36:52.490 --> 00:37:06.519
Myles Brown: you're trading off. Okay, a bit of a steep learning curve and some complexity. But you're getting a lot out of it. But do you need that thing or not? I guess, really what it comes down to? Um. But we have another question is
184
00:37:06.940 --> 00:37:12.539
Myles Brown: there can amount of hands-on built into the training I need to walk away with the skill I can use right away. The
185
00:37:13.940 --> 00:37:23.080
Eric Frick: absolutely um. As a matter of fact, this week I'm. I'm recording lab walkthrough videos for one of our courses. So
186
00:37:24.030 --> 00:37:42.770
Eric Frick: we use a uh environment as our our uh lab environment, and our courses are designed to be sixty percent hands on. So uh, it's not just me or one of my colleagues droning on about lectures. Um, We do have a brief lecture, but it introduces the concepts that are reinforced in the lab. And so
187
00:37:42.780 --> 00:37:44.959
Eric Frick: uh, we have a very robust lab
188
00:37:45.740 --> 00:38:02.210
Eric Frick: environment. So with our training. Um, myself, or one of our other instructors will help people if they get stuck on the labs. We have the capability of of uh shadowing their session in our lab environment and fixing a typos and problems and and helping guide them through. But
189
00:38:02.220 --> 00:38:06.740
Eric Frick: yeah, with this type of technology in particular hands-on
190
00:38:07.440 --> 00:38:17.480
Eric Frick: on this critical. You really have to touch and do this stuff it because the light bulb won't. Go off in your head until you've actually seen it work. And you're like, Okay, Yeah. Now I get it. I understand. And
191
00:38:17.490 --> 00:38:28.200
Eric Frick: also, you know, if you're studying for a certification exam more and more certs are moving to practical certifications where it's not just a multiple
192
00:38:29.160 --> 00:38:44.620
Eric Frick: voice. Of course you're going to have to environment and actually do something. And so more and more vendors are moving to that, so hands on becomes even more critical, not only for supporting your organization and being productive on day one, but also getting past these certifications as well.
193
00:38:44.870 --> 00:38:58.890
Myles Brown: Yeah, that's certainly the case with the Ck: the the certified Kubernetes Administrator. You you got to have that muscle memory, knowing how to manipulate things. Otherwise you'll run out of time, you know. That's That's what I found. Right?
194
00:39:01.200 --> 00:39:09.069
Myles Brown: So here's another question: What trends are on the horizon for the cloud native. Where should we believe looking for? And how can we prepare for that?
195
00:39:12.760 --> 00:39:14.209
Eric Frick: Well, I I think
196
00:39:14.240 --> 00:39:26.310
Eric Frick: the the trends are the the cloud native is always in flux, like kubernetes, is is constantly changing. Um! New features are being added and integrated. Um! You'll see it
197
00:39:26.410 --> 00:39:33.430
Eric Frick: more and more emphasis as people are deploying more mission critical systems around this around security. So security
198
00:39:34.280 --> 00:39:53.510
Eric Frick: can't be an afterthought. That's that's one trend. The thing is integration of, you know, in the early days of Kubernetes integrating things like databases. We're a challenge, and you can't just ignore that If you have a legacy uh, you know system built around a giant fire, breathing oracle database that can't be an afterthought.
199
00:39:53.520 --> 00:39:54.939
Eric Frick: So things
200
00:39:56.040 --> 00:40:09.010
Eric Frick: things like that of handling in um, and also um the uh the trend of more and more organizations are going to a hybrid environment where they do have the need,
201
00:40:09.020 --> 00:40:16.720
Eric Frick: maybe from a security or a company policy standpoint, or running something on Prem, and then is trying to take advantage of. You know the the
202
00:40:17.710 --> 00:40:37.119
Eric Frick: economics of aws or azure. So I I think you're going to see more and more uh emphasis around hybrid uh types of of situations where you really need to support that. So I think those are the big trends that I see, you know security is becoming more and more uh, you know, a a huge need,
203
00:40:37.130 --> 00:40:38.470
Eric Frick: especially as
204
00:40:39.500 --> 00:40:50.920
Eric Frick: you hear about more and more things happening, and also the flexibility of of being able to um to to migrate to different cloud providers, and not get some kind of vendor Vendor uh,
205
00:40:50.930 --> 00:41:00.120
Eric Frick: you know, tie in with that, or you know. So um. And I think that's another reason to study. You know kind of generic kubernetes, or whatever is
206
00:41:01.410 --> 00:41:06.409
Eric Frick: because you might want to be a full dependence on one particular vendor, For example.
207
00:41:07.710 --> 00:41:20.260
Myles Brown: Yeah, that that's a trend we're seeing quite a bit is is multi cloud, hybrid cloud and and using things like kubernetes to to sort of shield the application from that vendor lock in.
208
00:41:20.270 --> 00:41:40.460
Myles Brown: Um. I think that's gonna just increase over time because everybody started starting to see. There are some real benefits to Multi Cloud. There's some drawbacks, too, but there's some some benefits to not time yourself to one vendor. I mean. Everybody knows that from years of experience at Id but but I think the cloud is such a big move that people
209
00:41:40.530 --> 00:41:50.649
Myles Brown: it was overwhelming to learn one cloud to learn multiple. It was, you know, a lot at first, but now they're starting to see, and and a lot of organizations are embracing that
210
00:41:52.270 --> 00:41:55.549
Myles Brown: uh Hillary, Do we have any other questions on your end?
211
00:41:56.950 --> 00:42:01.249
ExitCertified: No, I think that's it. I don't see any other questions coming through.
212
00:42:01.660 --> 00:42:04.240
Um, let me see.
213
00:42:05.660 --> 00:42:12.490
ExitCertified: So. Um, Eric, what do you see as the biggest hurdle in improving an Organization's cloud maturity level?
214
00:42:14.860 --> 00:42:27.270
Eric Frick: Well, I I I think it's. I I think it's two things I think it's. One is establishing a roadmap, and the other thing is really getting the training so that people can develop it, develop an
215
00:42:28.200 --> 00:42:36.180
Eric Frick: understand that that that roadmap. So I think what has to happen is an organization really has to commit to being a
216
00:42:36.280 --> 00:42:48.790
Eric Frick: continuous learning, continuous improvement, a type of organization. Where uh it's not like, hey? We've gone to the cloud we're over the the you know. We're over the hurdle. We don't have to learn anymore. So I I I
217
00:42:49.790 --> 00:42:55.499
Eric Frick: I think you know literally at the highest level thing. It's a commitment to becoming a continuous learning organization
218
00:42:55.530 --> 00:43:10.650
Eric Frick: and having the training back that up, and in making and institutionalizing that, and and really make it part of the company Dna to really commit that that, hey? I'm going to skill up by people continuously, and
219
00:43:11.260 --> 00:43:27.890
Eric Frick: that's a shift for a lot of organizations where, you know, training may have been an afterthought, or you know you have some, you know, minimal required training every year. I I I think, really to move up the cloud maturity scale that that that commitment to continuous improvement is, is the most important thing, and it's a mindset.
220
00:43:27.900 --> 00:43:32.199
Eric Frick: Um, you know, and and it may be, represent a radical change
221
00:43:33.190 --> 00:43:41.509
Eric Frick: in company culture work with a lot of customers that like, Yeah, it's It's fine if my cus if my employees train, but they have to do it on their own time.
222
00:43:41.520 --> 00:43:53.980
Eric Frick: Um, where's other customers to say, I allow X amount of hours per per week or per sprint. If they're doing agile development, we're going to dedicate some time to that, and really make it part of
223
00:43:54.900 --> 00:44:04.439
Eric Frick: our our Berkshire to be continuous learning. So I think those are some of the things you have to consider to really move up to scale. You really have to have a commitment to to to continuous learning.
224
00:44:06.660 --> 00:44:08.960
Myles Brown: Yeah. And I I would say,
225
00:44:09.340 --> 00:44:22.470
Myles Brown: that's not just cloud native. That's cloud in general. Right? It's It's a moving target. There's always new stuff coming, so I I tell people when they come and take. You know, an aws architect in class, I tell you, don't build an architecture, and then
226
00:44:22.800 --> 00:44:50.779
Myles Brown: wipe your hands of it and say, Well, that's it. We're done forever. We've built our, you know I have somebody on the team who's looking out and saying, Well, what's new in aws, you know. Are there new services available? Uh, is there something that we're doing manually, that either Kubernetes can do for me, or maybe the Cloud vendor can do for me that you know, can shift some of that responsibility off our developers doing everything.
227
00:44:51.000 --> 00:45:09.730
Myles Brown: And so, yeah, I find that that that continuous learning, continuous, reevaluating your architecture is is an important thing that you put that into your software development lifecycle? Right? We have another question here: How can I determine what my organization's cloud maturity is? Are there measures for this.
228
00:45:09.750 --> 00:45:13.870
Myles Brown: Yeah, you kind of mentioned that it was sort of a measurement thing. Is there a way to do that?
229
00:45:14.190 --> 00:45:20.839
Eric Frick: Yeah, there's a number of different um models that are available where you can assess your cloud maturity.
230
00:45:22.060 --> 00:45:29.780
Eric Frick: The links in front of me right now. But we can certainly provide those. But yeah, there are a number of different,
231
00:45:30.310 --> 00:45:37.749
Eric Frick: not only organizations, but you know kind of help, assessment tools that that can help you. Um
232
00:45:38.100 --> 00:45:42.749
Eric Frick: kind of assess your current state, and then also have some guide,
233
00:45:43.640 --> 00:45:46.119
Eric Frick: and for you you can move up that scale.
234
00:45:46.800 --> 00:45:47.790
Nice,
235
00:45:48.330 --> 00:45:50.080
Myles Brown: excellent.
236
00:45:50.730 --> 00:45:56.040
Myles Brown: Well, I think we're probably winding down at this point. I don't see too many new questions coming in,
237
00:46:04.610 --> 00:46:05.779
I guess.
238
00:46:07.140 --> 00:46:11.630
Myles Brown: I guess. One question when we talked about the monolith thing.
239
00:46:12.260 --> 00:46:14.700
Myles Brown: You know some organizations they don't.
240
00:46:15.210 --> 00:46:21.569
Myles Brown: They don't have any old stuff, you know. If you're at a fairly young company, you don't have a lot of legacy, but
241
00:46:21.690 --> 00:46:31.300
Myles Brown: but there is a lot out there right like. What What do you see out there like? Why is there so much out there still? That's that's on these monolith applications,
242
00:46:32.420 --> 00:46:48.080
Eric Frick: boy? There, there's just some applications that just refuse to die. Um! I I One of the projects I worked on a a past is I worked on a a migration of twenty million lines of cobalt code from the railroad Retirement Board.
243
00:46:49.020 --> 00:46:59.299
Eric Frick: They were located in Chicago. Um, all mainframe based. They had a huge uh annual bill uh for uh, operating the mainframe, you know, as a
244
00:46:59.540 --> 00:47:05.309
Eric Frick: seven figure plus annual bill to do that, and you know So so.
245
00:47:06.050 --> 00:47:09.170
Eric Frick: And and that system had been around, for,
246
00:47:10.910 --> 00:47:22.050
Eric Frick: you know, twenty-five years, and so so that's the kind of classic case in point and and the point that I made. Mostly. There was only one person there that actually was still actively developing on it,
247
00:47:22.490 --> 00:47:31.750
Eric Frick: and maybe fifty or one hundred people had worked on that system over the the life cycle of it. So you know the the other example
248
00:47:32.400 --> 00:47:49.629
Eric Frick: I I worked for Ohio, and he had a a legacy mainframe system that did telephone billing, even though we had uh voice over ip phones for sixty thousand employees, we still have landlines all over the State, and it was managed by a cobalt based mainframe system
249
00:47:49.640 --> 00:47:53.130
Eric Frick: wasn't particularly mission critical, but it's
250
00:47:54.110 --> 00:48:08.549
Eric Frick: still hung around, and you know it. To To get rid of that thing required a significant effort, so some sometimes it's not a a mission critical thing. There's something just running in a closet, and and people are like Oh, I didn't even know we had that.
251
00:48:08.650 --> 00:48:15.019
Eric Frick: And even newer organizations. Um may get them via um acquisition.
252
00:48:15.930 --> 00:48:25.929
Eric Frick: So maybe it's starting to get to grow. They see some success. They do a few acquisitions, and then all of a sudden, Wow! Bam uh legacy system didn't know you had it. Um
253
00:48:26.440 --> 00:48:36.669
Eric Frick: uh! Several years ago I toured a a verizon. Here I live in the Central Ohio area, visit their office. They were doing some new things. They had had
254
00:48:37.870 --> 00:48:51.809
Eric Frick: twenty-seven, and billing systems that they had had through acquisitions, as that Telco company got built up. And so you know. How does it happen? It just happens. Um, you know. So even if you think Oh, i'm a startup company, and i'm brand new.
255
00:48:51.840 --> 00:48:58.689
Eric Frick: I'm not going to have any of these problems. And then, all of a sudden you start growing and you have some success. Maybe you acquire a few people, and then all of a sudden, you
256
00:48:59.290 --> 00:49:09.810
Eric Frick: that you inherit these things. So it it's just it's It's amazing. You can't I? I I did some cons consulting for a a a um.
257
00:49:09.900 --> 00:49:20.130
Eric Frick: It's a government agency here in Ohio, and one of their their mission critical systems was built in power. Builder. I didn't even know power builders still existed, you know. I mean. So you
258
00:49:21.070 --> 00:49:40.469
Eric Frick: find these these bits of you know ancient systems that are out there, and then you look at them. You're like, Oh, my God! This thing is constrained by the way it's built, and it can't really service the clients that they need to because of the architecture. So um, unfortunately, they you just find them. They're everywhere. And you think
259
00:49:40.480 --> 00:49:44.049
Myles Brown: in this day. And
260
00:49:44.490 --> 00:49:47.289
Eric Frick: Yeah, I just said. And you would think they'd all be gone.
261
00:49:47.960 --> 00:49:52.110
Myles Brown: They're not just mainframes, either. I mean, it can be
262
00:49:52.500 --> 00:50:04.400
Myles Brown: a monolithic Java application right? Like I mean it. It It can kind of, you know. I've I've I've worked in some environments where you know we have one deployable artifact, and it runs
263
00:50:04.510 --> 00:50:23.809
Myles Brown: half the business right, and so that, you know those models take lots of forms, not just mainframe like not not just cobalt forty year old code it. It can be from eight ten years ago. It just it got a much bigger than it was originally intended, I think. Right?
264
00:50:24.250 --> 00:50:39.810
Myles Brown: Um, uh, maybe maybe one last. Actually, we have one here asking about um taking courses in my free hours. I have hard time committing to a full schedule. You know. What can we do with that, I mean, I guess I guess maybe you could talk about the the on demand.
265
00:50:39.820 --> 00:50:47.400
Eric Frick: Sure, we we have recently redeployed our on-demand environment. We've re-filmed everything from the ground up as well as
266
00:50:48.080 --> 00:50:57.229
Eric Frick: our labs are on to me. Environment is flexible. You can work on it, you know, whenever you have time, uh, you know, spend an hour at a time work through one lesson at a time.
267
00:50:57.270 --> 00:51:04.149
Eric Frick: The um um! The countdown is in terms of the number of hours you actually consume
268
00:51:04.940 --> 00:51:08.889
Eric Frick: on that course, and it has access to the live lab environment.
269
00:51:09.800 --> 00:51:23.960
Eric Frick: So so very flexible environment. We've put a lot of work into it recently. So uh, I'm, Sure, we're going to see a lot of growth in that is, and it's a common thing where maybe you can't dedicate forty hours for a whole week to attend a a live boot camp, but
270
00:51:23.970 --> 00:51:29.870
Eric Frick: you can work on it one hour a day, and that's actually how I prefer to learn is a little bit at a time.
271
00:51:30.290 --> 00:51:38.000
Myles Brown: Yeah, for sure. And and the lab you get the same total amount of lab time. But you can just start and stop it. Kind of thing. Is that the idea?
272
00:51:38.440 --> 00:51:44.479
Eric Frick: Yes, exactly. And it's integrated into the the on Demand delivery system.
273
00:51:45.200 --> 00:51:48.060
Myles Brown: Well, that That sounds like a great alternative for
274
00:51:48.470 --> 00:51:59.060
Myles Brown: for for people that can't attend a live class. Now, when it comes to live classes like, I said, if you're doing more of a private engagement. You might be able to, you know,
275
00:52:00.240 --> 00:52:06.679
Myles Brown: mess with the hours a little bit, but on an individual basis. If you're going to come and take a private public class,
276
00:52:06.850 --> 00:52:17.639
Myles Brown: you know It's generally nine to five. There's not much you can do about that, but the on demand really does fit that nice, nice uh niche where you you, you know I don't have that much time to commit
277
00:52:17.650 --> 00:52:43.629
Myles Brown: like you said a lot of organizations, you know some organizations. It's tough like they're You're sort of on your own. Yes, we'll pay for trading, but you can't take time off. You know we have a lot of consultancies and things that are like a billable hours, and they can't, you know they've got to work on it two hours on Friday afternoon, or you know something. They they have a very little time uh, but maybe once a week, or something that they can do,
278
00:52:43.640 --> 00:52:47.279
Myles Brown: so that that does certainly uh scratch that itch, I think
279
00:52:47.540 --> 00:52:49.250
Myles Brown: All right. Well, I think
280
00:52:49.260 --> 00:53:10.890
Myles Brown: I think that's pretty much all the questions we're seeing. Uh, I want to thank you, Eric, for for your presentation today. And uh, and I think Brandis for uh providing those those uh vouchers for the uh the Cn. Fifty on demand class. Um, like, I said, you should be getting a link in an email in the next few days. I'm sure.
281
00:53:10.900 --> 00:53:22.649
Myles Brown: And you'll also get this recording. If you have any questions you've got this email address. Uh, To be honest, you can probably just send things to me as well. Let me just throw my email in there,
282
00:53:25.650 --> 00:53:29.589
Myles Brown: i'll just use my that exit certified.
283
00:53:31.410 --> 00:53:42.820
Myles Brown: So if you have questions, whether it's related to technology or you know sales, I I can find a salesperson um to help you. Uh get set up. Um,
284
00:53:43.060 --> 00:53:58.679
Myles Brown: We uh we do more than just cloud native training. We mentioned. We do all that, you know, uh public cloud stuff. We we actually do quite a bit around analytics and things like that. Uh, the Voucher code does not seem to work. Somebody is saying
285
00:53:59.120 --> 00:54:01.429
Myles Brown: voucher code does not seem to work the
286
00:54:01.580 --> 00:54:05.839
Myles Brown: well, we should get that ironed out before we email it out.
287
00:54:05.970 --> 00:54:09.220
ExitCertified: Yeah, um, let's see who it is.
288
00:54:09.650 --> 00:54:20.729
ExitCertified: Um. So, Richard. Um, I can take down your information, and then probably just email um someone on the remarantas team to get that checked out if it's not working currently on the website.
289
00:54:21.420 --> 00:54:26.240
Myles Brown: Yeah, we'll we'll get that sorted out and then send out an email when we uh
290
00:54:30.050 --> 00:54:32.870
Myles Brown: possible. It's a Yeah, we'll figure that out
291
00:54:33.560 --> 00:54:52.859
Myles Brown: all right. Well, thank you. Thanks again for everyone for attending. And uh, hopefully, you found this useful, and we hope to see you in class sometime soon or uh, you know, if you're in the on demand, you'll you'll probably see uh, Eric. They'll see you on the Cn. Fifty, I think. Is that right?
292
00:54:53.270 --> 00:55:00.779
Eric Frick: Yeah, or at least hear me uh. So I don't know how much uh camera time I log in there. But yeah, you'll at least hear my voice.
293
00:55:01.660 --> 00:55:02.720
Excellent!
294
00:55:03.350 --> 00:55:04.649
Alright,
295
00:55:05.730 --> 00:55:08.109
Eric Frick: thanks again, everyone.
296
00:55:08.650 --> 00:55:11.960
Eric Frick: And I really appreciate you. Tony and I enjoyed our discussion.
297
00:55:12.370 --> 00:55:13.950
Thanks, bye,
