Hi. Welcome to a new episode of 'This is My Architecture'.
I'm Jose. I'm here with Quim, from Linke. What's up?
Hi. How are you?
Quim, tell us a little about what Linke does.
Linke is a tech company specializing in SAP, in AWS.
We are in charge of migrations and managed services
of SAP systems in the cloud.
And Linke has created a healing framework for SAP systems,
tell us a little about what this is.
Let's start with the basics, which is, SAP consists of a series of elements
which are distributed in AWS in different regions.
We have an application part, and we have a database part.
- Uh huh. - Okay?
So, what we have set up are normally active-passive systems,
and what we have assembled is an outsourced monitoring system
- for the instances. - Okay.
Got it. And how does this monitoring system work?
Normally in the classic environment, that's what the operating system takes care of.
And what we've done, trying to follow the AWS best practices,
is that decoupling, using the monitoring part
to utilize serverless systems available as AWS services.
Sure, because, up here I see... Eventually, the SAP platform
requires a very large computation. So from this distance,
simple EC2, I understand that you want to try to optimize the cost as much as possible, right?
Well, you can find the issue of cost optimization with the reservation part.
- Yes. - When you are working with high availability
you always need to be available, and, what we are doing here
is ensuring availability, the availability of the systems.
So, well, with what we've set up,
which are two monitoring elements based on infrastructure,
for which we use Cloudwatch, and with Lambdas
- to review application topics. - Uh huh.
Okay? We see that it's working and gives service to users.
Based on what happens, and the response of these two monitors,
we generate an event, any event, any failure, what we generate is an event
that, in turn, depending on the moment, it's associated with an SNS
which does two things. One, notifying the service,
via email or integration with any ITSM,
and to another healing Lambda which, what it does is recover
that failure that has been detected so that it works correctly.
And with that, then, we gain the peace of mind
that if the instance where the monitor is fails, we have it outside
and that lets us keep working with total peace of mind.
Got it. And so, what does the system look like here then?
Sure, nice touch. I'd forgotten. In the end, to do the healing,
what we do is, we launch command lines through the SSM Command.
And that allows you to restore the application. At the infrastructure level,
it's the AWS hypervisor which would be in charge of that,
but in this case it does operations typical of the operating system,
launching specific commands that are needed in SAP.
I see you have everything tied together well, a robust platform.
What are you working on in the short, medium, and long term?
One of the requests clients are bringing us
is that, in addition to high availability, to recover in another region.
And that's the part we're working on.
Creating a DR that, instead of the healing Lambdas, allows us
to have the replica of the data or backups and AMIs in other region
and then be able to define a flow with a Lambda that picks it up it directly in the other region.
And that's what we're working on right now.
Very good. Everything's clear, Quim. Thanks so much.
Thank you.
Thanks you, we'll see you in an upcoming episode of 'This is My Architecture'.