►
From YouTube: Community Engineering Hangouts. May 19, 2021
Description
Agenda:
- “Migration to jQuery 3.5.x. Benefits and challenges” by Sergii Ivashchenko
- “Cloud Managed Services Support in 2.4.3 and further” by Yevhenii Pyltiai
A
B
B
B
B
B
B
This
update
is
also
not
so
straightforward
and
what
we
are
going
to
do
in
scope
of
this.
First
of
all,
we
are
going
to
work
in
2.4,
develop
branch.
We
actually
have
already
delivered
some
changes
to
the
code
related
to
jquery
upgrade
there,
so
you
can
watching
that
to
for
develop
branch.
You
will
see
the
updates
that
are
going
on
and
right
now
we
are
working
on
the
code
base
preparation.
B
The
new
version
of
jquery
has
quite
a
few
breaking
changes.
Comparing
with
the
older
version,
that's
expectable,
considering
the
the
differences
in
versions,
so
the
preparing
code
base
is
basically
updating
the
code
we
are
using
with
jquery
to
be
compatible
with.
This
is
the
latest
version.
Unfortunately,
it
is
possible
to
keep
more
to
keep
almost
all
the
code
compatible
with
boss,
1,
12
and
and
3
e6.
A
B
B
B
That's
also
that
brings
the
work
with
jquery
defers
up
to
standards,
but
also
brings
a
lot
of
backward
incompatible
changes
about
which
we
will
talk
a
bit
later
in
this
presentation.
So,
basically,
as
a
simple
example,
if
previously
sending
the
ajax,
we
had
the
ability
to
specify
that
the
done
and
fail
function
that.
B
That
is,
and
in
this
case,
if
the
callback
specified
for
them
is
throwing
an
exception,
we'll
be
able
to
actually
handle
that
there
are
a
couple
of
additional
improvements
to
handling
exceptions
as
well
yeah.
So
here
I'm
just
going
to
give
you
a
slight
overview
of
several
several
features
and
several
backwards
and
incompatible
changes
that
I
think
are
the
the
most
effective
and
as
well
as
a
short
list
of
a
bit
less
impactful
backward
and
compatible
changes
and
features
at
the
end.
B
The
update
for
jquery
for
your
javascript
projects
previously
and
you
faced
some
specific
change.
You
see,
you
see
some
specific
challenging.
Please
share
this
experience
with
us
all.
Let
add
other
comments
to
this
meeting,
so
the
second
feature
is
kind
of
simplifying
the
work.
We
probably
very
frequently
use
to
query
the
jquery
post
functions
that
is
allowing
to
pass
the
or
the
settings
object
with
the
parameters
for
these
functions.
B
B
B
One
thing
that
was
improved
is
that
in
in
the
latest
jquery
we
have
the
ability
to
catch
exception
from
the
ready
callback
from
document
from
the
jquery
radical
back
right.
So
previously,
these
errors
were
not
possible
to
catch
and
basically
they
will
be
thrown
and
shown
in
the
console
in
the
new
version.
There
are
even
two
ways
to
do
this.
B
B
C
B
B
B
But
we
use
these
improvements
with
the
fixes
with
the
performance
and
optimizations
in
the
new
jquery.
There
are
actually
a
lot
of
breaking
changes
that
were
introduced
a
lot
of
backwards
and
compatible
changes
that
have
to
be
handled
on
our
on
our
site.
If
you
would
like
to
move
to
the
new
library
version
and
first
of
all,
as
I
mentioned,
promises
the
signatures,
so
the
the
callback
functions
have
changed
and
for
iax
that's,
I
think
that's
the
most
common
in
magento
code
base
from
my
from
my
experience.
B
So
previously,
when
calling
niaccs
and
specifying
the
callbacks,
we
have
used
successor
and
complete
functions,
and
now
that's
done
fail,
and
always
so,
while
successor
and
complete
callback
functions
are
not
going
to
work
in
the
new
jquery
version,
the
if
these
functions
are
defined
in
the
settings
object.
So
if
you
are
passing
an
object
to
a
yaks
instead
of
calling
the
functions,
you
can
still
use
use
these
names
as
keys
in
in
the
object
like
successor
and
complete,
to
specify
callbacks.
B
B
Is
specified
as
one
tag
instead
of
two
tags,
the
jquery
will
transform
it
into
two
tags.
So
this
example
here
jquery
from
div,
self-closing
and
sponsor,
send
self-closing
will
result
into
the
the
expected
div
and
then
spawn,
but
in
jquery
3.
since
jquery
3.5.
This
conversion
is
not
taking
place
anymore,
so
the
default
html
behavior
is
for
the
tags
that
are
not
self
closing
is
just
percept
them
as
an
opening
tuck
in
this
case
we'll
have
opening
dock
attack
of
div
and
opening
tuck
of
spawn.
B
B
B
B
B
B
B
If
you
are
going
to
take
the
value
from
that
multiple
select
in
jquery
1,
it
will
return
null
in
jquery,
3
5.
It
will
return
3536.
It
will
return
the
empty
array.
So
in
case
there
are
some
checks
later
on
it.
It's
worth
to
pay
attention
to
this
one,
so
one
interesting
change
of
behavior
of
hidden
and
visible.
B
B
B
B
B
I
don't
think
that
will
affect
the
clients
of
jquery,
but
I
do
believe
that
affects
the
development
of
jquery
and
yeah,
so
document
ready
handle
handlers
are
now
asynchronous
and
lots
of
other
smaller
backward
and
compatible
changes,
while
not
so
many
functions
have
been
removed.
There
are
lots
of
deprecated
functions
so
now
on
jquery,
and
you
can
see
the
list
here.
B
B
B
After
some
time,
lots
of
points
will
be
used
and
lots
of
bind
calls
will
be
used
and
if,
from
the
beginning,
like
early
you're
going
to
switch
those
new
functions
that
are
suggested
by
jquery,
then
that
will
that
will
be
a
good
example
for
the
future
development
as
well
and
in
the
end
you
will
need.
You
will
have
to
deal
with
less
of
updates
for
the
project
transmission
to
the
next
version,
so
the
things
that
are
useful
to
prepare
for
the
new
jquery.
B
B
B
It
looks
like
like
if
you,
if
you
will
navigate
just
to
block
jquery.com,
you
will
see
straight
away
all
the
blog
posts
of
for
for
all
the
releases
describing
the
changes
right
there
on
the
left
side
on
their
block.
And
finally,
there
is
an
api.
There
is
a
good
api
documentation
for
jquery.
That
also
mentions
all
the
changes
like
if
you'll
try
to
look
for
function
that
is
removed
or
is
deprecated
in
this
new
version.
B
If
you
click
on
removed
label,
you
will
see
all
the
removed
all
the
removed
functions
and
properties.
It's
also
helpful
and
finally
watch
24
develop
range
with
updates
and
also
stay
tuned
for
our
updates.
As
as
we
will
go
through
these
upgrade
process,
we
are
going
to
share.
We
would
like
to
share
information
with
you
as
frequently
as
possible.
Thank.
B
B
A
B
Is
going
to
be
quite
quite
a
big
and
backward
and
compatible
tasks
task
for
us,
and
I
don't
think
there
are
too
much
benefits
from
that.
Personally,
that's
that's
a
short
answer,
but
we
can
discuss
it.
If
you
have
the
preposition
on
how
jquery
can
be
replaced
in
magento
with
something
else,
we
are
always
open
for
discussion.
D
Okay
cool,
so
in
terms
of
why
upgrading
just
a
little
bit
cover
on
that,
so
we
do
have
definitely
concerns
to
the
previous
versions
of
the
jquery,
including
security
one,
and
we
must
we
are
required
to
address
security
concerns,
at
least
that,
but
again,
the
other
thing
that
we
already
mentioned
today
on
the
upgrading
front,
removing
entire
jquery
from
magento.
It's
a
big
question
yeah.
By
the
way,
let's
see
we
have
iguana,
I
love
the
call
so
eager.
D
B
B
We
are
going
to
simplify
that
update,
as
as
as
we
can
like,
providing
the
the
probably
some
some
tests
from
our
side,
but
right
now
the
the
work
that
is
being
done
into
for
develop
is
completely
backward
compatible.
We
are
updating
the
code
base
in
a
way
that
it's
compatible
with
the
old
version
and
the
new
version.
B
B
B
C
B
B
A
E
E
E
Awesome
so
I'll
try
to
be
quick,
since
we
don't
have
too
much
time
left.
But
basically,
what
we
wanted
to
talk
today
about
is
introduction
of
official
support
for
cloud
managed
services
and
at
this
time
it's
we're
talking
about
aws
and
actually
see
some
people
who
already
probably
seen
this
content
on
the
summit
hackathon
we
did
with
aws
team.
E
So,
basically,
starting
with
our
strategy,
we
are
trying
to
basically
provide
the
most
scalable
platform,
support
and
massive
traffic
for
large
organizations,
large
catalogs
and
still
you
know,
providing
proper
security
and
performance
at
the
same
time,
so
that
we
don't
make
those
kind
of
tradeoffs
that
we
actually
need.
You
know
to
sacrifice
performance
to
host
bigger
catalogs,
or
vice
versa,
so
we're
trying
to
find
solution,
basically,
which
will
provide
best
performance
at
the
same
time
with
whatever
catalog
or
other
settings
you
you
may
want
to
configure
and
start
inside
your
magenta.
E
So
we
worked
with
aws
very
closely
to
basically
introduce
official
support
into
magento
for
the
services
you
see
on
the
screen,
so
we
basically
took
each
service.
We
are
using
like
database
elastic,
search,
radius
and
others
and
selected
one
one
of
them
managed
services
on
aws
site,
which
we
find
fits
best
for
the
purpose,
so
mariah
debuted,
my
sequel,
will
go
to
aurora.
Basically,
elasticsearch
remains
to
be
an
elastic
surge,
but
it's
a
managed
one.
E
Elastic
cache
is
going
to
kind
of
replace
radius
or
I
mean
not
replace
but
basically
be
an
alternative
to
radius.
Aws
recently
released
managed,
ribbitum
queue
which
wasn't
available
before,
which
is
great,
because
previously
we
had
only
the
sqs
option
and
that
required
actual
additional
development
in
magento.
E
So
repeat:
mq
basically
works
natively
and
so
far
we
didn't
find
any
issues
and
definitely
s3
for
some
media
storage,
some
static
content
and
things
like
that.
So
a
lot
of
these
things
were
used
previously
by
some
partners
and
customers,
but
we
never
supported
it
official,
the
meaning.
You
know
whatever
issues
maybe
might
have
been
happening
there.
We
couldn't
really
look
into
that
and
that
helped
much,
but
now
we're
basically
within
the
last
few
versions.
E
We
are
trying
to
basically
get
to
a
point
when
we
can
confidently
say
that
the
services
are
supported
and
you
can
build
your
stack
on
top
of
them
and
definitely
it
may
take
some
time
to
kind
of
polish
everything
and
make
sure
that
you
know
in
production.
It's
performance
the
way
we
expect
and
actually
kind
of
model
test
all
of
these
services,
but
testing
each
one
of
these.
We
basically
seen
good
improvements
here
and
there
in
terms
of
performance
stability.
E
A
A
E
A
E
You
probably
have
the
chance
to
actually
look
at
it,
or
at
least
there
were
a
few
presentations
about
it
from
our
team,
so
you
may
have
heard
that
it's
there
not
sure
if
you
had
time
to
actually
try
it,
but
but
it's
there
in
two
four
three
we're
adding
a
few
upgrades
to
us
for
implementation.
Basically
based
on
some
feedback,
we
got
and
some
additional
like
tech
depth
we
had
so
243
has
more
polish
test
reintegration
with
some
additional
performance
improvements
and
some
other
stabilization
things.
E
E
So
there
are
a
few
things,
basically
that
are
still
to
be
resolved.
As
you
may
understand,
these
services
are
often
a
little
bit
behind
on
the
service
versions.
So,
for
example,
aurora
doesn't
support
mexico
8
at
this
point
yet,
but
luckily
we
have
kind
of
support
for
earlier
versions,
and
you
know
things
like
that,
but
basically
we've
tested
out
all
of
this
and
are
also
building
like
automation,
now
to
actually
prove
that
these
things
work
continuously.
So
you
know
either
it
will
be
like
pull
request,
or
some
overnight
builds.
E
I
guess
the
important
part
to
to
the
audience
here
is
what
the
impacts
to
future
releases
and
extensions
that
we
have.
So
you
know
it's
kind
of
up
to
you.
If
you
want
to
to
use
those
or
not,
we
still
retain
all
the
previous
options
we
had
like
just
hosting,
for
example,
mexico
or
radius
or
elasticsearch
like
on
your
instances
or
you
can
go
with
managed
services,
but
for
future
releases
there
are
a
few
impacts.
E
Basically,
so
there
is
additional
compatibility
testing
scope,
so
you
know
if
you're
contributing
to
requests
or
contributing
code
to
magento-
or
you
know
just
looking
at
some
like
compatibility
challenges,
so
basically
we're
now
at
an
additional
test,
and
for
that
so,
for
example,
as
I
said
like
my
sequel,
8
is
not
supported
yet
in
aurora,
and
it
would
mean
that
you
know
the
implementation.
If
something
is
being
done,
basically
needs
to
work
with
aurora
as
well.
It's
not
it's
not
possible
anymore.
E
To
do
it
just
for
for
mexico,
or
my
idb
will
actually
need
to
be
consistently
making
sure
seems
like
managed
services
work
it's
more
on
our
site
than
on
your
side,
because
we
basically
will
be
having
those
automation
testing
in
place,
but
it's
definitely
like
additional
scope
of
testing
for
us,
so
we
may
maintain
compatibility
with
multiple
versions
of
services,
so
you
know,
for
example,
in
like
two
four
x
versions.
We
would
say
you
know
we
support
mysql
eight.
Only,
but
it's
not
the
case
anymore.
E
As
I
mentioned,
it
will
be
part
of
our
development
practices
and
in
back
to
extensions.
So
there
are
a
few
things
to
keep
in
mind
if
you
are
heavily
relying
on
something
like
elasticsearch
in
your
extensions
or
you
know
similar
similar
things
like
elasticsearch
plugins.
You
know
there
may
be
some
compatibility
challenges
so
managed
services.
They
are
definitely
having
lots
of
benefits.
You
know
like
performance
as
we
discuss
scalability
out
of
scale
and
easier
upgrades.
E
All
of
that,
but
at
the
same
time,
all
of
these
benefits
come
with
some
cost
and
basically
that
cost
is
some
challenges
with
availability
of
like
plugins
or
similar
things
in
different
services.
So,
for
example,
if
you
look
at
the
elasticsearch
plugin
list
on
managed
elasticsearch,
it
will
be
shorter
than
what
you
would
expect.
You
know
to
see
from
a
hosted
elastic
search.
E
Finally,
I
guess
it's
just
a
general
recommendation,
but
it
would
be
good
to
make
sure
like
any
extensions
or
customizations
developed
are
compatible
with
managed
services,
because
customers
once
they
realize
sorry,
it's
my
customers
once
they
realize
the
benefits
of
these
things,
they
will
be
asking
you
probably
to
move
them
to
the
managed
services.
You.
A
E
A
E
So
it's
a
good
question.
So,
basically,
as
I
said,
you
know,
we
not
always
were
actually
introducing
changes,
but
we
were
mainly
making
sure
things
work
so
for
database.
For
example,
we
had
to
make
changes
because
there
were
things
that
were
not
compatible
with
aurora,
so
there
are
changes
for
database
compatibility
for
elasticsearch.
Specifically,
it
worked
as
is
so.
There
were
no
changes
in
elasticsearch,
except
that
we
made
sure
that
we
are
not
using
any
kind
of
plugins
by
default
that
are
not
compatible.
E
That's
the
versions
line
that
we
have
a
proper
automation
in
place
to
kind
of
make
sure
the
quality
of
of
our
integration
stays
intact
over
time
and
similar
things.
So
the
support
was
like
interesting
because
it's
not
about
like
huge
amount
of
code
contributing,
but
about
huge
amount
of
processes
aligned
and
like
automation
and
testing
done
and
similar
things.
So
we're.
Basically
you
know
sure
we
can
say
now.
We
kind
of
officially
support
those
starting
to
foresee,
but
doesn't
necessarily
mean
we
introduced
a
lot
ton
of
culture.
F
Yes,
thank
you,
hello.
Can
you
hear
me
yeah
yeah
yeah.
Thank
you
for
a
nice
presentation.
It's
really
interesting
because
aws,
just
like
maybe
just
the
future
of
the
clouds
and
the
magenta.
From
my
point
of
view,
it's
very
powerful
servers,
but
you
have
two
questions
related
to
the
instance
types.
So
you
took,
you
presented
the
idea
of
auto
scaling
and
I'm
worried
about
the
instance
type
you
will
suggest
for
customers.
E
Yeah,
so
we
are
still
we're
still
documenting
all
of
that,
because
different
different
services,
basically
depending
on
what
they
do,
they
need
different
instance
types.
So
in
in
previous
architecture,
basically
we
were
having
two
instance
types
that
were
like
c-series
and
m-service
for
web,
and
this
is
all
the
other
services
respectively,
but
in
new
world,
when
we
get
these
auroras
and
everything
else,
there
may
be
some.
You
know
our
service
involved
or
some
t-series
involved
here
and
there,
because,
basically,
not
all
services
need
to
be.
E
You
know
huge
by
default
and
they
may
be.
You
know
like
in
percentage
of
lot.
I
would
say
you
know
they
can
be
consuming
less
resources
and
others.
So
I
I
cannot
tell
you
right
now.
I
guess
the
exact
instance
types
it's
something
that
needs
to
be
tested
depending
on
what
exactly
what
exactly
you're
trying
to
implement,
but
we
will
have
some
recommendations
over
time.
F
Yeah,
thank
you.
Thank
you.
So
much
and
I
have
one
more
question
about
the
elasticsearch
service.
You
know
that
it
provides
a
lot
of
security
settings
and
I
wonder
if
you
will
provide
any
maybe
instructions
how
to
set
up
this
elasticsearch
service.
Just
according
to
the
base
magenta
installation
yeah,
it
will
be
really
nice
and
of
course,
if
you
will
provide
any
sync,
like
maybe
easy
tools
for
configure
the
aws
environment,
it
will
be
really
great
because
the
aws
provides
a
lot
of
fun
stuff
from
the
cli.
F
E
Yeah
sure
so
ec
tools
does
support
it
already.
It
was
released
as
part
of
the
last
release,
so
we
didn't
put
that
kind
of
any.
You
know
big
notice
about
that
anywhere
yet
because
you
know
we're
still
polishing
things,
but
dc
tools
had
some
incompatibilities
basically
because
compared
to
the
local
installation
we
needed
to
like
pass
over
the
end
points
and
like
credentials
and
all
that
other
stuff,
so
we
fixed
all
of
that
and
actually
tools
now
supports
it.
F
E
Thank
you
and
yeah,
just
just
just
to
add
to
that
on
on
setting
up
the
the
the
services.
Basically,
the
team
is
working
now
on
actual
documentation
how
to
do
on-prem
installation,
because
you
know
that's
basically
where
we're
starting
from
to
to
get
more
data
on
basically
how
how
things
work,
and
once
things
are
polished,
you
know
we
will
be
using
like
pc
tools,
documentation,
but
I
mean
if
you,
if
you
want
to
look
into
what
was
done
in
last
release.
E
F
D
I
just
want
to
add
a
little
bit
on
the
open
source.
So,
as
you
know,
like
a
two,
four
three
release
is
going
public
better
soon.
I
believe
early
june
will
have
probably
better
for
two
for
three,
so
you
will
be
able
to
try
out
all
this
nice
stuff
which
we
were
talking
about
so
but
please
keep
watching
the
communication
and
updates.
Also,
we
have
schedule
for
the
public
beta
and
ep
on
our
dev
docs
website.