►
Description
INFOSTRUX is a Dagster technology partner. They help organizations select and implement the best possible technology to meet their business goals. In this video, Nasko Grozdanov (Manager, Engineering) explains the business benefits of using Dagster over Airflow.
A
A
Fundamentally,
teams
are
excited
to
build,
you
know,
workflows
in
texture
and
they're,
tired
of
doing
it
on
airflow
and
that's
a
significant
elements
to
a
choice
of
Technology.
You
know
the
ability
to
attract
talents
to
a
particular
piece
of
work
over
a
long
term
and
also
to
minimize
you
know,
fatigue
and
and
churn,
and
then,
when
the
teams
are
using
Dax
against
airflow,
like
we
see
a
far
higher
rate
of
development,
you
know
they're
they're,
able
to
close
the
loop.
A
Far
quicker
Daxter
has
a
really
amazing
platform
to
be
able
to
develop
locally,
as
well
as
in
your
deployment,
using
like
Branch
deployments.
Things
like
that
and
teams
are
able
to
iterate
very
quickly,
try
ideas
out
very
quickly
and
put
a
protection
and
have
them
work,
and
then
what
I'm,
seeing
with
teams
is
that
you
know
the
testing
of
those
of
the
orchestration,
the
Automation
and
the
workflows
that
you're
able
to
build.
It's
not
an
afterthought
right.
A
It's
kind
of
you
don't
have
to
bring
that
to
the
table
to
exercise
for
you
with
other
tools.
You
often
have
to
create
that
yourself
and
kind
of
finally-
and
this
is
been
my
experience
a
few
times
already-
is
that
when
you
encounter
issues
you
know
we're
able
to
get
in
touch
with
the
the
team
directly,
they
have
an
open,
Slack
Channel,
where
you're
able
to
communicate
with
them
and
resolve
issues
that
you'd
think
would
take
you
a
week
or
something
like
that
and
actually
get
resolved
very
quickly.
A
Really
creates
the
incentive
to
have
a
single
control
plane
end
to
end
for
all
your
data
right
and
what
you
see
with
time
is
that
teams
will
integrate
into
their
into
Dexter
earlier
and
later
portions
of
the
data
cycle
that
would
normally
be
handled
by
other
pieces
and,
and
so
it
creates
the
incentive
to
be
more
transparent.
With
all
the
steps
that
are
involved
with
the
data
foreign.
A
Dexter,
instead
of
airflow,
is
honestly
kind
of
a
multi-faceted
question.
The
first
thing
is
that
the
you
know
the
experience
for
end
users,
the
user
interface
and
all
that
is,
from
our
point
of
view,
more
approachable
than
airflow.
You
get
the
information
faster
things
like
error
logs
are
just
a
click
away
right
instead
of
three
clicks
away.
A
So
it's
it's
details
like
those
it's
an
appealing
platform
that
is
Pleasant
to
use
and
that
matters
more
than
you
think,
on
a
day
to
day
right,
then
we
find
that
we
have
to
write
less
code
in
order
to
produce
the
end
result
that
we
want
the
dependencies
being
determined
implicitly
rather
than
having
often
to
be
specified
explicitly
as
something
that
you
know
it
avoids
redundant
code
and
makes
it
easier
for
teams
to
collaborate.
A
Availability
of
a
platform
like
Baxter
cloud
serverless,
really
means
that
teams
can
consider
using
it
far
earlier
than
airflow.
In
our
experience,
you
have
this
sort
of
low
barrier
to
entry
in
order
to
start
using
the
product
there
for
even
small
teams
and
it's
able
to
grow
with
you
and
has
all
the
same.
You
know
ability
to
deploy
hybrid
or
on-prem,
as
you
would
with
a
more
complex
tool
like
airflow
but
you're
able
to
approach
it
far
earlier
in
your
journey.
A
It's
really
kind
of
a
game
changer
for
us,
like
typically
with
DBT
you'd,
go
from
something
that's
a
little
bit
too
rudimentary
to
then
having
to
make
the
massive
jump
to
using
airflow,
and
you
would
only
do
that
for
really
sophisticated
teams
and
quite
large
teams
right,
whereas
with
Dax
or
you're
able
to
kind
of
from
day
one.
If
you
want,
even
with
a
team
of
one,
even
very
small
team.
A
You
know
if
you're,
using
something
like
the
extra
cloud,
serverless
you're
able
to
have
that
tool
right
away
and
the
level
of
technical
debt
that
you're
experiencing
is
very
low.
So
for
us
it's
it's
just
far
broader
in
terms
of
in
terms
of
the
teams.
A
We
can
introduce
it
to
and
we're
seeing
teams
that
are
very
small,
asking
us
excitedly
about
it
or
asking
us
to
implement
it
for
them,
and
I
mean
teams
of
one
teams
of
three
things
like
that,
because
for
them
the
trade-off
between
technical
debt
and
the
value
they
get
is
overwhelmingly
advantageous.