>> My name is Marilag and welcome to my world.
[MUSIC]
>> I have been working from home for four months now in
my new house that I want to show you. Come.
[MUSIC]
>> My house, it's not completely done yet.
Because like I said,
I moved about four months ago.
One thing that was so important for me is that I
need to find a home where I can get a lot of air,
I can get a lot of nature.
Apparently, that's what inspires me when I'm working.
[MUSIC]
>> I came from a city where it's crowded,
it's crazy, and none of my friends worked with computers.
So I didn't really have any,
I would say, role model.
Luckily, I had a brother who is really,
really good with computers.
When my parents decided to buy him one,
so they introduced this massive white machine
in our really small living room.
I think it was like 36 square meters apartment
and we're a family of six.
They brought it in, and then I got curious.
As soon as I got started,
as soon as I a wrote my first program and then that was it.
That's the love at first sight,
almost kind of thing.
Being a Computer Programmer from where I was from
was difficult because I didn't have access to the right resources.
I used a lot of time learning even
now after 20 years of working in IT.
Starting as a Junior Programmer in a school trying
to build solutions for an academic institution,
and then eventually moving to Europe,
to Denmark to develop
larger scale applications for multinational companies.
I would say that, of course,
even if it's scaled up,
the challenges are the same.
It's your access to learning,
which should be constant because it changes so fast.
Everybody knows that about technology,
and you don't want to ignore it because there's a lot of
opportunities with all the new things that's coming.
But it's difficult to learn.
If you're doing it alone and you don't
have access to learning materials
and to a network of people that could also inspire and help you,
it can be quite challenging.
I started my own communities
in the Philippines and also in Denmark,
and started sharing my experiences by speaking at conferences.
I'm really, really happy that I get
to give back to the community this way.
[MUSIC]
I always start my day on Azure DevOps,
and because I have my team in the Philippines,
it's very important for us to be able to collaborate efficiently.
One of the first things that we tackle
are the bugs that we find on production,
and it goes on top of the backlog.
Because we have everything automated with
our pipelines and then we use Live Share,
so that we can collaborate on fixing the bug,
it's very easy for me to see what's going on,
change something on the file and then my colleague can
test it and then locally and then commit it,
and in the pipelines run and then the bug is
fixed in production within a couple of minutes.
I work on primarily the Cloud Architect.
My main role is to break
down a big problem into smaller software components.
I think that's really important,
especially, for development teams because it's easier
to solve problems if you can focus on one thing at a time.
But the fun part is how to make
these components work together
without creating very strong dependency.
Because if you make them too much dependent with each other,
then you're ultimately also just
building a big system and you don't want to do that.
You want to isolate the development of
each of these components and make them talk together.
One of the ways for making them communicate using
Azure services is to design your application to be event-driven.
If you want an event-driven application,
there are different platforms on Azure
that you can use for different purposes.
Once you have broken down
your big problem into smaller components,
it's very important to know how
to connect this components together.
What do you want to do is to put something
like a broker in between these components,
so that they can talk to each
other via the broker by sending messages.
You have to distinguish between
a command and an event as types of messages.
A command message is just something
like saying that this component,
it has executed a command and then it
has a contract between the other component,
so that the other component must
know that the command has been executed,
so that it can react.
One of the things that you can use on Azure
for this is something called a service bus.
In a service bus is a very advanced queuing system.
It's built for enterprise grade messaging.
You want to use a service bus for sending messages as commands,
but you also have to distinguish it from events.
An event is something that has transpired.
For example, a component has
executed a command and after it is executed,
it will publish an event.
But once it has published this event,
it doesn't really have to worry about who
is going to be picking up this event, this messages.
So as far as that component is concerned, it's already done.
Then you can set up subscribers, and that's optional,
so the subscribers can pick up
the event, and then also, now it start executing their own command.
For this, you have something called an Event Grid on Azure,
where it's really designed for processing events.
So what you can do is it has an endpoint,
so that your component can call that endpoint
and you can send an event message.
Then from that, you can set up a lot of subscribers.
There are different types of subscribers who, for example,
you can set up an Azure function as
a subscriber or a webhook cues,
or even another service bus,
which is an advanced cue.
Once an event has been published by Event Grid,
it goes to service bus.
That's how you orchestrate it.
But if you have a need for processing large amounts of events,
then you would need something called an event stream.
You can want this as a fully managed service on
Azure using something called Event Hub.
But if you want to use
the very popular open-sourced events streaming service,
then you can use Kafka,
then configure your clusters on Azure.
But I think the more efficient way is to
also use fully managed services for Kafka,
like running Kafka on
HDInsight or running Confluent on Azure and it's super efficient.
This is the building blocks together efficiently.
Once you have all these small pieces running,
the most important thing for a developer is to put that on
production as fast as you can with highest quality.
For that, when we build our solutions,
we use automation a lot.
We use YAML on Azure Pipelines to automate our CI/CD,
so that we can deploy a piece of that software on its own,
from dev all the way to production, and it's super-efficient.
We use this type of architecture and
this tooling in one of our largest projects at the moment,
and that's to build a self-service portal
for Developers in an enterprise company,
so that they can speed up
their delivery of their Cloud applications.
They use the self-service portal to
provision Cloud artifacts on Azure
as fast as they can without having
to call service desk and requests for resources,
which can take months and even
sometimes a year before they can get something running.
But now, from months to just a couple of weeks,
they have something running on production and they have more time
to innovate and they can maximize the use of the Cloud this way.
>> One thing
>> Marilag
>> has taught me is
>> to be open.
>> To be persistent.
>> Always have the courage.
>> Dedicating time to your passions.
>> Self love.
>> That you can never master something
after the first time of you trying it.
>> Always be true to ourselves.
>> To love myself.
>> To continue my search for strong,
impactful and diverse community leaders.
>> Always do what you want to do and do it passionately.
[MUSIC]
>> The best
>> thing about Marilag.
>> She is passionate with everything she does.
>> Is her innate desire to learn new things.
>> She has me as her sister.
>> Is her character.
>> Is that she makes sure that she does her best at everything.
>> That she's a true role model.
>> That she can be really spontaneous
and will give you instant surprises.
>> It's her ability to explain a technical topic.
One of the things that makes her a great [inaudible] bigger.
>> Some of the problems that we need to solve in technology,
we need to solve now.
We cannot wait any longer.
For example, when the pandemic happened,
we have to rally a lot of
Developers to solve the issues very quickly.
The last thing we need is
Developers struggling with a technology or a tool.
We want them to be happy Developers.
Like me, I'm a happy Developer,
but I also know the pain I've been through with.
But now, I'm in a better position with access
to learning resources and to a community.
I want to be able to help others to be where I am,
where we can solve the problems easily and still
have enough time to do other things that matter to us,
like our family and maybe also giving back
to the community and empowering others.
[MUSIC]