►
From YouTube: Lightning Talk: Build a Twitter Translation Bot In 5 Minutes With Knative Functions - Lance Ball
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from April 17-21, 2023. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Lightning Talk: Build a Twitter Translation Bot In 5 Minutes With Knative Functions - Lance Ball, Red Hat
Come see how quickly and easily you can get started developing reactive Kubernetes apps with Knative Functions. In this quick 5 minute demonstration, you will see me develop a Twitter bot that translates Tweets into multiple languages using Google’s Translate API. With only a handful of commands to run and a simple API to learn, getting from zero to powerfully productive takes only minutes. Let me show you how - in only 5 minutes!
A
Hey
everybody:
my
name
is
Lance
ball
I'm,
a
software
engineer
at
red
hat
for
the
last
couple
of
years,
I've
been
working
on
this
project
that
is
now
known
as
k-native
functions.
I
want
to
show
you
today
how
quickly
and
easily
you
can
get
up
and
running
with
your
first
k-native
applications
using
the
power
of
functions
as
well
as
camel
k
for
an
event
source.
A
First
of
all,
I
want
to
talk
a
little
bit
about
what
k-native
brings
to
the
table.
Besides
what
everyone
already
knows
about-
and
that
is
you
know,
scale
to
zero.
It's
also
very
much
about
developer
happiness
through
the
k-native
functions,
programming
model
and
client
tools,
it's
about
ease
of
deployment
using
that
same
CLI,
as
well
as
the
k-native,
client,
CLI
and
then.
Finally,
we've
got
this
common
event.
Format
called
Cloud
events
that
ties
everything
together.
It's
that
Common
Thread
that
goes
through
the
k-native
serving
Eventing
and
functions
modules.
A
The
building
blocks
I
think
that
these
three
things
all
come
together
to
make
k-native
something
sort
of
greater
than
the
sum
of
all
these
individual
parts,
so
functions
for
a
lot
of
developers
just
coming
to
kubernetes.
It's
a
lot
right,
there's
a
lot
of
mental
overhead
there's
a
lot
of
things
you
have
to
learn.
K-Native
functions
is
a
programming
model
and
a
set
of
tooling
that
works
to
kind
of
reduce
the
friction
when
you're
first
coming
to
kubernetes,
it
significantly
reduces
the
time
to
productivity,
I
think
all
right.
A
So
how
are
we
going
to
do
this?
I?
Have
this
demo
that
I
wanted
to
do
today,
but
for
obvious
reasons,
I'm
not
actually
going
to
do
the
demo,
but
for
the
record
I
do
have
it
down
to
under
five
minutes.
This
is
a
kind
of
bad
diagram
that
shows
what
we're
going
to
try
and
build.
First
of
all,
there's
a
camel
kamlet
that's
going
to
serve
as
our
Event
Source.
It
makes
polling
requests
to
the
Twitter
API
the
search
API
converts.
A
Those
results
into
Cloud
events
sends
those
Cloud
events
deck
directly
to
the
k-native
event
broker.
That's
the
little
Hollow
Diamond
that
you
see
there
in
the
middle
that
event
broker
has
a
couple
of
triggers
associated
with
it.
One
of
them
sends
Cloud
events
to
a
translate
function
which
uses
the
Google
translate
API
to
translate
the
Tweet.
If
it's
not
in
English,
it
returns
a
new
Cloud
event
to
the
event
broker,
with
a
new
type
that
new
type
triggers.
A
Another
function
called
a
viewer
function
which
does
nothing,
but
you
know
print
that
tweet
or
the
cloud
event
of
the
Tweet
to
the
screen
so
that
we
can
see
everything
working
okay.
So
let's
take
a
look
at
the
code,
then
here's
our
translate
function.
It's
pretty
simple!
You
can
see
it's
just
a
little
bit
of
JavaScript.
It
receives
a
cloud
event
as
the
data.
For
that
event,
we
have
the
tweet.
A
The
next
function
that
we
have
in
this
little
application
is
a
viewer
function.
It's
even
simpler
than
the
translate
function.
It's
written
in
go
and
all
it
does
is
receive
a
cloud
event
and
print
it
to
the
screen
because,
like
I
said,
we
just
want
to
make
sure
that
everything
works
in
a
real
application.
You're
going
to
do
something
a
little
bit
more
interesting,
I,
hope.
A
Okay,
and
this
is
the
Twitter
search
camlet.
It's
really
just
a
bunch
of
yaml.
As
long
as
you
have
your
access
token,
your
API
keys
and
your
secrets
and
some
sort
of
search
term
that
you
want
to
search
for
you're
set
you
deploy
this
thing.
It
starts
polling
the
Twitter
search,
API,
converting
those
results
into
Cloud
events
and
sending
them
directly
to
the
default
k-native
event
broker.
A
So
how
do
we
put
all
these
things
together?
It's
just
a
handful
of
command
line
calls,
first
of
all
to
deploy
the
two
functions
we
used
to
use
the
func
deploy
command,
so
we
deploy
the
viewer
function
in
the
translate
function,
then,
to
create
an
event
broker.
We
can
just
use
KN
broker,
create
default
to
create
a
default
and
memory
event
broker.
Then
we
use
KN
trigger
create
to
create
the
two
triggers.
We
give
them
names.
A
The
dash
s
flag
tells
us
where
the
true
where
the
events
are
going
to
go
so
the
first
one
is
sending
events
to
the
translate
function
and
filtering
on
type
Twitter
search
Source.
The
second
one
is
sending
events
to
the
viewer
function.
That's
the
result.
That's
coming
back
from
the
translate
goes
to
the
viewer
function,
filtering
on
type,
K
native
function,
translation
and
then
finally,
we
use
the
common
Cube
cuddle
apply
to
apply
that
yaml.
A
That
is
our
Twitter
search,
cam
link
and
if
everything
works,
as
expected,
we
get
a
scrolling
tweets
on
our
screen
with
the
viewer
function
as
we
tail
the
logs.
In
this
case,
it's
not
actually
happening
in
real
life,
because
this
isn't
a
demo.
This
is
a
screen
capture
of
the
last
time.
I
did
this
before
you
know
before
coming
up
here.
That's
it!
Thank
you
very
much.
There's
a
QR
code.
If
you're
interested
in
checking
out
this
demo
yourself
a
couple
of
links,
there
hope
you
have
a
fantastic
kubecon.