►
From YouTube: OpenJS In Action w/ Fusebit: Betting Your Product’s Developer Experience on Node.js and Open Source
Description
OpenJS recently spoke with Yavor Georgiev, Co-Founder, and Head of Product at Fusebit, to learn more about how his product leverages Node.js and other benefits of the open source ecosystem.
0:00 Introduction
1:25 Fusebit and Node.js
3:15 Security
5:30 Node.js next-10
7:00 Fusebit SaaS integrations for developers
9:15 Contributing to open source: everynode
12:15 JavaScript is ubiquitous
14:00 Supporting the open source community
15:10 End
A
Hi,
I'm
alex
robinson
marketing
lead
at
the
openjs
foundation,
we're
continuing
our
openjs
in
action
series
today
with
a
conversation
with
javor
georgiev.
Who
is
the
co-founder
one
of
the
co-founders
of
fuse
bit
yabor
you're
here
to
talk
to
us
today
about
fuse
bit
and
how
you're,
using
node.js
and
kind
of
generally
speaking
about
how
the
node.js,
open
community
and
ecosystem
is
helping
fusebit
to
make
mass
integrations
that
are
easy
and
accessible
to
developers
all
over
the
place.
B
That's
right,
yeah,
we're
big
believers
in
in
node
in
the
node
ecosystem
and
our
entire
product
is
actually
based
on
a
javascript
developer
experience
based
on
node,
so
so
yeah
we've
been
there
since
the
the
early
days
and
continue
to
stay
on
top
of
everything.
That's
going
on.
A
Is
it?
Is
there
something
unique
about
how
fusebit
is
using
node.js,
or
is
it
just
that
it's
a
best
in
class
tool
for
you,
yeah.
B
Absolutely
so
yeah,
so
a
couple
of
things
so,
first
and
foremost
we're
developer
products,
so
our
customers
themselves
are
our
developers
and
so,
as
a
developer
product,
we
expose
a
programming
model
based
on
node.js.
So
not
only
do
we
use
it
to
build
our
service,
but
it's
the
way.
Customers
use
our
service
right,
so
we
expose
node
as
the
programming
model
for
anybody
creating
integrations
and
that's
great
for
a
couple
of
reasons.
B
A
you
know,
there's
already
a
massive
community
out
there
of
developers
that
are
familiar
with
node
and
javascript,
and
so
for
them
they
don't
have
to
relearn.
You
know
anything
new.
They
just
bring
their
existing
skills,
they
bring
their
existing
processes
around
devops
and
such
they.
Basically,
you
know
already
know
how
to
use
our
product
just
because
we
leverage
node
as
our
developer
experience.
B
Another
thing
is
that
you
know,
obviously
the
npm
ecosystem
is
so
rich,
so
there's
a
module
for
everything
these
days.
So
if
a
customer
needs
to
do
something,
they
don't
have
to
implement
it
from
scratch.
They
can
just
grab,
grab
a
module
off
of
npm,
and
so
that's
a
real
productive
experience
for
them
and
great
for
us,
because
they
can.
They
can
get
more
done
with
our
product
faster
right.
B
Absolutely
and
that's
another,
that's
that's
a
great
point.
We're
we
ourselves
big
parts
of
the
product.
The
source
code
is
available
on
github,
and
so
customers
can
come
in
and
basically
fork
features
or
fork.
Some
of
our
sas
connectors
and
change
them
make
them
their
own.
So
we
ourselves
are
leaning
into
that
angle
as
well.
A
Cool
on,
like
just
kind
of
piggybacking,
on
that
a
little
bit
how
how
is
node.js
helping
you
to
offer
something
secure
like
a
secure
platform.
B
Yeah,
that's
a
good
question,
so
it's
a
long
answer.
We,
the
founding
team,
so
me
and
one
of
the
other
co-founders,
were
both
former
microsoft
employees
and
then
former
author
zero
employees
and
author
zero
is,
you
know,
I'm
sure
folks
are
familiar,
but
it's
you
know
a
identity
and
access
management
platform,
and
so
a
lot
of
our
own
security
is
based
on
off
zero
and
off
zero
itself.
They're
a
big
node.js
shop.
B
So
our
our
auth
story
for
the
product
itself
wouldn't
be
there
if
we
didn't
have
node
and
if
we
didn't
have
companies
like
auth0
that
have
also
invested.
B
You
know
in
the
ecosystem,
but
obviously
another
big
piece
is,
as
we
were
talking
about
earlier.
We
we
ourselves
leverage
a
lot
of
modules
off
of
npm
and
having
a
lively
community
with
with
modules
where
the
developers
are
constantly.
You
know,
updating
their
code
and
patching
vulnerabilities
and
staying
on
top
of
things
and
that
that's
critical
right,
because
if,
if
there's
a
vulnerability
in
something
we
use
and
it
stays
unpatched,
you
know
that
that's
a
big
problem
for
us.
So.
B
Luckily,
we
haven't
had
issues
like
that
with
npm.
A
Yeah,
that's
good
to
hear
and
sort
of
just
curious.
Have
you
been
working
with
node.js
since
before
it
was
part
of
the
openjs
foundation.
B
Yeah,
I
think
we
were-
I
mean
we
going
back
to
history.
We
were
at
microsoft
me
and
my
other
co,
one
of
my
other
co-founders.
We
actually
worked
to
bring
support
for
node
to
azure
to
the
azure
cloud
and
so
back.
Then
it
was
in
the
zero
point.
Something
version
range,
so
yeah
we've
been
we've
been
engaging
with
nodes
from
the
very
early
days.
A
Okay,
and
is
there
any
sort
of
like
improvement
or
like
march
difference
that
you've
seen
or
I
mean
there,
has
to
be
something
because
you've
been
with
it
since
the
beginning,
but
I
would
say
in
like
the
last
couple
of
years:
is
there
anything
you
you've
noticed
is
different.
B
Yeah,
absolutely,
I
think,
what's
what's
really
happening
now
in
the
node
community
and
is
very
healthy,
as
is
kind
of
a
the
ongoing
and
open
conversation
around
the
future
of
the
platform
and
where
things
are
going,
you
know
before
you
know
it
was.
It
was
somewhat
of
a
of
a
close
process.
The
way
the
way
decisions
were
made,
and
now
you
know,
there's
there's
working
groups
for
almost
everything
the
minutes
are
being
made
public.
The
you
know
the
there's
recordings
of
all
the
calls
we
ourselves.
B
I
just
I
was
just
trying
out
one
of
the
one
of
the
new
experimental
features
and
I
had
feedback,
and
you
know
I'm
about
to
file
a
bug
and
kind
of
join
that
conversation
and
we
really
enjoy
sort
of
the
the
open
process
and
the
open
conversation
around.
You
know
what's
next
and
we
feel
like
we
can
participate
in
that
which
is
which
is
great.
B
It's
awesome
another.
Another
thing
is,
you
know
we
recently
were
talking
about
undici
and
so
the
bigger
conversation
of
how's
nodes,
http
stack
evolving
and
that's
another
one,
another
another
big
conversation.
It's
been
the
the
existing
http
models.
You
know
pretty
pretty
ancient
in
in
node
and
having
having
the
ability.
Obviously
we
build
a
lot
of
web
services,
so
that's
critical
for
us,
so
being
able
to
be
part
of
that
conversation
as
well
has
been
tremendous.
So
thank
you.
Thank
you
tell.
B
Yeah,
so
fusebit
is
an
integration
platform
for
developers
based
on
node.js,
so
a
simple
way
to
think
about.
It
is,
if
you're,
if
you're
a
builder
out
there,
putting
together
a
sas
application
or
any
application
for
that
matter.
You
know
you
need
integrations
to
to
common
third-party
sas
products.
Right.
B
Nothing
exists
in
a
silo
today,
and
so
you
need
a
slack
bot
or
if
you
you
know,
if
you're
in
a
if
you're
in
the
productivity
space
you
need,
you
know
some
integration
to
jira
or
atlassian,
so
we
provide
those
integrations
in
a
turnkey
way.
That's
you
know,
ten
times
more
productive
for
the
for
the
average
developer.
Instead
of
everybody
building
integrations,
you
know
themselves,
they
could
just
leverage
our
service
offering.
So
we
like
to
think
of
fusebit
as
stripe,
but
for
integrations
basically.
B
B
Yeah,
so
in
in
the
in
the
integration
space
you
know
so
far.
A
lot
of
the
incumbent
players
come
at
it
from
you
know
an
I.t
angle
or
from
you
know,
a
productivity
angle
for
non-technical
users
and
fusebit
is
probably
the
only
one
of
the
very
few
integration
solutions
out
there.
That
is
actually
entirely
designed
for
developers
from
day
one
based
on
node.js
right.
So
that's
what
that's?
What
makes
us
unique
and
you
know,
because
we
are
for
developers,
there's
basically
you
know
infinite
customizability.
B
We
can
achieve
really
great
problem
solution
fit
for
our
customers.
Unlike
you
know,
some
of
the
like
no
code
solutions
out
there,
where
you're
kind
of
at
the
mercy
of
what
it
already
does,
but
because
our
product
is
for
devs
like
it's,
you
know
you
can
you
can
really.
You
can
really
solve
your
problem
to
the
t.
B
So,
since
with
fusebit,
we
focus
on
on
a
on
a
b
to
b
audience
right,
so
our
customers
themselves
their
businesses
and
their
users
or
businesses,
and
so
when
you,
when
you
want
to
connect
business
software
to
something
like
salesforce,
you
know
where
you
know
the
data
matters
and
the
fidelity
matters
you
still
that's
still,
where
developers
sort
of
rain
right
you're.
You
really
need
someone
with
the
right
technical
mindset
to
be
able
to
pull
off
an
integration
like
that
yeah.
A
Makes
sense,
how
does
fuse
bit
engage
with
the
open
source
side
of
things.
B
Yeah,
oh
it's
interesting.
You
should
ask
that
because
we
just
recently,
we
recently
put
out
a
project
out
there.
It's
called
every
node
that
lets
as
developers
run
any
version
of
node,
including
the
most
recent,
builds
on
aws
lambda,
which
sometimes
doesn't
have
the
latest
versions
on
there,
and
so
so
we
we
built
that
internally
for
ourselves,
because
we,
you
know
some
of
some
of
the
integrations
we
want
to
do-
require
a
later
version
of
node.js
right.
B
So
we
built
it
for
our
own
product,
so
we
could
run
it
on
aws,
but
then
we
went
and
put
it
out
there
for
for
the
rest
of
the
node
community
to
to
take
advantage
of,
and
we've
seen
some
some
really
good
uptake
and
a
lot
of
good
conversation
around
it.
B
And
you
know
that's
I
mean
that's
just
one
small
example
like
the
team
routinely
takes
pieces
of
our
product
and
and
puts
it
out
there
for
everybody
else
to
use
whether
it's
npm
packages
or
repositories
out
there
or
even
you
know,
content
so
yeah.
We
we
love,
we
love
engaging
with
the
community
in
that
way,.
A
Yeah,
that's
that's
great,
I
think
that's
a
great
way
to
contribute.
You
know
some
of
the
technology
and
the
talent
that
you
guys
have
in
your
team
and
also
it
speaks
to
a
little
bit
of
something
else
that
I
wanted
to
touch
on,
which
is
like
how
is
the
way
that
you're,
using
either
node.js
or
any
other
open
source
projects
like?
How
is
that,
like
you
know,
helping
to
sustain
the
open
source
ecosystem
and
does?
A
Is
there
any
like
kind
of
vision
for
future
innovations
with
that,
and
that
can
be
with
any
open
source
tools
or
just
how
you
guys
are
working
in
general?
That
you'd
like
to
share
the.
B
The
primary
way
we
try
to
contribute
is
by
by
giving
back
right
so
filing
issues.
When
we
find
something
contributing.
You
know,
fixing
issues
where
it's
blocking
us.
You
know
contributing
code
and.
B
Ways
in
which
we
try
to
we
try
to
bolster
the
the
ecosystem,
and,
obviously
you
know
we're
involved
in
in
conversations
as
as
new
designs
land
for
for
for
new
node
features,
for
example.
But
yeah.
That's
that's
that's
about
it.
You
know,
we've
we've
played
with
you
know
making
you
know.
As
I
mentioned
before
we
you
know
we
release
certain
parts
of
our
product
as
open
source
and
we're
always
talking
about
hey.
Can
we
make
more
and
more
of
it
open
source?
B
Because
I
mean
the
way
we're
thinking
you
know
about
our
product.
You
know
we
have
a
service
offering
that
that
adds
a
ton
of
value,
but
there's
pieces
that
are
just
generally
useful
and
for
us
you
know,
selfishly
it's
actually
better
for
more
developers
to
be
familiar
with
them,
instead
of
keeping
them
secret
right
so
like
so,
the
more
people
are
familiar
with
aspects
of
fusebit
that
we've
made
open,
open
source,
the
better
for
our
our
our
our
product
and
our
service.
So.
B
A
There
are
a
lot
of
other
programming
languages
that
developers
can
use,
is
javascript
still
the
language,
the
programming
language
of
choice
for
developers,
and
why
would
you
say
that
is.
B
Yeah
I
mean
just
looking
at
the
job
market
out
there
today,
it's
like
it's
really
hard
to
find
good
javascript.
That
is
in
particular
folks
that
work
on
the
back
end
as
well
as
the
front
end,
and
so
I
think
that
that's
that
speaks
to
its
kind
of
continued
health
and
ubiquity,
so
so
yeah.
I
think
it's
still
it's
still.
It's
still
great.
B
It's
there's
still
amazing
versatility
being
able
to
build
end-to-end
solutions
with
front-end
and
back-end
it
kind
of
leveraging
some
of
the
same
skill
set
and
now
even
some
of
the
same
actual
modules
that
are
available
on
both
so
yeah.
I
mean
the
language
itself
continues
to
evolve
as
well.
B
So
it's
not
you
know
going
to
fall
behind
the
times
so
yeah.
We
continue
to
be
quite
quite
excited
and
you
know
there's
some.
Some
real
cool
initiatives
happening
that
you
know
like
the
standardizations
of
the
of
the
the
module
spec,
for
example,
is
one
of
those
things
where
you
know
now
you
can
now
you
can
write
a
module
and
use
it
pretty
much
anywhere
where,
where
javascript
runs,
whether
it's
node
or
like
in
a
browser
right-
and
so
this,
this
kind
of
continuing
of
innovation
is,
is,
is
great
and
kind
of
keeps.
B
A
Cool
so
yeah,
it's
been
great
learning
more
about
your
product
and
how
you
work
with
node.js
and
just
engaging
with
the
open
source
ecosystem
in
general.
So
is
there
any
like
closing
thoughts
that
you'd
like
to
share
with
us.
B
Yeah
well,
first,
thanks
alex
for
giving
us
a
chat,
a
chance
to
to
talk
to
you.
My
parting
thoughts
is
mostly
I
just
want
to
thank
the
you
know
the
node.js
community,
everybody
who's
contributing
everybody
who's.
You
know,
you
know
even
unpaid,
putting
hours
into
to
make
note
and
the
the
package
ecosystem
great.
It's
been
tremendous
for
for
companies
such
as
fuse
bit
the
the
ability
to
innovate
and
get
product
to
market
super
fast.
B
So
you
know:
we've
we've
really
appreciated
that
we've
tried
to
give
back
to
the
community
by
obviously
hiring
folks
that
have
the
right
skill
set
out
of
the
community.
A
bunch
of
our
team
is
got
hired
out
of
the
of
the
node.js
community
in
colombia
right
and
so
that's
one
way.
We
try
to
try
to
support
node.js
and
and
the
devs
that
work
in
in
in
the
in
the
ecosystem
and
and
yeah
it's
it's
just
been.
B
It's
just
been
a
real
boon
for
it
for
us
as
a
startup,
so
we
really
appreciate
it
and
thank
you
all.