►
From YouTube: KBE Insider Amsterdam - Joris Cramwinckel, Ortec Finance
Description
Join Joris Cramwinckel, Technologist at Ortec Finance, as he discusses how Kubernetes, Red Hat OpenShift, and cloud-native microservices have enabled Ortec Finance to provide innovative SaaS solutions. Joris also explains how containerization has reduced complexity in Ortec Finance's development processes and improved CI/CD performance.
Tune in to learn why Ortec Finance turned to Red Hat OpenShift to cost-effectively build and deploy Fintech applications at scale.
A
B
B
B
C
B
C
B
C
B
B
A
B
A
And
event,
driven
as
well
I
mean
because
typically
in
fintech
right,
a
lot
of
stuff
is,
you
know,
because
I
did
I
was
a
consultant
for
a
long
time,
a
bunch
of
that
was
in
fintech
or
financial
services.
I
actually
did
some
work
for
Thompson
speaking
of
software
as
a
service
about
making
good
decisions.
A
But
you
know
a
lot
of
those
architectures
have
been
Enterprise
service
bus.
You
know
kind
of
event-driven
architectures
for
a
long
time
is.
Was
your
environment
like
that?
Or
was
it
more
kind
of
you
know,
because
in
some
ways
modeling
is
more?
Like
a
you
know
you
put
in
the
the
parameters
right
and
outcomes,
an
answer,
yeah.
B
Yeah,
so
we
don't
have.
We
have
event-driven
architectures
at
the
moment,
just
because
the
yeah,
the
the
the
cloud
native
stack,
allowed
us
to
embrace
these
new
paradigms
more
easier
than
in
traditional
Ops
right
now,
on-premise
operations,
these
type
of
structures
are
not
not
supported,
but
in
in
in
a
nutshell,
we
we
build
a
lot
of
calculation
engines
right
yeah
and
some
of
these
engines
are
used
by
by
Banks
large
Dutch
Banks.
C
C
A
C
B
C
B
B
Yeah
yeah,
it's
still
assured
yeah,
so
so
yeah.
We
also
have
yeah
in
in
terms
of
doing
stuff.
Well,
like
forecasting,
the
balance
sheet
of
a
pension
fund
is
a
single
responsibility
thing
right
right.
You
can
imagine.
We
have
600
lines
of
code
they're
doing
that
yeah,
and
these
are
these
are
so
so
we,
our
product
ranges
from
from
web
web
products
with
GUI
without
GUI,
with
only
API,
but
also
more
and
more
traditional
desktop
products.
C
B
C
A
A
Yeah
yeah
well,
I
mean
and
I'm
sure
that
kind
of
containerization
is
also
allowed
a
lot
more
of
your
kind
of
code
reuse
in
different
scenarios,
right
where
you
probably
had
a
lot
more
custom.
Things
like
one
thing
that
worked
for
desktop
and
one
thing
that
worked
for
I,
don't
know
mobile
right
and
now,
with
the
containerization.
C
C
B
A
A
B
A
C
B
B
A
B
A
You
know-
and
my
part
of
my
examples
was
like
yeah
in
in
our
in
that
building
alone,
so
yeah
16
floors,
but
still
it
has,
you
know
trash
cans.
You
know
everywhere,
but
every
single
trash
can
has
scales
in
it
that
you
can
get
real-time
data
of
the
weight
in
that
individual
trash
can
and
one
of
the
really
cool
things
that
Boston
University
has
done
with
their
contracts.
Is
that
now,
if
they
hire
a
vendor
to
do
I,
don't
know
scales
and
trash
cans,
I.
A
A
A
C
A
So
what
do
you
think
is
you
know
kind
of
from
your
perspective?
What
do
you
think
is
going
to
be
the
next
kind
of
big
change?
Is
it
going
to
be
kind
of
getting
all
those
things
to
like
a
cloud
native
scenario?
Is
that
really
the
next
major
point,
or
are
you
already
looking
at
something
else
on
the
horizon
that
you
think
is
going
to
impact
your
you
know,
approach
to
these
problems
that
you
know
kubernetes
or
openshift,
or
you
know
these
these
tool
chains
kind
of
help,
enable
or
help
you
think
about.
C
B
Yeah
yeah
yeah,
you
fought
your
battles
and
sometimes
it
converges
and
and
and-
and
you
see,
Engineers
becoming
better
every
time
in
embracing
new
technologies
and
platforms
play
a
big
role
in
in
in
into
broadcast
these
new
technology
to
our
Engineers.
The
biggest
challenge
now
is
to
to
change
the
humans,
like
the
the
the
organization
aspect
to
to
these
technology
changes.
I'm
a
strong,
strong
believer
of
Conway's
law.
C
B
You
communicate
as
an
organization
right
and
as
a
company,
we
have
four
different
units,
and
so
you
have
four
different
pieces
of
software:
four
addition
pieces
of
software,
but
also
catering,
four
different
markets.
So
these
cultures,
although
we
are
headquartered
in
in
the
Netherlands
and
and
yeah,
we
do
have
a
large
International
workbase
but
I
see
so
many
differences
within
the
teams.
Already
yeah
yeah.
A
B
A
C
B
B
B
In
the
financial
sector,
you
should
you
can't
release
fast,
always
yeah.
If
you
ship
a
SARS
solution
to
a
bank,
you
cannot
do
that
twice
a
week
right,
you
can.
The
bank
is
not
equipped
to
do
that
or
most
banks
are
not
yeah.
So
what
happens?
Is
you
don't
ship
new
gold,
you
ship
new
configuration
yeah
more
often
and
yeah
there's
way
different
Dynamics,
so
we
now
Implement
a
kind
of
get
Ops
a
GitHub
stack.
Some
people
are
not
familiar
with
code
right
so.
A
A
A
With
with
the
project
we
worked
on,
we
were,
we
were
looking
for
a
way
to
basically
kind
of
like
change,
how
authorization
and
authentication
worked
in
the
existing
system-
yeah
yeah-
and
we,
you
know,
budgeted
for
like
a
three-month
project
or
whatever
to
do
this
work,
and
when
we
were
working
on
it,
I
kind
of
saw
this
way.
We
could
kind
of
kind
of
slide
it
in,
and
so
we
were
done
in
like
a
month
yeah,
but
we
we
missed
the
release
day
by
by
a
day
two
days
or
something.
C
C
B
B
You
know,
methods,
yeah
and
and
when
it
really
comes
to
the
surface,
is
when
you
design
your
github's
flow,
because
that's
really
fun
actually.
Last
week
we
did
that
with
the
team,
that's
responsible
for
configuration
and
then
that's
where
the
technology
and
the
process
come
together
right.
So
then
we
thought,
okay,
how
do
you
want
it
to
work
and
right?
B
How
does
it
go
right
now
and
a
lot
of
handshakes,
a
lot
of
handovers
which
we
now
in
in
the
current
realm
we
can.
We
can
automate
right
and
also
with
the
git
Ops,
it's
so
powerful.
You
can
program
your
your
policy.
So
if
someone
does
an
updating
configuration,
you
can
say:
okay,
someone
who's,
not
the
author,
who
has
this
role
in
the
in
the
ad
group
of
the
company
is
allowed
to
to
merge
this.
A
A
Yeah
I
think
I
missed
a
turn,
so
I
was
just
checking
to
see
if
I,
a
small
detour
yeah,
so
we'll
tour
this
little
part
of
the
Amsterdam
yeah.
So
it's
I
think
you
know,
as
we
you
know,
as
we
were
able
to
divorce
a
lot
of
the
you
know:
kind
of
the
operating
environment
from
the
application
environment.
You
know
using
containers
and
kubernetes,
and
you
know
things
like
that.
I
think
it's
it's
getting
interesting
about.