►
Description
To learn more about critical open source JavaScript projects like Appium, Dojo, jQuery, Node.js, and webpack, and 27 more checkout The OpenJS Foundation: https://openjsf.org/
Creating SQSLite - My Journey into Open Source - Jenny Eckstein, LIfion by ADP
JW Grand Ballroom 1
Speakers: Jenny Eckstein
SQSlite allows us to create a mock of Simple Queue Service (SQS) in order to test interactions with AWS. SQSlite is a lightweight solution that can be installed as a node module, or work as a standalone command line interface (CLI) tool. You do not need to register, provide a credit card or worry about running over the free limit when using AWS for development. Developing software using AWS directly causes costs to soar. There are some solutions such as localstack, and other stand-alone applications that imitate a particular service. However, there was no available solution for SQS service. I will share SQSLite’s journey from research to implementation and final result, as well as my personal story of becoming an open-source contributor.
A
A
A
A
Many
of
us
who
have
started
coding
at
some
point
discovered
coding.
How
does
it
usually
start
for
me?
It
started
on
youtube.
I
saw
how
how
you
can
write
code
and
I
was
very
curious
and
once
I
have
discovered
what
I
can
do
with
code.
I
was
amazed.
It's
like
a
lego.
I
can
build
a
lego
land
out
of
so
most
stories
go
like
this.
Can
everyone
hear
me
well?
Well,
okay,
perfect,
so
how
most
stories
go?
You
discover
programming
and
you
want
to
build
everything
at
once.
A
You
get
so
excited,
you
build
a
front
end,
you
build
a
backhand
and
then
you
discover
cloud
and
you
integrate
cloud
and
let's
say
in
our
case
it's
aws.
You
go
on
aws,
you
sign
up,
you
get
your
account!
You
put
in
your
credit
card
and
you
begin
the
work
and
you
build
your
application.
You
write
some
unit
tests,
everything
works
and
you
feel
so
empowered
with
everything
you
can
build.
A
You
discover
sqs
and
you
build
a
queue
and
you
see
that
you
can
send
messages.
You
can
receive
messages
and
you
decide
to
automate.
You
learn
about
unit
testing
and
you
write
tests
and
you
automate
them
on
every
code.
Change
your
tests
run.
Everything
succeeds,
you
feel
so
proud
of
yourself
of
everything
you
build
and
everything
you
can
build.
You
can
see
that
programming
gig
coming
up
in
your
future
at
the
dream
job
you
wish
you
can,
you
will
have
or
a
freelance.
A
A
A
A
So
local
stack
is
great
and
it's
fantastic
for
large-scale
applications
and
it
saves
a
lot
of
people
a
lot
of
time
and
money,
but
there
are
a
few
challenges
with
local
stack.
It
has
about
three
pages
of
configurations,
a
lot
of
requirements
and
generally
a
challenge
for
to
get
started
with
very
quickly.
A
So
what
what
are
some
other
solutions?
So
I
have
built
a
sql
slide,
which
is
a
mock
server
for
sqs,
aws
sqs
and
why
sql
slide.
Essentially,
there
are
already
three
similar
products
on
the
market
in
open
source,
dynalite,
kinesalite
and
server,
and
now
we
have
sql
slide
and
I'm
so
proud
of
that
animation.
A
So
why
sq
slide
essentially
sql
slide
is
an
ntm
module
that
is
written
in
pure
node.js.
It
is
open
source,
it
saves
you
cost
just
like
local
stack,
it's
very
lightweight.
You
can
use
it
as
a
node
module.
You
can
integrate
it
into
a
unit
test.
You
can
write,
run
it
as
a
cli
tool
and
we
have
replaced
our
standard
mocking
unit
tests
for
sqs
and
have
seen
a
very
like
it's.
It's
proved
very
successful.
It's
it's
definitely
improved
our
unit
testing.
A
How
would
you
actually
develop
in
it
and
I
will
walk
you
through
the
code.
I
put
I
conveniently
put
line
numbers,
so
you
can
follow
along
with
me.
So
if
you
have
ever
built
with
anything
with
aws
sdk,
you
import
aws,
sdk
online.
Two,
you
also
import
sql
slide,
because
because
that's
what
we're
going
to
use
for
our
server
in
this
case
on
line
13,
you
instantiate
sqs,
and
you
pass
that
at
point
that
says
local
stack
and
what
what
that
does
is
it's.
A
Instead,
it's
sends
the
input
to
aws
but
redirects
it
to
your
local
machine.
So
your
inputs
are
the
same
as
you
would
send
to
aws
actually
does
validations,
but
it
doesn't
run
the
processing
time.
Therefore,
it
runs
as
a
mock
server.
It
does.
It
doesn't
charge
you
money
and
it
imitates
the
behavior
as
exactly
as
you
would
expect
in
sql
slide,
and
you
get
the
response
exactly
the
same
as
you
would
get
from
aws
sqs.
A
So
passing
that
remo
local
local
host
passing
that
local
host
gives
us
a
fake
server
and
then
line
17.
We
start
that
server.
So
we
run
that
function
line
4
to
line
11,
which
starts
a
server.
It
passes
some
parameters
like
log
or
false.
It
uses
fastify
under
the
hood.
So
anything
you
would
pass
on
in
into
the
fast
fi
you
can
pass
into
sql
slide.
You
listen
on
port.
Your
server
is
running
and
then
line
19
through
line
32.
Essentially
you
perform
the
same
operations
you
would
for
sqs,
you
create
q.
A
A
A
You
can
also
use
sql
slide
in
your
in
your
unit
test,
and
here
I
have
an
example
with
jest,
where
you
have
also
import
an
aws
sdk
you
import
sql
slide.
You
create
some
local
host
endpoint
and
in
the
before
all
you
instantiate
sql
slide
with
that
endpoint
to
run
on
a
local
host
on
line
17
and
then
line
27
to
line
30.
You
get
you
get
to
write
your
unit
test
and
you
can
assert
for
the
same
output.
A
You
can
also
use
sql
slide
as
the
cli
tool,
and
you
will
write
the
same
way
as
you
would
write
with
aws.
Essentially,
you
also
pass
the
endpoint
parameter,
which
redirects
you
to
your
your
local
server
and
the
input
and
the
output
will
look
exactly
the
same.
So
we
have
three
ways
to
use
it
use
it
as
a
server
use
it
in
unit
test,
uses
a
cli,
and
the
rest
is
up
to
your
imagination.
A
A
A
So
my
suggestion,
when
you
start
an
open
source
project,
is
to
have
someone
else
help.
You
don't
think
you
can
do
everything
by
yourself.
You
can
try,
but
it
is
hard
you,
no
one.
Always
has
the
time-
and
you
always
want
to
have
the
next
of
kin
in
your
open
source
project,
to
help
you
maintain
it
and
maintain
the
standards
that
are
expected
of
your
project.
A
A
Next,
if
you
are
someone
who
uses
a
popular
open
source
library
help
the
contributors
maintain
it
your
help
in
reviewing
the
pull
requests
in
looking
at
the
code,
understanding
the
code
proofreading
documentation,
adding
improvements
is
very
helpful.
If
you
find
the
bug,
it
would
be
very
helpful
for
you
to
fix
it
and
open
source
contributors
really
appreciate.
A
My
favorite
when
I
was
working
on
my
project
was
when
the
bug
report
came.
It
came
with
here's
this
pr,
so
this
you
don't
always
have
to
open
the
pr,
but
at
lea,
be
out
there
to
help
and
to
help
open
source
contributors
help
you
so
lesson
number
two
make
it
easier
for
creators
to
offer
you
their
product.
A
A
Open
source
is
a
lot
about
communications,
and
the
communication
protocols
are
very
important
to
avoid
the
back
and
forth
communication
which
could
be
integrated
into
your
into
your
project.
For
example,
always
bill
always
have
templates
for
bug
reports
and
the
features
have
a
checklist
which
engineers
need
to
go
through
before
before
opening
that
pull
request,
whether
it
they
run
unit
tests,
they
run
integration
tests,
they
have
added
documentation
like
that.
A
Issues
or
feature
requests
have
labels,
because
they're
really
helpful
in
terms
of
the
effort
it
would
take
to
contribute
to
that
particular
issue.
So
is
your
communications
with
protocols.
It
will
save
you
a
lot
of
time
and
will
give
you
a
lot
more
time
working
on
your
features.
Instead
of
resolving
simple
questions.
A
A
You
look
at
you,
look
at
the
proposed
solutions
and
see
what
you
can
learn
from
it
appreciate
your
contributors.
If
they
proposed
a
great
idea,
let
them
implement
it.
Thank
them
in
your
readmes
and
release
notes
and
build
relationships
with
them,
because
they,
they
might
be
your
that
person
that
you
need
to
help.
You
build
out
that
idea
that
you
have
give
credit
for
their
good
thoughts.
A
A
It's
very
hard.
If
you
had
a
tough
day
of
work,
you
opened
the
pr
you
received
about
a
dozen
comments,
your
build
failed,
something
went
into
production
and
it
broke,
and
it
was
your
bug
so
what
we
all
have
bad
days,
let's
learn
from
our
mistakes
and
let's,
let's
let
it
not
get
us
to
stop
imposter
syndrome
is
real
for
a
lot
of
people
and.
A
A
So,
to
sum
up
lesson
number
one
understand
your
responsibility
as
an
open
source
contributor
lesson
number
two.
As
someone
who
uses
popple
library,
give
back
lesson
number
three:
don't
wait
for
the
great
idea
start
small,
build
features,
fix
bugs
lesson.
Number
four
is
communications
with
protocols,
lesson
number
five
learn
from
your
contributors,
lesson:
number:
six!
Don't
let
anybody
grind
you
down
and
lesson
number
seven!
Don't
let
the
imposter
syndrome
hold
you
back.
A
So,
what's
next
for
sql
slide
and
if
my
talk
has
inspired
inspired,
you,
which
I
really
hope
you're
welcome
to
start
contributing
with
my
project
and
I
do
need
help
too
something
I'm
looking
to
do
for
sql
slide
is
to
build
user
interface,
where
you
don't
always
have
to
use
it
as
a
cli
tool.
You
can
actually
see
what
things
are
working
visually.
A
Welcome
to
connect
with
me,
I'm
on
github,
twitter
and
you're
welcome
to
send
me
an
email
and
some
special
thanks
for
people
who
have
contributed
to
my
project
and
helped
me
and
guided
me
and
some
of
the
people
I
have
mentored,
who
also
have
contributed
to
the
projects.
Most
of
them
were
junior
engineers,
and
there
are
always
some
great
tweets
that
I
find
on
twitter.
So
that's
some
special
credits
too.
A
So
I
did
once
did
not
notice,
merge
conflict
and
I
have
released
that
in
a
patch.
What
I
did
is
in
the
end
in
npm.
You
cannot
really
take
back
what
you
did
so
I
had
to
essentially
just
create
a
new
version,
a
new
patch
and
there's
nothing.
You
can
do
at
that
point.
The
mistake
has
been
made.
The
history
has
been
written.
A
A
A
I
can
try.
I
mean
this
was
this
idea
started
and
the
edgardo
gave
me
the
idea
that
gardu
is
my
mentor
and
the
engineering
manager.
He
encouraged
me
to
build
this
and
what's
next
is
up
to
my
imagination
and
the
commitment
that
I
would
have
through
my
new
project,
there's
still
a
lot
of
work
to
work
on
this
one,
but
I'm
not
stopping
on
where
I
am.
If
you
have
a
great
idea,
I
would
love
to
hear
from
you.
If
you
see
there
is
a
need,
then
you
need
someone
to
build
it.
A
A
It's
hard
to
remember,
I
think
the
first
time
I
had
to
build
add
something
to
open
source
was.
It
was
a
popular
library
that
I
was
using.
I
don't
recall
the
name
at
this
point.
It
was
something
that
the
library
did
not
offer.
So
it
was
a
feature
that
I
needed
for
my
for
the
project
I
was
working
on,
so
I
essentially
found
the
need
and
opened
opened.
The
issue
opened
the
pr
and
contributed
to
that
project,
and
that
feature
is
still
there.