Hello and welcome on This Is My Architecture.
I am Alessandro from AWS.
Today I am with Walter Dal Mut from Corley. Hello, Walter.
Hi.
Can you tell me about Corley and what you do?
Sure. Corley is a partner of AWS that follows clients on the territory
for cloud migration and the development of cloud-native applications.
Ok, I see here that you have an architecture
Elastic Container Service,
Elastic Load Balancing.
I know that you started with a monolithic architecture
and then you redesigned it.
Can you tell me about the application
-and how you transformed it? -Sure.
The monolithic application, Idea Scuola, would manage
the whole supply chain of digital contents.
So, the student, the professor,
the agents on the field that distribute the license
as well as the managers that handle the whole platform.
Ok. So, you moved to an architecture based on microservices.
Why did you choose this specific type of architecture?
Well, for several reasons
from cost saving to scalability,
the management of parallel development teams
and the support of multilingualism in the development
of the different infrastructural parts during the migration.
Ok. Could you explain how this works?
Sure.
It starts with load balancing
to the different microservices
all existing within the ECS part.
So there is just one passage from the load balancer that finishes
the https protocols and moves to the different microservices
deployed in the ECS.
Ok.
I see Lambda, Code, Notification System.
How does it integrate with these parts?
The different microservices often need to communicate with each other.
So, what happens is that
when a microservice
has to notify an event because of an internal variation
it actually notifies an SNS topic.
So, a topic is directly notified
and, depending on the subscriber,
which means the microservice that needs to read that information,
it may arrive a message in a queue
or a Lambda may be activated
for a direct execution
of the event received on the platform.
For example, the sign up of a user.
Ok. So, those who read the queue
besides having the Lambda
and other services that read the queue
are always hosted on ECS?
Yes, they are always hosted on ECS
or, if they are integrations of third suppliers,
they can get attached directly to the queue
and pull out the information.
-I get it. -It is completely flexible.
So, I see you also have CodeCommit
as a source-code repository.
So, you managed to move on to
a sort of easy development.
Can you tell me more about the advantages?
Yes, absolutely.
With the increase of microservices
and the development teams
we have the need to release quickly
-the application functionality. -Of course.
So, the developer publishing directly his code on CodeCommit
create a codebuild event
that builds
the docker image necessary for that application
and then it publishes it on the ECR.
Once the image is uploaded a stack of cloud formation is updated
which delivers
the infrastructural update directly in the framework.
All this in a very short time.
Ok, perfect.
I see down here Elasticsearch too.
So you have research functions inside the product?
Yes, of course.
Elasticsearch is a fundamental element because it provides
all the research advantages with a lots of added values
directly offered on the platform.
Moreover, this is used not just
in the ECS part that takes care of context indexing
but also in the integration
of a digital catalog coming from external sources
that release the documents directly on a S3 backet.
At the release of a S3 bucket a Lambda is unleashed
which pulls out the key information from it
and create an index in the same repository
so that then directly
through the stack of the ECS, a dedicated microservice
all the platform received the research results easily.
Beautiful. I get it.
So, do you have in mind
some future developments?
Are you working on something specific that you want to mention?
Yes, thanks to the expandability of the platform
we can introduce additional components
like, for example, the new AI services
the sensible content extraction from PDF
services like this to offer indexing
and that kind of activity.
We also created a real playground for the applications
so that other suppliers can join the development releasing their services
directly in the structure.
Working on making the infrastructure
more simple with less parts
to handle for the different application components
which also means more advantages
such as cost saving.
I see.
Very well. Thank you for your explanation, Walter.
Thank you.
Thank you for coming.
Thank you for having me.
Thank you all for watching This Is My Architecture.