►
From YouTube: Cloud Native Talks #6 (Online Meetup)
Description
We are glad to invite you to the Cloud Native Talks #6 (Online Meetup) hosted by Cognitive.
Please make sure to subscribe and enable channel notifications for any updates and early announcements.
Follow us on Twitter (https://twitter.com/CNKPoland) & Facebook (https://www.facebook.com/cnkubernetes...).
More information about the Cloud Native Warsaw Conference: http://cloudnativewarsaw.com/
Thanks to the generosity of our sponsors we have 50 tickets with a 50% discount. Use this code: 'CN&K8sC50' here: https://evenea.pl/event/cloudnativeco...
Choose workshops that interest you!
https://evenea.pl/event/cloudnativewo...
Sign up to the Cloud Native & Kubernetes community Slack:
https://bit.ly/2DKBxJ1
Agenda:
00:01 - Introduction
02:00 - Piotr Bochynski "Modernize your applications in a cloud-native fashion with Kyma" + demo (EN)
52:04 - Q&A session
Direct contact with organizers: community@cognitive-cs.com
Useful links:
If you want to reproduce the demo from the talk you can follow this blog post: https://kyma-project.io/blog/2019/7/8/extend-wordpress
Kyma blog: https://kyma-project.io/blog
Kyma Roadmap: https://kyma-project.io/roadmap/
SAP blogs about Kyma: https://blogs.sap.com/tag/kyma/
Become a Contributor
Request a feature or report a bug:
https://github.com/kyma-project/kyma/
Join the CORE SIG
https://github.com/kyma-project/community/tree/master/sig-and-wg/sig-core
Contact the Kyma team directly on Slack
https://bit.ly/2JUX1XS
B
A
My
name
is
ELISA
and
I'll
be
your
host.
For
this
event,
our
speaker,
Peter
Bowman
ski,
has
been
working
in
software
development
for
many
years,
always
involved
in
this
research
and
development
topics.
For
the
last
eight
years
he's
been
building
cloud
services,
services
as
a
developer
and
an
architect
currently
works
in
an
open
source
schema
project
as
a
chief
product
owner.
A
Please
note
the
following
upcoming
events.
During
summer
we
plan
to
organize
more
cloud
data
talks.
We
will
post
more
information
soon
so
stay
tuned
and
follow
the
cloud
native
and
kubernetes
community
on
social
media.
All
links
are
in
the
description
below
the
video.
Of
course,
you
can
buy
tickets
to
the
cloud
native
course
or
conference,
which
will
be
on
the
9th
and
10th
of
September.
There
are
workshops
alongside
the
conference
where
you
can
learn
communities
and
go
thanks
to
the
generosity
of
our
sponsors.
We
still
have
tickets
to
the
conference.
B
Hello,
guys
yeah
so
I,
already
thud
hello
in
the
YouTube
chat,
I
hope
you
can
see
that
I
would
like
to
have
some
interactive
session.
Of
course,
if
you
wish
so
we
can
ask
questions
in
the
chat.
I
will
try
to
watch
them
also
in
the
meantime
and
answer
them
today.
Topic
is
a
modern
how
to
modernize
your
application
in
a
cloud
native
fashion,
so
cloud
native
is
a
hot
topic.
You
are
here
because
you
are
interested
in
that
topic.
Kubernetes
is
just
the
example.
B
Cloud
native
is
much
much
bigger
word
and
today,
I
will
give
you
a
guide.
How
we
in
kheema
project,
see
how
we
can
bring
this
cloud
native
word
to
the
applications
you
have
in
your
house
in
your
company
and
you
have
to
somehow
modernize
and
maintain,
and
it's
not
your
own
green
field
development
that
you
always
have
the
possibility
to
choose
the
environment.
You
work,
but
you
need
to
work
with
the
applications
that
exists
for
a
longer
time.
So
first
I
would
like
to
introduce
your
keema
c'mon
kima,
what
it
is.
What
is
it?
B
Thank
you.
My
is
an
open
source
project
designed
for
kubernetes.
So
we
do
not
hide
kubernetes.
Kheema
is
built
on
top
of
kubernetes
and
contain
a
lot
of
contains
a
lot
of
applications
from
the
cloud
native
landscape
and
that
that
are
heavily
used
in
the
kubernetes
world.
We
added
a
couple
of
things
on
top
of
government
is
to
make
extensibility
of
applications
easier.
B
What
does
schema
mean?
Kheema
is
a
greek
word,
meaning
wave,
and
so
we
are
following
the
Greek
convention
in
kubernetes
word.
So
kubernetes
is
my
Greek
name
for
for
the
pilot
for
the
guy
course
driving
the
ship
and
kima
is
a
wave,
so
it's
yeah
it
works
together
and
what
what
challenges
kima
actually
solves
in
few
sentences.
I
would
like
to
justify.
Why
why
we
started
the
project
at
all.
So,
first
of
all,
and
the
challenge
that
we
address
is
that's
in
ever
average
company.
B
You
have
too
many
systems
with
different
infrastructure,
with
different
products,
from
different
vendors
and
integrating
them,
and
extending
them
is
just
a
hard
task
with
these
systems.
Also
the
risk
comes
here,
so
you
have
many
scenarios
and
you
want
to
learn
something
by
doing,
and
sometimes
you
can
destroy
some
applications
during
this
learning
curve.
B
Sometimes
it's
also
slow.
So
if
you
have
in-house
uhm,
monolid
applications
or
not
modern
applications
that
are
developed
as
micro
services
and
development
cycle
can
be
a
long
and
heavy.
So
adding
new
features
can
cost
that
you
need
to
wait
an
on
maybe
quarter
for
the
next
release
to
see
your
improvements
or
your
extensions
other
things
that
we
are
targeting
and
we
want
to
simplify
this
complex
access
to
the
services,
both
from
cloud
providers
and
from
for
services
that
are
hosted
on
premise
in
your
data
center.
B
So
we
heavily
use
Service,
Catalog
concept
to
really
manage
this
services
in
a
simple
and
easy
way.
Another
thing
somehow
mentioned
before
menorahs
gets
too
big,
so
it's
not
only
slow
to
develop
that,
but
some
it
becomes
just
unmanageable.
So
complicated
number
of
steps
that
you
need
to
to
apply
in
order
to
deploy
your
application
and
changes
are
really
spread
across
the
big
codebase.
B
This
is
really
something
you
do
not
want
to
deal
with,
especially
if
you
have
many
such
systems,
so
this
is
really
complex,
stuff
and
the
final
I
think
that
if
you
want
to
get
rid
of
this
Manolis
and
go
to
the
cloud
native
and
develop
your
applications,
your
new
features,
it's
going
to
the
cloud
native
word
is
not
also
easy.
Kubernetes
itself
is
a
complex
beast.
All
the
other
applications
that
are
in
the
Kuban
CN
CF
landscape,
so
cognitive
computing
foundation,
landscapes
are
complex
there.
B
B
How
do
we
do
that?
First
of
all,
we
introduce
the
concept
of
application
connector.
What
is
it
application
connector
is
is
something
we
developed
as
an
abstraction
that
allows
you
to
treat
your
legacy
application,
your
monolith
or
your
application
from
external
vendors
as
a
service
like
a
cloud
service,
mainly
so
you
can
have
instances
of
that
applications
injected
in
your
kubernetes
environment.
B
You
can
see,
and
even
stream
from
these
applications,
you
can
call
the
API
so
of
these
applications
in
easy
and
secure
way,
so
establish
kind
of
trusted
connection
to
that
applications
and
we
bring
the
developers
just
convenient
way
to
interact
with
this
application
without
taking
care
about
the
security
getting
tokens,
setting
up,
client
certificate
or
other
credentials.
This
is
done
by
application.
Connector.
B
Another
thing
we
introduce
is
serverless.
We
have
so
serverless
is
the
password
number
one
right
now
in
the
industry,
but
what
we
do
is
we
treat
our
extensions
as
as
functions
you
want
to
deploy
and
you
can
easily
use
also
kubernetes
cluster
to
host
these
functions,
so
you
can
focus
on
the
business
logic,
right,
write
the
code
and
then
the
deployment
the
operations
is
just
scheduled
by
them,
but
the
serverless
engine
on
top
of
kubernetes
cluster
right
now
and
we
are
cooperating
with
the
key
native
project.
B
If
you
know
that
project,
it's
project
started
by
Google,
that
is
offering
the
serverless
framework
for
kubernetes
and
also
for
standalone
usage
like
google
cloud
run,
and
we
have
it
also
in
Hema,
and
the
last
pillar
of
our
features
is
the
service
management.
So
indeed,
in
this
area
we
integrated
kubernetes
service
catalog.
So
this
is
the
implementation
that
brings
providers
that
implement
open
service
broker
API
into
into
kubernetes.
You
can
see
the
catalog
of
services
from
different
cloud
providers
and
provisioned
and
instantiate
them
binded
them
to
your
code
easily
without.
C
B
Taking
care
of
all
of
the
complexity
and
related
to
that
part,
and
one
slide
about
the
architecture.
So
now
you
can
see
what
how
kima
is
built,
what
are
the
boundaries
of
of
kima?
So,
on
the
left
hand
side
you
can
see
the
applications
that
we
integrate.
So
this
is
any
business
solution
and
the
on-premise
application
and
a
cloud
application
you
want
to
interact
with,
extend
it
and
we
we
through
the
application
connector.
B
We
import
events
from
from
that
application
and
we
enable
and
calling
API
so
of
these
applications
with
easy
way
and
of
course,
you
are
able
to
call
ap
API
hosted
in
the
keema
in
the
kubernetes
cluster.
Also
from
this
application
in
the
safe
way,
on
the
right
hand,
side
you
have
any
open
service
broker
service
provider.
So
right
now
we
have
open
service
brokers
for
a
drawer
for
AWS
and
for
Google.
B
So
all
these
free,
big,
hyper
scalars
have
open
service
brokers
that
exposed
the
services
they
offer
in
the
consistent
API
that
is
consumable
by
Service,
Catalog
and
so
combining
applications
and
the
cloud
services
in
your
code.
So
you
run
the
function
here
on
top
of
key
native,
and
if
you,
if
you
combine
all
these
things,
you
need
to
just
write
this
code
here
and,
and
you
don't
have
to
really
touch
the
on-premise
solution
or
or
any
solution
mano
lead
applications
to
already
realize
some
extensibility
scenarios.
B
Of
course,
on
top
of
that,
we
have
a
lot
of
things
that
are
coming
with
the
best
applications
from
cloud
native
landscape.
So,
for
example,
whatever
you
you
write
in
the
in
the
business
logic
it's
running
together
with
from
it
use
graph,
Anna,
Jaeger,
SEO,
service,
mesh
and
other
components
that
really
gives
you,
the
observability
monitoring,
logging
and
and,
for
example,
managing
external
access,
so
micro,
API
gateway.
These
things
are,
you
are
getting
for
free.
We
in
kima
project
just
integrate
all
these
best
tools
in
this
cloud
native
landscape
into
nice.
B
That
install
schema
and
the
kubernetes
cluster
and
we
can
run
on
any
kubernetes
cluster
actually,
so
we
have
compatibility
plans
for
GCP
and
a
sure
for
many
others
of
GE
and
aks.
We
can
run
also
on
any
kubernetes
cluster,
that
is
in
the
version
112
or
above
so
this
is
yet
prerequisite
the
requirements.
B
We
have
I
think
that
that's
main
point
of
the
architecture
and
yeah,
so
what
kima
does
is,
is
really
gluing
all
these
components
from
cloud
native
landscape
plus
a
couple
of
things
like
application,
connector
that
simplify
their
usage,
but
we
do
not
write
own
components
to
too
many
own
components,
because
we
believe
that
for
certain
aspects
there
are
already
best
components
available
and
we
do
not
have
any
need
to
write
them
again
and
again.
So
so,
for
example,
we
do
not
want
to
have
own
path
or
our
infrastructure.
We
utilize
kubernetes
for
authentication.
B
We
use
index
component
initially
coming
from
Korres
and
right
now
it's
given
to
the
community
for
integration
of
API.
We
use
open,
API
specification,
open
API
in
this.
You
probably
know
it
as
a
name
of
under
the
name
of
swagger
as
an
API
is
the
new
specification
that
is
bringing
the
same
standard
to
a
synchronous
API,
so
even
based
api's
and
open
service
broker
is
already
mentioned,
is
using
service
catalog
to
provision
services,
of
course,
in
the
monitoring.
B
B
We
use
Minah
to
store
contents
of
this
API
specification.
Documentation
that
you
have
for
your
services
are
stored.
Err.
We
use
e
Co
as
a
service
mesh,
which
brings
our
apart
from
the
mentioned
before
API
micro
gateway,
mutual
TLS,
so
security
in
the
cluster
and
all
these
observability.
So
you
see
and
traffic
we
can
without
the
writing
any
code.
And
of
course
we
have
awesome
eventing
in
the
in
the
key
Mizuki
myspace
menu
on
a
synchronous
programming
model.
B
So
we
believe
that
this
is
a
way
to
to
go
with,
with
a
synchronous,
will
work
load
in
the
kubernetes
cluster
because
it
scales
better
and
we
integrated
creative
project
mentioned
before,
and
we
also
contributed
to
K
native,
not
as
a
messaging
system,
which
we
believe
is
really
nice
solution
now
time
for
for
extensibility
scenario
and
how
all
these
components
can
be
used
in
maybe
not
real-world
scenario.
But
the
scenario
that
is
easy
to
explain.
So.
B
Let's
assume
that
we
have
some
requirements
for
the
extensibility
I
want
to
have
a
block
for
my
products.
This
block
will
be
wordpress
based,
I
want
to
have
in
my
blog
site,
I
want
to
publish
in
comments
immediately,
but
only
those
with
the
positive
message.
I
want
to
scale
my
code
horizontally,
I
want
to
have
monitoring
tracing
a
nice
dashboard
and
I
can
write
PHP
code,
which,
for
a
WordPress,
can
be
difficult.
If
you
want,
you
can
help
me
in
this
demo
going
to
the
WordPress
a
demo
kheema
pro.
B
You
have
QR
code
here
and
maybe
I
can
even
pass
the
link
in
the
chat
in
the
meantime
and
I
have
in
that
site.
Already
block
WordPress
sites
published
and
I
will
show
you
how
we
can
do
that
with
kima.
In
the
meantime,
I
see
some
question
from
the
audience.
I
will
read
it
if
I
understood
correctly.
In
this
case,
mono
application
is
not
migrated
to
cloud,
but
your
solution
integrates
with
it
by
application,
connector
and
only
kima
is
running
in
cloud.
Yes,
that's
right.
B
There
are
many
applications
in
the
world
that
are
not
so
easily
deployed
to
the
cloud,
but
my
example:
I
will
show
in
a
minute
WordPress
actually
I
hosted
it
in
the
cloud
also.
So
it's
hospitals
on
the
kubernetes,
so
you
are
not
limited,
but
we
focus
on
connectivity
to
data
application,
not
hosting
the
application
itself.
I
hope
that
I
answered
that
question.
Let
me
switch
quickly
to
the
live
demo,
so
I
have
here
kima
installed,
and
this
schema
instance
has
the
code
to
do
the
scenario
I
presented
in
the
requirements.
B
B
C
C
B
B
This
is
yeah
what
I
wanted
to
achieve
in
the
short
demo,
but
demo
is
more
for
entertaining.
So
we
can
try
on
your
own
how
artificial
intelligence
of
positive
and
negative.
The
message
is
positive
or
negative
works.
Now.
I
will
switch
quickly
to
the
code
and
show
you
how
I
did
it
and
what
is
required
on
the
kima
site
to
enable
that
stuff
in
WordPress
okay.
So
this
is
the
main
view
you
end
up
when
you
install
kima,
so
kima
gives
you
also
nice
web
UI,
all
the
things
you
do
in
kima.
B
You
can
also
do
from
command
line
from
keep
CTL
and
him
a
command
line.
I
will
come
back
to
that
later,
but
this
UI,
actually,
I
think,
is
really
cool
and
allows
you
to
manage
your
extension
logic
and
your
binding
to
two
applications
from
this
in
the
convenient
way.
So,
let's
start
with
how
this
schema
instance
actually
knows
about
WordPress,
and
so
in
the
application
section
I
have
the
WordPress
application
created,
and
this
WordPress
application
is
serving
some
api's
and
serving
some
events
and
is
bound
to
the
names
by
to
the
default
namespace.
B
What
does
it
mean
that
it
is
bound
that
it
means
that
we
have
possibility
that
applications
can
be
really
connected
to
some
namespaces,
so
we
can
have
some
isolation.
You
can
imagine
that
you
have
some,
maybe
development
environment
in
one
name,
space
and
stage
environment
in
another
name
space,
and
you
want
to
have
different
applications.
Different
environment,
for
example,
bounded
to
different
namespaces,
how
you
how
you
can
create
new
applications.
This
is
really
simple.
B
You
just
create
new
one
and
provide
the
name
and
description
and
later
on
when
you,
when
you
created
it,
to
connect
it
into
with
our
application
connector,
you
need
just
click
on
the
connect
and
you
copy
to
the
clipboard
one-time
token.
This
token
is
expiring
quickly
and
can
be
used
once
used
once,
and
this
is
the
way
how
we
establish
trust
with
the
application
on
the
on
the
WordPress
site.
We
have
also
a
connector
that
is
provided
that
is
exporting
all
the
events
and
enabling
API
you
can
install
such
connector
to
your
WordPress.
B
From
from
github
repository,
we
have
hosted
this
tema
connector
on
human,
quieter
side.
I
will
point
it
later
how
it
looks
in
the
in
the
in
the
WordPress
settings
its
kheema
connector
settings
here,
and
you
have
just
place
to
play
to
past
the
token
and
press
connect
I'm
already
connected,
so
I
will
not
do
that.
So
this
is
just
one
quick
operation
to
pair
that
when
you
have
in
the
keema.
Actually
you
can
already
write
the
code
and
I
will
show
you
how
this
code
looks
like.
B
So,
as
I
told
you
that
we
have
serverless
engine
inside
keema
and
there
is
a
section
lambdas
when
you
can
list
the
functions,
I
wrote-
and
here
is
the
review
function,
so
so
actually
the
function
that
does
all
this
magic
I
shown
a
minute
ago
and
now
I
will
try
to
maybe
make
it
a
little
bit
bigger.
So
you
can
see
the
entire
code
in
the
in
the
YouTube
video,
so
the
the
function
is
really
a
simple.
So
we
have
a
couple
of
imports.
B
Of
course,
I
use
sentiment,
NPM
package
so
and
this
lambda
is
written
in
no
js',
because
I
do
not
know
PHP
I
mentioned
and
for
no
dress.
You
have
package
for
everything
so
in
case
of
sentiment
so
checking
what
is
the
attitude
of
the
of
the
message?
There
is
also
the
package
with
this.
This
is
a
simple
library
that
just
checks
in
the
dictionary,
positive
words
and
negative
words
and
hate
is
negative.
Love
is
positive
and
then
calculates
the
score.
What
is
the
balance
of
this
positive
and
negative
words?
B
And
that's
that's
what
I
used
and
then
I
have
just
a
couple
of
calls
to
which
are
done
during
the
event
processing,
so
first
I,
I,
lock
and
the
event
data.
So
what
I'm
getting
from
the
WordPress
then
cf
second
line
is
just
getting
the
comment
content
by
from
by
the
ID
of
the
comment,
because
in
the
event
from
WordPress,
you
have
only
idea
of
the
comments
we
need
to
retrieve
that
comments
using
WordPress
API,
then
I
displayed
a
comment.
Then
I
check.
B
What
is
the
the
sentiment
of
these
comments
or
the
positive
or
negative
I
write
it?
This
sentiment
in
the
log
and
if
the
score
is
greater
than
0.2
I
check
to
change
the
status
to
approved
and
I
update
the
comments.
I
have
two
helper
functions,
so
get
comment
which
is
retrieving
the
comment
from
WordPress
and
another
update
comments,
which
is
changing
the
status
and
adding
this
score
to
the
to
the
comments
text,
and
you
can
see
here
and
there
are
no
credentials
I'm
constructing
comment.
B
B
From
the
event,
and
then
I
just
returned
the
response
of
WordPress,
my
wordpress
is
protected,
so
there
is,
there
are
credentials
required
token
to
to
access
this,
this
wordpress,
but
the
developer
doesn't
have
to
take
care
of
that
and
he
just
hits
the
wordpress
key
to
a
URL
and
there
is
a
proxy
deployed
in
the
application
connector
that
is
actually
making
sure
that
this
is
using
right
credentials.
How
does
it
work?
B
This
environment
variable
is
injected
to
my
code
through
the
service
bindings.
What
is
the
service
binding?
It's
actually
what
I
mentioned
before
as
a
Service
Catalog
functionality
in
the
catalog
I
showed
you
I
showed
you
first,
the
application
that
that
is
created,
but
this
application,
when
is
registered
in
the
keema,
appears
also
in
the
service
catalog
and
Service.
Catalog
is
the
list
of
services
that
are
available
in
my
keema
cluster
I
connected
to
the
services,
all
the
services
from
our
broker.
So
you
see
a
lot
of
other
services,
databases
other.
B
Oh
so,
through
the
application
connector,
we
can
register
and
this
WordPress
application
in
in
keema,
and
we
can
see
the
API
so
you've
seen
that
I
used
the
API,
but
actually
I
used.
This
endpoint
here
that
is
documented
here.
So
developer
is
not
left
alone
that
he
has
to
figure
out
how
to
call
the
service.
So
he
has
this
application
and
this
WordPress
service
with
all
the
IDS,
and
he
can
see
also
what
is
in
the
in
the
events.
I
used
the
event
comment
post,
which
contains
comment,
ID
and
comment
status.
B
So
this
is
how
I
know
how
to
write
this
code
going
back
to
the
okay,
maybe
not
going
back
yet
so
I
added
this
instance.
So
this
instance
is
visible
in
the
service
instances,
and
this
is
this
WordPress
instance
and
like
when
I
click
that
when
I
added
it
to
my
namespace
I,
also
bound
it
to
to
the
application
to
to
this
binding
causes
that
the
application
really
is
enabled
to
call
the
API,
and
this
receiving
events
bind
application.
B
You
can
get
any
deployment
or
service
that
is,
that
is
available
in
your
cluster
kubernetes
cluster
and
you
can
select
it.
So
you
see
my
functions
but
also
deployments
other
things,
and
you
can
bind
this
this
application
to
this
instance
of
of
o2
to
to
your
function
that
so
this
is
the
magic
that
is
happening
behind
all
these
environment
variables
that
are
here,
and
here
you
have
also
the
trigger
for
the
function.
B
So
so
short
summary,
you
write
the
code,
which
is
mainly
so
in
my
case,
is
about
20
lines
of
codes.
If
I
remove,
lock
and
imports,
it
may
be
even
less
that
is
doing
the
stuff
and
I
just
trigger
it.
With
with
the
event
that
is
coming
from
the
application,
connector
and
I
am
able
to
call
the
API
fro,
secure
gateway
without
taking
care
of
any
credentials
yet
so
that
was
mainly
in
the
code.
I
will
use
may
be
some
time
also
to
show
you
a
different
version,
more
complex
version
of
that
extensibility
scenario.
B
So
here
you
have
just
static
code
for
checking
sentiment.
Probably
you
could
use
that
directing
the
PHP
know
needs
maybe
to
have
kubernetes
and
all
this
stuff
called
native
for
such
simple
scenario,
but
you
can
imagine
that
you
have
more
and
more
cases,
so
there
are
other
things
you
want
to
do
so,
for
example,
you
want
to
some
messages
in
external
systems.
You
want
to
use
more
sophisticated
analyst
analytics,
not
this
built
this
NPM
package
for
for
checking
sentiment
in
English.
So,
for
example,
a
sure
provides
the
service
for
text
analytics.
B
That
is
able
to
recognize
the
language
and
then
do
the
sentiment
analysis
in
given
language
in
multiple
languages,
and
maybe
you
want
to
and
use
that
functionality
and
instead
of
this,
how
you
would
work
with
that
I.
Could
you
can
start
with
new
lambda
a
new
function
or
new
service,
because
kima
is
also
not
limited.
Only
to
serverless,
you
can
deploy
a
regular
service
micro
service
and
anna
docker
container
that
is
able
to
run
in
the
kubernetes,
can
be
deployed
here
and
can
have
also
all
these
things
injected.
B
So
so
you
can
inject
also
services
and
call
them
from
your
own
micro
services
not
only
from
functions,
but
imagine
that
you
have
also
possibility
to
extend
it
a
little
bit
in
this
scenario.
So
we
want
to
publish
the
messages
on
the
slack
channel
and
you
want
to
use
Azure
as
a
analytics
engine
to
check
if
the.
B
B
So
maybe
I
will
start
from
from
the
short
demo,
so
here
I
have
a
slack
open
in
a
new
window.
One
second
I
will
just
bring
that
window
to
to
the
screen.
You
see
this.
These
are
life.
This
is
live
stream
of
of
these
comments
you
push
to
to
them
to
my
article,
to
numb
to
my
blog
posts
on
on
WordPress,
and
you
see
that
I
am
able
with
the
other
services
analyzed
if
this
is
English.
B
B
This
is
nice
polish
example
of
text
of
the
comment,
so
it's
not
identified
as
English
and
the
meaning
is
negative
in
that
case,
and
a
couple
of
others
are
Mia
recognized
as
positive.
So
this
is
maybe
not
so
positive
but
is
identify
as
positive
and
yeah
a
couple
of
others.
Also.
Thank
you
guys.
You
are
ready
positive
in
in
the
feedback.
So
not
so
many
haters
there
that's
good
and
just
wanted
to
show
you
how
this
is
different
from
from
the
previous
example.
B
So
I
have
some
help
or
functions
to
check
if
it
is
English
comment-
or
it
is
positive
comment
and
in
that
case
I
use
text
analytics
from
from
agile
and
again
it
is
just
injected
in
my
code
as
an
environment
variable,
so
I
hit
text
analytics
and
point
with
languages
or
with
sentiment.
I
pass.
The
text
from
the
comment.
B
I
will
not
go
into
the
details,
because
this
is
yeah
irrelevant
for
the
for
the
presentation
purpose,
but
it
is
not
so
complex
to
use
that
services
and
and
then
in
the
response,
I
get
the
if
it
is
English
or
not
or
it
is
positive
or
not,
and
then
I
built
in
the
in
the
main
function.
I
did
I
built
slack
message,
you've
seen
in
in
the
slack,
so
this
emoji
is
added
and
I
put
that
in
the
slack
message
and
slack
message
to
send
message
to
the
slack.
B
B
One
instance
is
added
here
and
you
see
how
you
yeah.
You
have
also
a
description
of
this
services:
how
to
provision
how
to
how
to
use
that
and
I
yeah.
It's
nice
nice
service.
There
is
a
free
tier,
so
we
can
have
5000
monthly
transaction
with
no
charging
so
yeah
for
this
purpose.
I
used
this
plan
when
I
provisioned
these
utter
text
analytics
in
my
kima
cluster.
B
That's
mainly
end
of
the
life
demo.
I
have
a
couple
of
things:
I
wanted
to
mention
about
kima
itself,
and
then
we
will
conclude
to
the
Q&A
session
if
we
have
any.
But
yes,
so
please
prepare,
maybe
some
questions.
So
a
part
of
that
there
is.
There
is
more
functionality
that
is
behind.
So
this
there
is
no
only
UI
for
kima
everything
that
I
did
here
so
binding
applications
or
writing
lambdas
or
anything
else,
is
available
from
CLI.
B
B
You
have
great
documentation,
it's
hosted
on
the
kheema
project
io
also,
but
you
can
have
it
also
in
the
cluster,
because
we
believe
that
documentation
is
essential
parts
of
the
of
the
code
and
all
the
art
things
that
developers
produce
even
the
greatest
developers
framework
without
the
commendation
is
not
usable
and
we
have
context
wall
dogs,
so
we
can
have
helpers
also
in
given
in
given
windows
in
given
places
in
in
the
in
the
application.
So
I've
shown
you
a
example
for
other
text
analytics
here's
example
for
Google
broker.
B
We
have
monitoring
built
in
air,
so
maybe
this
is
something
I
want
to
also
show
you.
So
whatever
you
write,
you
have
also
the
dashboards.
There
is
a
dashboard
that
is
automatically
populated
for
for
your
lambda,
because
we
use
easier.
So
we
have
all
these
traffic
information.
There
are
points
where
the
other
that
was
invoked
and
there
is
another
in
the
same,
the
in
the
same
pile
at
time.
Both
lambdas
were
invoked.
You
can
see
you
can
see
the
memory
usage,
the
response
times
etc
and
a
couple
of
others.
B
That
is
think,
and
we
have
a
lot
of
other
dashboards
that
are
really
showing
the
health
of
the
cluster
itself.
You
have
ports,
you
have
entire
service
master
dashboard.
A
lot
of
things
are
available
here,
okay,
so
that
was
the
monitoring
integration.
We
have
also
tracing,
so
you
can.
We
have
Yerger
integrated,
so
we
can
track
how
the
messages
the
events
that
are
coming
to
Kemah
are
visible.
It
is
also
integrated,
so
you
can
see
that
in
the
UI
and
yeah
we
have
other
benefits.
B
So,
for
example,
you
can
you
can
have
kima
a
light
on
me,
cue,
so
we've
we
have
also
version.
That
is
not
installing
all
the
components,
because
we
have
a
lot
of
components
in
kima
to
bring
all
this
fancy
stuff
to
you.
But
kima
light
is,
for
example.
Without
is
this
monitoring
I
shown
before
because
in
the
local
development?
Probably
you
don't
need
that
use.
You
know
what
you,
what
were
your
calls
and
you
can
install
in
the
it
on
the
mini
cube.
B
We
have
all
these
a
synchronous
event
inc
with
cognitive,
which
is
abstraction,
so
you
can
plug
in.
So
we
have
already
nuts
shipped
with
the
kima,
but
you
can
have
something
else
that
is
supported
by
a
native,
for
example,
good
pops
up.
Instead,
we
have
micro,
ati
gateway,
so
you
are
able
to
expose
your
services
your
lambdas
easily,
so
the
WordPress,
for
example,
I
deployed
on
kima
cluster,
is
automatically
exposed
with
the
TLS
certificate,
so
you
and
it
is
done
by
API
gateway
we
provide.
B
We
have
also
a
possibility
to
add
items
to
the
to
the
UI
I
presented
to
this
console
with
the
microphones
and
approach
we
use
Luigi
framework,
which
is
also
open
source
framework
to
intend
to
compose
your
applications
from
many
microphones,
and
so
we
have
can
have
independent
development
of
them
and
yeah
I
already
mentioned
this.
This
documentation,
this
API
specs.
We
store
them
in
in
asset
store
with
respect
by
Amenia,
but
can
be
also
backed
by
cloud
service
instead
and
we
have
also
hand
broker.
B
So
this
is
a
part
of
our
Service
Catalog
offering
so
in
the
industries
catalog.
We
have
also
possibility
to
use,
can
broker
to
instantiate
services
that
are
not
have
hand
charts,
and
we
have
built
in
Redis
deployment
that
can
be
instantiated
from
the
Service
Catalog
easily,
with
the
hand
broker
Helen
brokering
service.
The
topic
for
a
separate
talk,
I,
think
and
I
will
not
go
too
much
into
the
details
and
yeah.
If
we
with
kima,
we
do
the
real
open
source
development.
B
So
it's
not
that
we
just
host
the
code
on
the
github
and
it's
available.
We
really
have
cooperation
with
the
community.
We
kima
project
was
born
year
ago.
Actually,
yesterday
we
had
one
of
our
first
birthday
in
the
open
source
as
the
key
native
project
and
we
developed
it
together
with
and
with
Google.
So
we
have
also
our
teams
and
our
contributions
there.
We
also
contribute
to
a
sync
API
specification.
B
Our
and
people
are
essential
contributors
there
and
in
the
Service
Catalog
sick
from
kubernetes.
We
have
our
own
members
and
our
colleagues
are
one
of
our
colleagues
even
nature.
In
this
special
interest
group
of
kubernetes
and
this
member
of
the
kubernetes
organization
and
yeah,
we
encourage
you
to
to
become
a
contributor
and
everything
is
on
this
on
the
other
github.
So
in
the
github
my
project,
slash
kima,
you
can
fill
the
feature,
request,
bug
reports
or
yeah
just
pull
requests
and
we
are
available
on
slack
so
there
is.
B
There
is
course
seek
that
you
can
join
on
the
slack
and
there
is
a
link
to
that
and
you
can
ask
any
questions
on
the
kima
slack.
I
can
even
show
you
that
this
is
really
active,
active
Fink.
Where
is
my
yes
like
channel?
So
we
may
be
so
you
see
that
there
is
a
couple
of
channels
in
the
slack
installation.
I
think
is
the
one
you
will
hit
first,
because
this
is
something
that
people
try.
B
First
then,
there
is
general
channel
and
seek
core
16
core
channel
that
that
we
have
regular
meetings
and-
and
you
can
talk
with
us
really
in
person,
so
it's
it's
online
meeting
and
you
can
join,
and
here
you
can.
You
have
several
announcement
at
cetera,
you
can
read
and
you
can
join
our
community.
So
you
see
that
there
is
about
700
people
already
in
this
black
channel
and
I
wanted
to
show
you
also
and
the
github
page
so
project
keema
is
there.
We
have
already
700
stars
and
we
ask
for
more.
B
Okay,
if
you
like
it,
please
please
go
there
and
installation
guide
is
really
easy
and
I
mentioned
you,
this
Kim
and
Kim
alight,
and
if
you
want
to
install
it
locally
with
mini
cube.
There
are
really
literally
two
comments
to
do
and
you
will
have
your
own
cluster
on
your
local
machine
and
of
course
you
have
installation
steps
on
cluster,
so
I
recommend
you
going
with
GK
or
GCP
marketplace
you
can.
We
are.
We
are
there
so
in
the
market
place.
So
this
is
Google
cloud
platform
marketplace.
A
B
Yes
and
I
have
answer
for
that.
So
I
mentioned
this
came
a
project
IO
with
with
documentation
a
lot
of
documentation,
but
if
you
go
to
the
main
site
and
you
scroll
down,
you
see
early
adopters.
So
there
are
a
couple
of
companies
that
already
use
that
that's
solution
and
one
of
them
net
economy
is
when
production
in
May.
So
it
was
during
the
cube
con
I
think
when
we've
been
there,
so
they
went
live
with
kima.
A
couple
of
other
are
close
to
that
and
yeah.
B
We
are
getting
more
and
more
customers
right
now
in
the
in
our
commercial
offering.
So
if
maybe
one
on
vert
Iseman
so
kima
is
an
open
source
project,
100%
open
source,
all
you
can
contribute.
You
can
become
even
the
code
owner
here,
but
we
have
also
commercial
offering
in
a
city.
So
we
have
already
several
customers
that
are
on
boarded
to
the
commercial
offering
which
is
called
city
extension
factory
and
the
name
is
and
but
under
the
hood
there,
this
product
is
powered
by
team
out
source
project.
So
we
have
also
commercial
use
cases.
B
A
C
A
B
So
yeah
so
the
migration
from
Manali
to
micro
services,
as
we
imagine,
is
more
that
you
don't
necessarily
rewrite
your
application
to
the
micro
services.
So
there
is
some
other
way,
so
you
can
build
new
features,
a
side
of
them,
and
this
is
something
we
do
also
in
SAT,
so
you
you
can
believe
or
not,
but
in
SA
P
we
have
also
some
legacy
applications
that
are
not
born
last
year
and
we
have
a
lot
of
them.
B
That's
where
you
have
that
have
rich
history
and
we
enabled
them
for
for
clouds
and
micro-services
in
the
way.
I
present
it.
So
we
build
the
connectors
for
them
because
it's
easier
yeah.
So
we
can
build
the
connector
once
for
this
application
and
then
all
our
customers
can
benefit
and
do
not
have
to
struggle
with
all
these
problems
with
Manolis
with
risky
deployments
over
and
over
again.
So
they
can
use
that
that
thing,
if
you
can
lift
EEMA
at
the
end
of
that
process.
B
Yes,
you
can
so
actually
kima
is
the
bunch
of
open
source
components.
All
of
them
are
open
source,
so
we
utilize
existing
components
and
we
have
our
own
components
but
also
open
source.
So
you
can
fork.
If
you
don't
trust
us,
you
can.
You
can
build
your
own
version
and
you
can
run
it
or
you
can
just
also
modify
the
the
way
kimye's
install
so
kima
is
also
modular.
We
have
possibility
to
exchange
some
components,
remove
some
components.
So
the
example
with
kima
light
is,
is
the
best
example.
B
Right
now,
I'm
working
in
the
C
for
custom
for
for
the
line
of
business,
which
is
customer
experience,
and
so
we
have
integrated
SCP
commerce
as
the
first
one,
because
this
is
the
city
Commerce
is
developed
here
in
Poland
in
the
city
office,
Inc
leave
it
sir.
So
we
have
good
connection
to
these
two.
Those
guys-
and
this
is
the
first
application-
others
are
SAT
marketing,
and
now
we
are
integrating
all
the
safety
service
cloud
and
s4
stack.
B
A
B
So
the
scalability
is
more
about.
If
you,
if
you
may
imagine
right
now,
I
write,
maybe
something
more
complex,
more
sophisticated
than
text
analytics,
which
is
a
relatively
quick,
quick
and
is
using
external
services.
But
you
can
imagine
that
you
for,
for
example,
there
is
another
story
that
we
are
working
right
now,
which
is
related
to
another.
Our
ICT
product
product
contact
content
hub,
which
is
which
is
managing
products
for
for
commerce
sites,
and
their
case
can
be
just.
For
example,
you
do
resizing
of
the
images
in
a
cloud
native
way.
B
So
imagine
that
you
have
maybe
some
some
product
catalog
and
you
have
I,
don't
know
hundreds
thousands
of
images
and
you
need
to
prepare
thumbnails
images
for
for
a
big
view
for
mobile
view,
whatever
view
and-
and
you
want
to
do
that-
that
feature
you
want
to
add
to
your
product
content,
you
can
imagine
that
if
you
want
to
do
that
inside
the
application,
you
need
to
scale
that
application.
This
mono
lead
application,
even
though
that
other
features
are
not
heavily
used.
B
B
If
you
have
just
adding,
if
you
adding
seeing
a
single
image
at
the
time,
you
can
keep
just
a
one
two
nodes
of
the
faster,
and
if
the
traffic
comes
up,
you
can
instantiate
up
to
infinite
number
of
of
nodes,
and
then
you
have.
You
can
do
that
outside
of
them
of
the
application.
Of
course,
you
need
to
be
able
to
send
this
amount
of
events
and
and
have
a
proper
scaling
on
to
get
these
events
and
get
these
images,
probably
from
from
the
source
system.
B
A
B
A
B
This
roadmap,
which
applications
are
part
I,
can
provide
you
a
link
later
because
I
have
note
this.
This
is
linked
in
the
CP
site,
so
it
is
nothing
in
the
kheema
I'm
not
prepared
for
that
right
now,
I
can
send
it
later
and
as
an
update.
Maybe
in
the
comment
for
for
for
this
video
and
for
sure
you
have
so
one
thing
you
can
see
it's
a
road
map
of
key
might
salvia.
B
So
so
this
is
here
in
the
in
the
site
and
you
can
see
what
is
possible
in
different
areas,
so
they
I
will
select
one
and
use,
and
you
and
you
see,
have
even
some
nice
view
in
which
release
what
is
planned
and
what
is
planned
in
the
future,
and
this
is
the
live
road
map
because
it
is
rendered
from
epics
from
github.
So
you
can
see
what
features
you
can
expect
soon.
B
B
Already
in
the
github,
so
not
everything
is,
is
there
more
things
will
come
soon
so,
but
your
feedback
is
also
welcome
here.
So
if
you
see
some
features
that
are
missing,
you
want
to
have
them.
Please
contact
us
on
slack
on
github
the
feature
request.
We
are
really
open
and
we
react
on
the
on
the
people's
demands.
Yeah.
A
And
for
the
information
we
will
post
all
necessary
links
that
were
mentioned
in
this
presentation
or
in
the
Q&A
session
tomorrow
in
posts
and
below
the
video
when
it
uploads
as
video
to
watch
in
YouTube
is
now
we
have
live
broadcasts
and
then
we
will
have
in
the
form
of
video
on
the
YouTube
channel.
I,
don't
see
more
questions.