►
Description
Fighting Covid with Serverless and JavaScript - David Gonzalez, NearForm
At NearForm, we built a number of Covid tracking applications but more important: we also open sourced the core. This source can be found at https://github.com/covidgreen/. In this talk, I will explain what are the major pitfalls we found along the way but also how to operate a planetary scale application with a very reduced team of people and a surprisingly low number of outages. Table of contents: - Introduction - Why Serverless - What were the biggest problems - Recommendations for running large scale geographically dispersed apps
Join the speaker for live Q&A on Slack, channel - #openjs_world-automation_ci_cd
Thursday, June 3 from 02:00 - 02:20 PDT / 11:00 - 11:20 CEST
Thursday, June 3 from 07:40 - 08:00 PDT / 16:40 - 17:00 CEST
A
First
of
all,
some
presentations.
I
work
as
a
devops
architect
for
a
company
called
uniform
by
the
way
we
are
hiring
if
you
are
looking
for
a
job.
Just
send
me
an
email
and
I'll
be
more
than
happy
to
introduce
you
to
the
pertinent
people,
I'm
also
a
part-time
lecturer
at
cct
college
in
dublin
I
lecture
mainly
in
cloud
and
devops
and
in
general
software
development.
A
But
turns
out
the
next
day
you
test
positive
for
copy
19.
So
how
do
you
warn
the
people
who
have
been
with
you
in
the
booths,
which
are
a
close
contact,
that
you
have
copied
19
and
they
have
been
in
touch
with
you
should
then
they
should
be
tested,
but
you
don't
know
them.
So
that's
a
very
sort
of
tricky
problem
and
in
the
beginning
of
all
the
copied
pandemic,
we
didn't
know
too
much
about
the
disease.
A
We
didn't
know
how
close
or
or
for
how
long
you
should
have
been
in
contact
to
a
person,
but
the
reality
is
that
the
videos
was
spreading
very
quickly.
There
is
another
interesting
point
about
kobe
19
is
that
everybody
talks
about
the
heart
immunity
at
70
percent,
like
once,
70
percent
of
the
people
are
immune
to
the
virus.
In
theory,
we
should
have
what
the
scientifics
called
health
immunity,
which
means
there
are
not
enough
individuals
who
can't
transmit
the
virus,
so
the
pandemic
will
reduce
and
eventually
will
disappear,
but
that's
not
the
reality.
A
So
that's
why,
when
the
pandemic
started
many
of
pretty
much
all
the
countries
in
the
world
dictated
a
severe
lockdown
where
people
will
not
be
able
to
get
close
to
each
other
and
block
the
people
in
clusters.
So
that
means
that
her
immunity
number
or
that
number
will
go
down
ideally
below
one
and
the
head.
Immunity
will
be
less
than
70
percent
until
we
have
a
solution
for
the
virus.
So
one
way
one
way
to
avoid
this.
This
transmission
is
by
isolating
close
contacts,
as
I
said
before.
A
So
if
you
are
only
seeing
your
family,
the
reality
is
that
you
will
only
transmit
the
videos
to
your
family
and
the
only
possible
vector
if
somebody
in
that
cluster
going
out
for
shopping
or
going
out
contacting
other
people.
So
we
reduce
the
ability
for
the
videos
to
spread
what
is
a
close
contact
with
time.
It
was
determined
that
it's
15
minutes
closer
than
2
meters,
and
that
is
why
what
google
and
apple
implemented
in
the
contact
tracing
api
in
android
and
ios.
A
In
that
case,
we
used
a
lot
of
javascript.
What
I
mean
a
lot
of
javascript.
Is
that
pretty
much?
Absolutely
everything?
Well
pretty
much.
You
know
absolutely
everything
in
the
application
is
written
in
javascript
from
the
application
itself
built
in
react.
Native
to
the
back-end
api
built
in
node.js.
A
A
A
A
A
The
rds
was
not
super
mature
and
we
prefer
to
go
for
the
the
you
know,
the
the
comfort
area
of
or
database
skills
the
api
gave
here
is
marked
in
bold,
and
there
is
a,
I
would
say,
a
foreign,
but
it's
not
very
funny
about
the
api
gateway,
and
so
the
api
gateway
is
key,
pretty
much
for
every
distributed
infrastructure.
Nowadays,
I've
seen
many
customers
mainly
building
node.js
applications
which
fail
miserably
because
they
don't
have
an
api
gateway
strategy.
A
A
Then
we
also
use
the
useful
suspects.
Sqs
sns
ppc,
like
you,
know,
typical
building
blocks
of
aws
that
everybody
would
use.
Also
serverless
has
another
problem.
Okay-
and
this
is
a
spoiler
alert.
Lambdas
are
bad
with
three
dots
and
we
will.
I
will
explain
you
more
about
that
in
a
second,
so
lambdas
are
a
very
dangerous
ally
and
node.js
and
landas
are
the
perfect,
perfect
combination
in
aws,
because
the
speeds
at
what
you
can
develop
a
system
with
some
components
based
in
lambda.
It's
unreal.
A
I
mean
you
can
be
very
productive
at
modeling
a
system
with
dandas,
but
if
you
model
your
full
system
using
dandas,
it's
what
I
call
the
2021
version
of.
Let's
use
a
store
procedures.
You
just
do
that.
Don't
do
that!
You
should-
or
in
my
opinion
you
should
actually
combine
lambdas
with
some
other
components
like
ecs,
fargate,
k
native
or
you
know
like
lately.
Google,
for
example
in
gcp,
have
released
something
called
gke
autopilot
which
allows
you
to
run
a
kubernetes
cluster
without
having
any
servers.
A
A
The
bogina
distributed
message-based
system
is
the
first
circle
of
hell.
I
can
tell
you
because
the
picture
on
the
right
is
the
picture
of
me
after
solving
a
book
for
like
about
12
hours
in
a
row,
so
we
all
know
how
hard
could
be
to
follow
the
flow
of
a
javascript
application
using
promises
or
using
callbacks
or
using
async
await.
I
hope
everybody
is
using
a
single
weight.
A
If
you
are
trying
to
follow
the
execution
of
a
request
across
a
number
of
services,
lambdas
and
cloud
native
services
like
api
gateway-
good
luck
with
that,
because
you
are
going
to
need
like
a
few
hours
of
coming
in
and
out.
So
my
advice
is:
make
your
system
as
simple
and
as
straightforward
as
possible.
I
read
this
morning
on
linkedin
a
very
interesting
phrase,
which
basically
said
architecture
in
software.
A
It's
there
to
make
your
life
easier.
Everything
else
is
just
religion,
and
that
is
something
that
should
be
a
mantra
in
serverless,
especially
working
with
javascript.
I
love
javascript.
It's
you
know
like
my
go-to
language,
for
pretty
much
99
of
the
work
I
do
nowadays,
but
the
reality
is.
The
javascript
flow
is
somehow
hard
to
follow
because
our
brain
is
used
to
a
procedural
language,
but
with
javascript
that
that's
not
the
case,
even
though,
with
async
await
you
can
make
it
look
like,
but
it's
really
not
there.
A
You
need
to
have
things
into
consideration,
but
imagine
combining
that
with
a
very
complex
flow
of
a
very
complex
flow
of
servers,
passing
requests
to
other
servers
or
lambdas
passing
requests
to
the
landers.
It
can
get
really
really
problematic,
and
this
is
the
continuation
of
the
three
dots
and
lambdas
are
bad
in
the
majority
of
the
cases.
But
there
are
other
times
where
lambdas
are
their
perfect
er
like
they
find
their
perfect
fit,
for
example,
for
an
asynctask
runner.
Let's
imagine
you
don't
need
to
imagine.
A
I
will
show
you
the
code
of
that
in
a
second
is
that
you
have
a
lambda
which
needs
to
run
every
night
to
send
statistics
to
the
central
statistic
office
or
to
recalculate
how
many
people
have
been
exposed
to
copied,
or
things
like
that,
and
so
lambdas
are
the
perfect
place
for
that,
because
you
can
delegate
into
your
infrastructure
the
running
of
lambda,
and
that
makes
your
life
so
much
easier
because
you
don't
need
to
worry
about
the
application
being
up
at
the
time.
You
don't
need
to
worry
about
retries
mechanism
and
things
like
that.
A
So
it's
just
convenient
they're.
Also,
the
perfect
jwt
validator
in
the
api
gateway,
so
one
of
the
reasons
of
the
api
gateway
to
be
alive
or
to
be
in
the
architecture
of
pretty
much
every
microservices
system
is
that
you
probably
are
using
distributed
authentication
with
jwt,
and
you
really
want
to
do
that
at
that
validation
and
number
verification
at
the
edge,
because
otherwise
you
need
to
do
that
in
every
service
and
can
get
very
problematic.
A
A
Another
very
good
point
on
lambdas
is
that
the
scalability
is
just
out
of
this
world
and
you
can
easily
choke
other
services.
I'm
going
to
give
you
here
very
interesting,
very
interesting
situation
where
we
needed
the
secret
for
the
jwt
validation
and
what
happened
was
that
that
secret
was
a
story
in
the
secrets
manager.
A
So
on
peaks
in
ireland
and
in
other
tenants
we
actually
had
over
4
000
requests
per
second
into
the
secrets
manager.
And
if
I
recall
correctly,
the
maximum
hard
limit
of
secrets
manager
per
account
per
second
was
set
to
2000
or
4000.
I
don't
actually
remember,
but
it
was
like.
All
number
of
requests
were
over
that
on
peaks
and
we
found
out
because
we
were
getting
some
errors
that
we
couldn't
explain
until
we
moved
the
secret
from
the
secrets
manager
into
an
environment
variable
in
the
in
the
jwt
validator
lambda.
A
A
Lambdas
are
also
very,
very,
very,
very
cheap
unless
they
spy
a
lot
of
contour
like
if
you
don't
have
a
good
mechanism
to
to
check
lambdas
and
to
you
know,
keep
them
at
at
bay.
You
can
end
up
with
a
serious
hefty
build
from
aws
or
from
any
other
club
provider,
but
if
you
have
them
under
control,
you
will
be
paying
less
than
100
euros
per
month
to
run
a
significant
amount
of
code
and
workloads
that
will
help
you
to
actually
deliver
your
system
with
a
very
high
level
of
stability
and
then
latency.
A
Like
many
people
will
come
to
me
saying
oh,
but
you
know
lambda's
introduced
latency.
I
will
tell
them
latency
what
latency
like
you
can
work
around,
that
you
can
actually
build
your
node.js
lambda
and
using
midi
or
any
other
middleware,
and
then
your
call
start
will
be
sub
second,
and
every
subsequent
call
will
actually
be
immediate.
There
is
not
going
to
be
call
runes
anymore
and
the
lambda
will
scale
up
or
down
depending
on
load,
and
basically
that
latency
is,
I
think,
on
the
on
the
past.
A
A
One
of
the
patterns
that
we
heavily
use
in
the
copied
applications
was
we
had
or
what
we
call
our
exposures
lambda,
which
was
annotated,
lambda,
which
was
actually
getting
the
list
of
all
the
random
ideas
that
got
exposed
into
like
like
they
got
tested,
got
a
positive
and
positive
result
as
you
are
infected
by
copy,
then
that
person
gets
an
sms
from
the
health
provider
and
then
you
bloat
the
random
id
into
the
server
and
then
all
the
phones
in
the
tenant
download
the
file
with
the
random
id.
So
there
is
no
way
to
track.
A
A
How
does
it
look
like?
So
we
have
this
as
open
source,
so
I
will
show
you
the
code
and
the
repositories
in
a
second.
What
we
do
is
we
keep
the
philosophy
of
we'll
build
one
instance
and
deploy
it
everywhere
approach
most
of
the
time.
Okay,
we
have
some
tenants
which
have
some
special
requirements
and
also
thanks
telephone
for
being
aguard.
So
terraform
is
amazing,
but
there
are
some
corners
where
a
terraform
plays
against
you.
A
So
the
fact
that,
if
you
want
to
do
an
if
else,
if
something
create
this
resource,
otherwise
don't
create
it
converts
a
simple
resource
into
an
array
of
resources.
It's
just
mind-blowing
and
the
fact
that
there
is
not
an
easy
way
to
just
include
or
remove
modules
until
tera
from
013.
It's
another
interesting
fact,
but
all
in
all
terraform
is
it's
a
powerful
ally,
so
just
be
careful
with
some
corners.
A
The
way
we
build
it
is
we
build
the
gold
standard,
which
is
the
copy,
green
infrastructure
repository,
and
then
we
use
that
as
a
module
in
every
single
tenant,
injecting
the
configuration
that
we
want,
plus
some
customization
that
we
need
for
each
tenant.
So
that
way,
we
can
actually
release
a
new
version
of
covering
grid
copy,
green
and
then
used
by
every
single
tenant
and
roll
it
out
to
the
nine
tenants
per
two
environments.
That
means
18
environments
pretty
much
immediately.
A
So
we
were
very
mindful
to
have
a
repeatable
process
and,
aside
from
that
repeatable
process,
we
wanted
it
to
be
as
simple
as
possible.
So
complexity
is
the
the
evil
number
one
on
every
system.
So
if
you
want
deploy
with
one
click
and
draw
back
with
one
click,
you're
almost
safe
from
disaster,
so
yeah,
that's
that's
your
approach.
The
applications
themselves
are
react
native,
so
we
at
near
form
we
breathe
node.js
inside
out.
We,
I
think
we
contribute
to
the
code
of
nodejs
something
like
40
of
the
code.
A
It's
people
working
in
node.js,
and
so
it
made
sense
to
use
react
native
because,
like
we
know
javascript,
we,
like
you
know
I
say
not
js,
but
the
reality
is
it's
just
javascript
and
we
know
react
very
well
so
having
the
application
done
in
vr
native,
is
you
know
the
obvious
choice
and
also
the
copy
green
initiative?
Is
a
linux
foundation,
public
health
project?
So
that
means
that
we
are
part
well.
A
You
also
have
some
level
of
documentation,
which
is
not
always
super
accurate,
but
in
general
describes
the
system
very
well
and
allows
you
to
pick
around
and
see
what
we
have
built.
Obviously,
it's
not
perfect,
but
I'm
of
the
opinion
that
perfect
is
the
enemy
of
don,
so
I
preferred
it
to
be
working
than
you
know
being
running
around
seeking
perfection
where
there
was
a
global
pandemic
and
we
needed
this
out
very
quickly
and
very
efficiently.
A
If
I
can
take
one
second
of
your
attention,
I
like
to
be
very
grateful
to
all
the
people
contributing
to
this
project,
because
the
team
was
amazing
and
it
would
not
have
been
possible
without
any
single
of
them.
So
that's
my
cutout
for
them.
We
also
have
other
interesting
repositories,
which
is,
for
example,
the
back-end
api.
So
this
back-end
api
is
just
the
server
side
that
we
we
build
in
in
near
form
for
supporting
the
server-side
loads
in
general.
A
A
Some
jwt
code
here,
but
also
allows
us
to
inject
the
allows
us
to
inject
the
the
roots
as
plugins.
So
whenever
you
go
into
a
root,
for
example,
metrics,
you
will
find
three
files
well,
four
files
in
this
case,
including
the
test.
The
first
one
is
the
index,
which
is
what
is
the
handler,
and
this
is
a
facilify
handler.
Okay,
it's
a
fast
effect
handler
which
has
become
a
plugin,
and
then
we
do
a
schema
validation.
This
schema
validation,
it's
coming
from
a
file
called
schema,
and
this
schema
defines.
A
How
should
your
request
look
like
super
important?
Every
time
you
accept
data
from
your
users,
always
without
any
exception
validated.
Otherwise
you
might
end
up
in
a
security
in
a
security
issue
or
creating
a
vulnerability
which
it's
because
of
the
lack
of
proper
input,
validation
which
might
end
up
in
a
command
injection
process.
Scripting-
or
you
know,
god
knows
what
so
I'd
be
very
careful
with
not
validating
data.
A
Then
we
also
have
the
query,
which
is:
how
do
we
fetch
data
from
the
database?
And
this
is
you
know
like
it's?
Not
even
the
fetch.
The
data
is
just
building
the
query.
We
use
a
library
called
sql,
which
we
built
in-house
in
your
form,
which
prevents
sql
injection
by
using
prepared
statement.
Even
look,
even
though,
like
even
though
looks
like
you,
have
just
concatenated
the
string.
The
reality
is
this:
sql
library
will
go,
take
all
these
parameters
and
create
a
prepared
statement
with
it.
A
A
The
same
structure
so
index
test
test,
query
schema
and
it's
the
same
everywhere
so
index
where
schema
and
test.
So
what
does
that
mean?
That
means
that
somebody
jumping
up
on
this
application
does
not
take
long,
because,
basically,
you
just
need
to
copy
and
paste
a
route
immediately.
What's
there
remove
what
he
doesn't
or
she
doesn't
need
and
then
start
coding
around,
so
that
becomes
very
helpful,
then
the
last
repository
I
want
to
talk
to
you
about
is
the
lambdas.
A
As
I
said
before,
orlando's
are
kind
of
like
created
to
support
the
main
workload,
which
is
the
api,
and
if
you
remember,
I
was
talking
about
one
lambda,
which
was
packing
the
the
closed
contacts
into
a
file
and
then
putting
it
putting
it
in
an
extra
book
that
then
would
have
been
served
into
a
customers
via
api
gateway
and
s3.
So
this
is
the
lambda
that
does.
That
is
the
exposures.
Again,
it's
all
open
source.
A
You
can
go
there
and
check
check
what
you
want,
but
this
will
actually
do
that
work
and
it
will
give
us
it
will
give
us
the
required
file,
which
then
will
be
served
via
the
api
gateway
and
the
phones
will
get
the
data
that
they
are
looking
for.
So
that's
the
perfect
usage
for
lambda.
Then
we
use
other
patterns
here
like,
for
example,
you
don't
see
here
an
sms
lambda,
because
every
single
tenant
is
using
a
different
sms
provider.
A
A
The
uk
regions
will
have
other
provider,
which
is
a
property
provider
that
they
build
for
sms
notifications
and
so
on.
The
reality
is
the
message
is
the
same
for
every
single
tenant,
but
how
you
deliver
that
message,
it's
different,
so
that
is
the
couple
using
a
lambda
and
it's
working
very
well
all
the
automation
to
deploy.
This
is
done
in
two
phases.
The
first
one
is
we
deploy
the
infrastructure
and
we
use
github
actions
for
that.
Github
actions
is
fantastic
because
it's
very
close
to
your
code.
It
only
have
one
one.
A
I
will
not
call
it
issue,
but
I
will
call
shortcoming
which
is:
there
is
not
a
manual
validation
step
in
the
middle
between
one
job
and
another.
So
that
means,
if
I
want
to
do
a
plan
on
terraform
and
then
and
apply
out
of
that
plan,
it
becomes
very
hard
because
I
don't
have
this
intermediary
hold
on
step
and
then
apply.
So
what
we've
done
otherwise
is
we
have
a
a
job
which
is
planned
and
then
we
see
the
plan
and
then
another
job
which
will
be
plan
and
apply.
A
A
A
Why
well
for
one
simple
reason:
in
this
project
we
have
separated
the
deployment
and
pretty
much
everybody
who
is
involved
in
the
project
can
do
deployments
at
any
stage,
not
that
we
are
a
big
team.
We
are
like
on
the
biggest
moment,
we
were
like
five
people,
but
we
have
a
very
high
level
of
communication.
We
also
don't
do
deployments
alone
and
that
allows
us
to
deploy
the
infrastructure
and
then
deploy
the
lambdas
without
having
to
redeploy
the
infrastructure
and
same
with
the
acs
target.
A
So
in
that
case
the
lambdas
were
deployed
with
a
github
actions
pipeline,
whereas
the
infrastructure
will
be
another
pipeline.
So
that
way
we
we
kind
of
segregate
what
the
blast
radio
sees.
If
something
goes
wrong
and
again,
some
people
will
be
like.
Oh,
you
should
deploy
lambdas
with
the
terraform
as
well.
But
it's
yes,
you
know.
We
thought
it
was
a
good
idea
and
we
actually
believe
is
still
one
of
the
best
ideas
that
we
we
could
have
taken
so
back
into
the
presentation.
A
Now
so
we
have
learned
a
few
lessons
along
the
way.
The
first
one
is
the
terraform
ecosystem
is
a
mess
if
you
are
using
telephone
third-party
modules.
Territorial
investment
is
not
massive,
but
you
are
getting
yourself
in
a
a
corner
and-
and
I
have
an
example
here
which
is
lds,
there
is
one
module
that
that
creates
an
rds
cluster
and
basically,
what
happened
is
at
a
given
version.
A
That
model
was
calling
the
cluster
default
and
then
one
version
later
the
cluster
was
called
primary
and
secondary.
I,
I
guess
it's
because
some
change
on
the
way
that
rds
deploys
or
similar,
but
what
does
that
mean?
That
means
that
we
have
to
recreate
the
we
have
to
recreate
the
cluster
or
we
have
to
actually
move
the
state
elements
across
and
one
by
one
for
nine
tenants
by
two
environments
pertaining.
So
that
means
18
talents
very
stressful
and
not
very
desired
and
thing
to
do
so.
A
I
would
actually
recommend
and
encourage
everybody
to
write
your
infrastructure
interactive
without
using
third
party
modules,
unless
it's
very
clear
that
the
party
module
serves
one
purpose
and
it
doesn't
go
into
the
wild
because
it
can
get
you
into
a
really
really
bad
corner
and
missing.
The
async
in
one
of
the
first
500s
can
destroy
the
throughput
in
your
cloud
native
system.
So
at
some
point
we
had
containers
starting
turns
out.
A
It
was
we
missed
the
async
in
one
of
the
festival
handlers
and
what
happened
was
that,
of
course,
when
you
throw
an
error
instead
of
resolving
into
a
promise,
it
will
actually
throw
an
error
and
kill
your
javascript
application,
kill
your
node.js
application,
so
the
container
has
to
restart,
and
that
happens
very
often.
Your
throughput
goes
into
the
floor.
So
be
very
careful
with
that,
and
I
wish
there
was
an
easy
way
to
detect
non-asynch
handlers
and
issue
a
warning
or
something
like
that.
A
Well,
because
you
don't
have
alerts
basically,
and
can
you
stop
alerting
me
on
every
request
twice
because
you
have
too
many
alerts
and
it's
incredibly
narrow
that
space
like
where
you're
alerting
is
perfect.
It's
almost
a
non-existent
state.
It's
like
you
know
when
you
do
yoga
or
something
like
that.
This
purity
and
clarity
of
mind
it's
it's!
It's
not
about
the
destination,
it's
about
the
trip.
So
this
is
the
same.
Monitoring
is
not
a
build.
It
once
forgets
and
it
will
always
work
because
it
won't.
A
You
should
always
have
two
monitoring
levels,
infrastructure
and
app
monitoring.
So,
for
example,
what
happens
if
your
node
event
loop
starts
having
delays,
you
won't
catch
that
with
the
infrastructure
monitoring.
But
if
your
database
is
down
your
application
is
going
to
fail,
but
you
probably
will
need
to
monitor
that
on
the
infrastructure.
A
So
if
something
is
wrong,
we
can
catch
it
very
quickly
and
we
can
actually
act
very
quickly
so
the
other
day.
I
actually
amazed
myself
because
I
managed
to
go
from.
I
am
looking
into
something
else
and
into
all
this
one
alert.
Let
me
look
into
that
in
about
15
seconds,
because
we've
gotten
so
good
with
cloud
watch
that
it
gets
up
to
a
point
where
it's
almost
like
an
extension
of
your
hands.
A
A
My
advice
is:
if
you
can
slice
them
vertically,
in
countries
or
in
regions
or
in
user
groups,
it's
going
to
make
your
life
a
lot
easier,
and
if
I
tell
you
we
are
processing
85
millions
of
requests
a
day.
You
will
be
like,
oh
my
god,
that's
a
lot,
but
well
actually
it's
more
than
85,
it's
like
a
few
hundred
but
yeah.
If
I
tell
you,
we
are
processing
5
millions
of
requests
a
day
80
times
it's
not
super
impressive,
because
5
millions
of
requests
a
day
is
pretty
much
manageable,
with
two
servers.
A
So
that
is
something
that
I'm
grateful.
The
approach
wasn't
global
because
otherwise
having
to
manage
a
big
system,
it
it's
actually
much
harder
than
managing
a
smaller
system,
especially
if
you
are
using
infrastructure
as
code
and
repeatable
infrastructure,
which
is
yes,
the
overhead
is
minimal,
so
yeah.
I
would
recommend
you
to
slide
your
system
vertically
and
be
the
master
of
your
trade
and
apprentice
of
the
rest
of
them.
A
That's
devops,
so
you
you
need
to
focus
in
one
area
like
me,
for
example,
infrastructure,
but
also
be
able
to
read
and
understand,
node.js
and
sometimes
write
it
and
because,
basically
like
you,
cannot
isolate
yourself.
If
you
want
your
team
to
succeed
and
that's
about
it.
Thank
you
very
much.
This
is
my
email.
That's
my
twitter
handle
my
linkedin.
Is
there
of
course
feel
free
to
connect
with
me
and
like
as
this
is
being
recorded?