บทถอดความฉบับเต็มของ From Incident Response to Optimization: The BBD Cloud Journey

WEBVTT 00:00:20.815 --> 00:00:22.996 Tech Unboxed with. 00:00:23.097 --> 00:00:23.797 BBD. 00:00:24.160 --> 00:00:25.321 Tech Unboxed with BBD. 00:00:26.641 --> 00:00:36.392 Here we are, another Tech Unboxed from BBD, and I have a special guest today with me, werner, and Werner is going to talk about managed cloud services at BBD. 00:00:36.392 --> 00:00:41.176 So, werner, can you please introduce yourself and tell a little bit about BBD? 00:00:47.579 --> 00:00:49.122 Yeah, sure, great to meet you and happy to be here. 00:00:49.122 --> 00:00:50.786 Um, so my name is banner the author. 00:00:50.786 --> 00:01:06.668 I'm part of the, the bbd software development organization, but specifically within our, our cloud space, and I head up our cloud managed service division, which also, coincidentally, service division, which also coincidentally does migrations, modernization. 00:01:06.668 --> 00:01:19.096 So really we are an enablement factory for cloud in BVD but, yeah, like you say, more specialized on the managed service front which we are discussing today. 00:01:19.737 --> 00:01:27.227 Oh great, and I'm happy to hear that there's many other topics that will come to the surface, so let's explore them one by one. 00:01:27.227 --> 00:01:35.109 But there was a little bird that told me that just recently you created a dedicated managed cloud service within BBD. 00:01:35.109 --> 00:01:37.147 Could you explain us a bit more about that? 00:01:37.700 --> 00:01:55.191 Yeah, so that's actually an interesting one, because even though we've recently sort of formalized and split it out into a uh like its own sort of brand within within bbd, that was really more of a a marketing focus on it. 00:01:55.191 --> 00:01:59.704 So how do we, how do we present our, our cloud services, a bit better? 00:01:59.704 --> 00:02:05.072 So the service itself has existed within bbd for uh for quite some time. 00:02:05.072 --> 00:02:26.098 Uh, quite a few years was really just more of a market positioning of that and the um, the idea of that is, uh, just to to highlight the, the offering, a bit better is that because there's a a new trend in cloud adoption? 00:02:26.158 --> 00:02:28.604 is that something changed in the last few months? 00:02:28.604 --> 00:02:31.950 That, uh, this carve out happened? 00:02:32.372 --> 00:02:36.647 it's not necessarily that there's a a new trend in in the market, but what we? 00:02:36.707 --> 00:03:11.414 We have definitely found that there is a requirement for uh for the service, and it is a bit bit different, in the way that we approach it, to the traditional business that we do In the sense of we are a purely multi-tenanted environment and it's almost like a subscription model or a software as a service, where we've built out the tooling, we've built out the processes, all the monitoring, etc. 00:03:11.414 --> 00:03:14.039 And we just plug it into your environment. 00:03:14.039 --> 00:03:23.528 And this is something that we have found in the market is something that many clients don't necessarily have internally. 00:03:23.528 --> 00:03:24.850 Many clients don't necessarily have internally. 00:03:24.850 --> 00:03:44.068 So not having proper monitoring and observability, not having the ability to respond to incidents that arise and also not necessarily knowing enough about the cloud in order to respond to these things well and, in some cases, not even being able to identify if there is a problem. 00:03:44.068 --> 00:04:02.615 So, yeah, that was really the rationale behind it is to make it a bit easier, position it for what it is, which is the subscription-based managed service, and just highlighting the values behind that. 00:04:02.780 --> 00:04:03.943 Just highlighting the values behind that. 00:04:03.943 --> 00:04:05.889 And how far does subscription-based go? 00:04:05.889 --> 00:04:16.350 Because you mentioned a couple of practical things that are very handy, like incident management and stuff, but how does it actually practically work on a technical level? 00:04:16.350 --> 00:04:25.262 Does that mean that the technical capacity or the CPU that you use on the cloud is also something on subscription-based, or is that you buy a lot and that's it? 00:04:27.266 --> 00:04:37.326 so a customer or any company would have their own cloud environment with all their services in there, their compute, database, storage. 00:04:37.326 --> 00:04:55.488 Um, all we do is we plug in an observability stack into that so we make sure that we can see all of the resources that you are running, and then we've got a predefined set of metrics that we monitor constantly. 00:04:55.488 --> 00:05:12.190 If anything breaches a threshold that we've defined as either the system is impaired or the system is down, that'll automatically flag on our help desk, and then we've got a team that does the incident response on our side. 00:05:12.190 --> 00:05:23.413 So what we're really taking the responsibility for here is how do we identify and respond to any technical issues? 00:05:24.442 --> 00:05:29.629 So that's where the manage part comes in, because you don't have to have your own team doing this. 00:05:29.629 --> 00:05:31.644 That's, in essence, what you're saying, right? 00:05:32.567 --> 00:05:33.170 Yeah, correct. 00:05:33.339 --> 00:05:45.740 And what that allows us to do as well is we don't just do incident response that's just, more often than not, the burning problem but we do a lot of proactive services as well. 00:05:45.860 --> 00:06:18.613 So one of the things is that we implement a security posture monitoring and if we use AWS as an example here, that'll be with Security Hub so we define what your security frameworks are that you need to comply to, or what compliance frameworks you need to comply to, and we will constantly monitor those from an infrastructure and security perspective to make sure that we maintain you above 80% of that score at a minimum. 00:06:18.613 --> 00:06:23.067 So that's one thing, and