►
From YouTube: Scaling Hyperledger Fabric networks
Description
A virtual meetup hosted by Hyperledger Toronto on April 15, 2021 featuring Tsvetan Georgiev, the co-founder of Senofi Inc. He talks about scaling permissioned blockchain networks based on Hyperledger Fabric. Having the right design when building and operating a network is essential for many use cases (i.e. supply chain) that depend on proper scaling and transaction throughput. We will discuss the heterogeneous nature of the networks and why cross-cloud deployments are essential.
More about the event is at: https://www.meetup.com/Hyperledger-Toronto/events/277310163/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerMeetups #Blockchain
A
Seconds
all
right,
you
were
live
on
youtube.
You
can
take
it
away.
I'll
drop
the
link
in
the
chat
as
well.
Thank
you,
david.
Thank
you
all
right,
then
hello,
good
day,
good
morning,
good
afternoon.
Everyone
welcome
to
the
hyper
ledger:
toronto,
meetup
groups.
Monthly
event.
My
name
is
laszlo
shandor
and
I'm
one
of
the
co-organizer
of
this
group.
A
He
is
a
co-co-founder
of
a
company
called
sanofi,
where
his
main
focus
is
product
development,
product
management
and
the
development
of
consortia
even
before
he
founded
or
co-founded
sanofi.
He
had
been
in
blockchain
and
had
experience
with
implementing
hyperledger
fabric
networks
in
many
and
multiple
industries
like
healthcare,
insurance
and
so
on.
He
brings
20
years
of
enterprise
software
engineering
experience
and
personally,
I
met
him
a
couple
of
years
ago
or
several
years
ago.
A
By
now
when
he
was
with
the
previous
company
and
they
did
hyperledger
fabric
training
in
toronto,
and
I
liked
it
a
lot.
I
think
at
that
time
many
company
companies
tried
to
open
courses
on
blockchain
and
hyperledger
fabric,
but
I
found
his
material
and
his
classes
very
useful,
which
I
used
it
for
a
long
time,
long
time
after
before
I
give
it
over
to
to
zlatan
to
take
it
away.
A
A
A
But
if
you
would
like
to
have
these
socks,
which
I
just
showed
you
when
you
send
a
question
in
the
either
in
the
chat
in
the
zoom
or
on
youtube,
I
will
keep
an
eye
for
that.
Also
mention
your
city
and
at
the
end
I
will
draw
someone
and
we
will.
We
will
figure
out
how.
How
can
I
mail
this
to
you
without
any
further
ado,
I
like
to
invite
at
zlatan
on
the
stage
and
please
take
it
away.
B
Thank
you
thanks
for
the
nice
words
and
yeah,
let's,
let's
dive
into
it,
a
bit
of
gap,
you,
you
said
a
lot
about
me.
Thanks
for
the
nice
words
again,
the
let
me
see
how
I
can
flip
the
slides
a
bit
more
to
it
on
what
I'm
doing
professionally
again,
we
are
actually
focused
on
hyperledger
fabric
as
our
technology
stuck
and
our
main
product.
Apart
from
the
services
we
provide
for
the
projects
is
consortiio,
and
that
is
a
software
as
a
service.
B
We
filled
the
gap
that
was
there
since
the
beginning
to
actually
manage
those
networks
across
clouds
across
business
partners
that
are
on
the
consortium,
and
that
is
very
essential
part,
because
that
brings
a
lot
of
complexity
and
even
though
the
steps
to
do
that
management
are
pretty
well
well
described
and
and
clear
from
documentation,
point
of
view
from
community
point
of
view,
they're
all
manual.
So
that's
why
we
built
consortia
to
automate
all
of
those
steps
and
make
it
easier
for
the
end
users
to
manage
the
hyperledger
fabric-based
networks
and
applications.
B
B
Of
course,
it
is
in
the
context
of
private
and
permission
blockchains,
not
in
the
context
of
public
blockchains
like
ethereum
or
bitcoin.
I
just
want
to
make
the
draw
draw
the
line,
because
it's
it's
extremely
different
to
actually
the
way
you
manage
scalability
on
those
networks
and
have
in
mind
that
permission,
private
networks
are
more
or
less
networks
that
a
particular
set
of
partners
have
control
over,
so
that
that's
what
we'll
be
talking
about
today.
B
So
the
agenda
is,
I
will
just
quickly
talk
about
what
scalabilities
in
general,
just
to
set
the
context
right,
so
you
know
what
what
areas
will
be
discussed
and
then
I
will
be
actually
focusing
more
on
to
what
scalability
means
for
distributed:
ledger
technologies
and
hyperledger
fabric
in
particular,
and
it's
not
just
about
talking
for
software
scalability
in
general,
it's
it's
more
or
less.
What
are
the
most
essential
and
important
topics
or
constraints?
B
B
So
it
is
very
realistic
to
expect
that
they
will
work
on
on
different
clouds.
That's
why
or
infrastructure.
It's
not
even
necessarily
a
crowd
cloud,
that's
why
cross
clouds
topic
is
essential
and
I
will
leave
25
minutes,
hopefully
for
questions
and
answers.
I
want
to
like
take
probably
half
an
hour
to
go
through
the
content
and
have
an
open
discussion,
make
it
more
interesting
and
probably
answer
questions
and
have
a
have
a
brainstorm
or
discussion
on
it.
So
in
general
what
scalability
is.
B
It
is
very
broad
topic
to
be
honest:
I'm
not
claiming
I'll
cover
everything.
Don't
get
me
wrong.
It's
it's!
It's
extremely
technical
and
complex.
There
is
a
lot
of
theory
behind
that.
I
just
put
couple
of
dimensions
here
that
are
actually
essential.
This
is
scalability
in
terms
of
that
administrative
scalability.
That's
that's!
B
You
have,
of
course,
the
functional
scalability
shortly.
It
is
about
enhancing
the
the
system
by
adding
new
functionalities
again
very
well
implemented
in
the
context
of
hyperledger
fabric.
It's
not
just
about
chain
codes.
Of
course,
I'm
talking
even
about
the
so-called
plugins,
where
you
can
actually
adjust
the
network
behavior
on
the
peer
level
by
implementing
some
system
chain
codes,
for
example,
to
verify
the
to
change
the
default
behavior.
B
You
have
on
it
at
a
particular
point
of
time.
This
is
essentially
extremely
complex
in
terms
of
hyperledger
fabric.
If
you
look
at
the
network
as
a
whole
and
we'll
go
through
those
things
in
in
a
minute
or
two
and,
of
course,
horizontal
and
vertical
scaling,
I
think
they're,
the
most
famous
or
the
most
talked
about
in
the
industry.
B
B
We
will
talk
about
what
a
happy
legit
deployment
actually
usually
looks
like
so.
First
of
all,
I
I
just
want
to
mention
that,
with
the
distributed
and
decentralized
networks,
it
is
not
one
one
time
thing
in
terms
of
topology:
it
is
not
something
that
is
set
in
stone.
Those
networks
are
actually
designed
and
supposed
to
grow
or
actually
reduce
it
in
in
size.
Speaking
of
you
know,
considering
the
number
of
organizations-
maybe
organization
or
business
partners
will
join
the
network.
Some
may
leave
the
the
network.
B
New
peers
will
be
added,
new
peers
will
be
removed.
So
that's
why
the
deployment
that
you
usually
start
with
over
time
changes
significantly.
So
when
you
are
organizing
the
first
thing
you
do
usually
is
to
organize
your
infrastructure,
think
about
it,
the
machines
or
the
computers.
That's
gonna
be
used
to
to
manage
the
lot
or
too
many
to
to
run
your
notes,
your
peers,
orders
and,
and
all
that.
B
So
this
is
where
you
actually
decide
on
what
infrastructure
to
use,
and
usually
people
go
with
different
cloud
providers
or
maybe
the
same
cloud
provider
and
different
geographic
locations,
and
the
reason
is,
I
already
explained
why
it's
important.
Then
you
deploy
your
organization
and
notes
from
fabric
perspective.
B
B
Those
consumers,
of
course,
could
be
your
clients
or
maybe
internal
clients,
of
your
solution,
depending
on
the
business
case
and
of
course,
last
thing
that
is
extremely
important
and
complex
to
manage.
Is
the
network
governance
they've
been
efforts
to
actually
streamline
the
the
governance
process
across
providers,
but
yeah
so
far?
It
is
something
that
is
out
of
bounds
from
hyper
fabric
perspective.
B
So
what
is
actually
about
now
scaling
about
hyperledger
fabric
networks?
So
first
is
about
scaling
the
consortium
okay,
so
it
is
here
not
about
adding
new
nodes.
I
want
to
make
a
note
here.
It
is
about
actually
adding
new
partners
that
come
with
their
own
notes.
Okay,
so
those
partners
that
join
your
consortium
are
actually
bringing
usually
should
be
bringing
their
own
notes,
and
what
is
important
here
to
consider
is
that
onboarding
of
business
partners
on
a
consortium
could
be
actually
onboarding
on
a
preset
network.
B
What
I
mean
by
that
is
that
those
business
partner
may
not
necessarily
have
notes
with
them.
It
could
be
a
process
where
someone
provision
notes
or
the
consortium
provision
notes
for
those
partners
and
onboards
them,
or
the
other
option,
of
course,
is
when
the
partners
that
are
joining
are
already
part
of
or
already
run
nodes,
and
they
just
want
to
add
their
nodes
onto
the
network
and
and
start
being
part
of
the
transactions.
B
So
that
is,
I
have
a
picture
nice
I
hopefully
you're
gonna
like
it
in
a
while
to
make
it
more
visual.
What
I
mean
by
that,
because
I
want
to
put
it
in
a
context,
in
my
case,
it's
a
supply
chain
context
very
easy
to
explain
very
intuitive,
to
understand
so
scaling
your
notes,
orders
and
peers,
as
I
mentioned
vertical
and
horizontal
scaling.
B
Okay,
as
soon
as
you
put
the
whole
network
in
a
single,
let's
say
cloud
provider
on
a
single
kubernetes
cluster,
if
you
wish
to
actually
streamline
and
to
make
the
scaling
more
simple,
you're,
essentially
centralizing
everything
in
some
cases
that
might
make
sense,
but
in
many
cases
that
defeats
the
purpose
of
using
distributed
ledger
technology
because
essentially,
even
though
they
are
distributed,
you
are
still
centralizing
them
on
the
same
infrastructure
and
horizontal
scaling
from
hyperledger
fabric
perspective.
That
is
essentially
adding
more
computational
resources.
B
So,
let's,
let's
take
as
an
example,
think
about
it
that
two
partners
are
actually
hosting
peers
and
one
of
the
partners
is
actually
able
to
at,
like,
let's
say,
new
cpus
on
their
infrastructure
to
handle
the
load
of
the
transaction
during
lunch
time,
because
you
know
their
users
decide
to
do
most
of
their
daily
transaction
during
lunch
lunchtime.
So
they
want
to
like
make
the
system
available.
B
B
B
So
it's
it's!
What
I
mean
to
say
here
is
as
well
that
it's
it's
extremely
hard,
unfortunately,
to
synchronize
those
efforts
in
reality.
Let's
be
realistic
right
here.
You
cannot
expect
that
now
imagine
a
network
of
10
partners
how
you're
going
to
synchronize
the
efforts
to
actually
scale
up
and
increase
the
transaction
processing.
B
Okay.
So
when
people
are
talking
about
transaction
throughput-
and
you
know
saying
hey
how
many
transactions
hyperledger
fabric
or
whatever
x
technology
can
process
on
the
chain
and
people
come
up
with
measurements.
Usually
those
measurements
are
taken
out
of
a
test
system
where
everything
works
in
one
box,
but
that's
the
best
case
scenario,
but
that's
not
realistic.
B
B
Okay.
So
this
is
a
picture
here
of
how
we
actually
at
a
new
partner
on
the
network.
Here
in
my
example,
as
you
see,
I
have
in
the
circle
an
existing
consortium
of
processor
farmer
and
retailer
think
about
that.
These
guys
are
actually
tracking
lettuce
on
the
network
from
the
farmer
to
the
retailer
shelves,
and
in
that
case
they
want
to
scale
their
network
by
adding
the
regulator.
B
Why
is
that?
Because
there
are
many,
many
businesses
out
there
that
run
or
use
many
many
suppliers
or
vendors,
and
they
may
not
even
understand
what's
going
on
down
below
the
chain
right,
so
they
may
be
working
with
the
vendor
and
that
vendor
may
work
with
contractors,
smaller
companies,
smaller
vendors
and
whatnot.
B
So
that
means
think
about
a
company,
a
that
works
with
company
b
and
company
b
works
with
companies
here
right.
So
all
of
those
companies
maybe
may
have
different
relationship
between
them.
They
may
not
even
know
that
they
work
with
each
other,
so
the
onboarding
and
the
deployment
of
their
hyperledger
fabric
peers,
assuming
they
use
coverage
of
fabric,
of
course,
will
be
driven
and
handled
by
each
company
individually.
B
B
If
a
zone
you
know
goes
offline,
you
don't
want
to
risk
too
much
by
hosting
your
peers
in
the
same
data
center
right
so
because
in
that
case,
even
if
you
have
10
peers,
if
the
data
center
goes
down
you're
going
to
lose
all
of
them.
So
that's
why
you
want
to
actually
distribute
them
geographically,
and
that's
not
the
only
reason
why
you
want
to
do
that
think
about
international
consortium.
B
You
may
have
partners
working
together
across
continents
right
one
in
north
america,
one
in
asia
and
they
may
have
their
peers
pretty
far
away
right.
So
here
now
we
are
talking
about
network
latency
right
so
when
they
talk
between
each
other,
depending
where
the
client
is
that's
performing
the
transaction,
the
the
latency
of
the
network
is
gonna,
pay
a
big
role
in
your
transaction
throughput
right.
B
B
Okay,
so
how
a
single
participant
network
may
look
like,
so
here
I'm
having
three
data
centers
and,
as
you
see,
they
provision
different
nodes
in
different
data,
centers,
of
course,
the
nodes
communicate
between
each
other
over
internet,
which
is
a
good
thing.
So
you
can
actually
not
just
provision
them
in
different
data
centers,
but
you
can
essentially
use
different
technologies
to
to
manage
the
net.
The
network
and
the
you
may
use
kubernetes
or
docker
into
different
or
just
you
know,
run
it
on
on
a
physical
machine.
B
B
Of
course,
when
a
transaction
goes,
as
I
mentioned
before,
it
is
important
that
actually
every
every
one
of
the
endorsers
on
the
transaction
have
their
notes
available
and
their
availability
managed
properly,
because
if
one
goes
down
and
endorsement
is
required
by
all
of
them-
that's
very
important
thing.
It
all
depends
on
the
endorsement
policy
you're
using
then
it
will
affect
the
availability
of
the
transaction
as
a
whole
on
the
on
the
tracking
channel.
B
B
Of
course,
if
you're
running
a
transaction
and
you'll
be
having
good
throughput
and
tomorrow,
you
decide
to
change
the
endorsement
policy
and
you
add
another
partner
to
endorse
and
that
partner
does
not
fit
the
view
with
endorsing
properly
or
endorsing
with
the
right
speed.
That
may
have,
of
course,
side
effect
on
the
general
throughput
of
your
transaction.
B
B
B
B
B
B
What's
that
hyperledger
network
or
foundry,
or
or
or
azure
blockchain
as
a
service
hyperledger
fabric
as
a
service
or
or
aws
as
a
service,
it
doesn't
matter
those
cloud
providers
are
not
supposed
to
constrain
a
a
network
or
a
consortium
that
is
actually
combining
nodes
run
on
different
cloud
providers.
It's
counterweight
intuitive
from
their
business
point
of
view.
They
don't
want
you
to
do
that
right,
so
they
want
you,
your
partners
to
run
their
notes
on
your
own
cloud
provider.
B
Reason
is,
of
course,
revenue
right,
but
I
don't
think
that
makes
much
sense,
because
you
cannot
actually
ask
one
single
partner
to
provision
notes
on
10
cloud
providers,
just
because
consortium
can
run
only
on
particular
cloud
providers
that
doesn't
make
sense.
The
cost
is
so
high
forget
about
justifying
it
justifying
running
an
application
based
on
such
network
right.
So
you
cannot
like
invest
millions
of
dollars
on
maintaining
notes
on
different
cloud
providers
just
because
they're
constrained.
A
B
Yeah
right
so
there
is
for
for
hyperledger
fabric
deployment,
I
guess
right
network
deployment
and
peer
deployment.
There
are
a
couple
of
projects
under
hyperledger
fabric.
Already
there
is
a
one
under
hyperledger
lapse
and
it's
maintained
by
the
community.
It's
it's
a
helm,
a
set
of
helm,
charts,
it's
not
just
maintaining
or
supporting
hyperledger
fabric.
It
also
supports
most
of
the
other
blockchain
networks
like
so
too
even
ethereum,
so
I
would
go
and
check
that
open
source
project.
B
B
They
well
documented
what
that
means,
because
you
cannot
scale
raft
indefinitely,
so
there
are
limitations
in
terms
of
how
many
limitation
being
you
know,
what
makes
sense
don't
get
me
wrong
limitation
is
something
that
I
would
say
recommended
setup
of
raft.
Of
course
you
could
try
to
bring
up
like
100
orders
to
serve
a
particular
channel,
but
that
doesn't
make
much
sense
people.
B
Usually
there
is
a
bit
of
misunderstanding
when
I
talk
to
different
people
hyperledger
fabric,
you
know
it's,
it's
it's
channel
based,
so
we're
not
talking
about
the
single
single
ledger
that
is
used
by
everyone
on
the
consortium
we
are
talking
about.
Channels
and
channels
is
a
different
instance
of
a
different
ledger,
so
the
ordering
nodes
are
actually
since
2.2.3.
B
They
made
it
change
the
ordering
service
in
a
way
that
every
order
may
actually
serve
in
different
channels
and
different
channels
can
be
served
by
a
different
order.
So
you
can
actually
add
or
remove
orders
that
are
part
of
a
particular
channel,
so
that
one
actually
gives
you
flexibility
to
actually
manage
an
ordering
node
that
is
actually
ordering
transactions
for
different
channels
or
different
ledgers.
B
That
may
not
necessarily
know
about
each
other
and,
of
course,
capital
edge
of
fabric
community.
Let
me
just
continue
what
I
was
about
to
say
a
minute
ago
is
that
there
is
a
limit
to
the
efficiency
of
the
ordering
service.
Based
on
how
many
ordering
nodes
you
run,
I
had
it
somewhere.
Let
me
just
look
that
up,
but
I
believe
that
they
recommend
to
have
for
a
channel.
Have
that
in
mind
on
a
single
channel.
B
B
One
order
could
be
a
part
of
different
draft
clusters
and
communities
recommending
up
to
11
to
maintain
quorum,
of
course,
for
the
rough
protocol
to
work
and,
of
course,
adding
more
nodes,
unnecessarily
brings
complexity
and
doesn't
give
any
value
so
ordering
service,
keep
it
small,
slim
and
distribute
between
few
partners.
If
you
want
to
just
for
the
sake
of
having
reducing
the
risk
by
one
of
the
partners
going
offline
and
letting
your
channel
when
served
but
yeah,
it
essentially
should
be
kept
to
a
couple
of
notes.
A
B
B
B
They
may
not
necessarily
know
what's
the
metrics
on
the
peers
of
their
partners.
Of
course,
what
they
know
is
the
through
the
service
discovery
is
what
is
the
topology
of
the
network,
but
they
don't
know,
for
example,
what
their
partners
peers
are
running
on,
how
many
cpus
they're
you
know
what
infrastructure
they're
running
on
how
much
they've
been
loaded,
because
those
peers
of
your
partners
may
be
serving
serving
different
channels.
You're,
not
part
of
so
you
just
have
a
view
on
the
topology
through
the
service
discovery.
A
B
It
is,
it
is
all
about
how
it's
configured.
Of
course,
you
can
do
a
high
transaction
throughput,
the
the
complexity
here
and
the
real
challenge,
it's
about
how
to
synchronize
those
efforts
between
the
partners
on
the
network.
You
may
not
always
have
the
chance
to
do
that
and
when
you
accept
partners
into
your
network,
you
have
to
ask
your
question
how
how
much
of
importance
the
transaction
throughput
is
for
you.
B
B
B
But
if
the
company
in
china
provision
appears
in
u.s
and
the
client
is
in
u.s,
of
course,
it
will
be
much
much
faster,
because
it's
all
about
endorsement,
I'm
not
talking
about
committing
the
transaction
on
different
peers
committing.
You
know
as
soon
as
you
have
like
10
peers,
geographically
distributed.
B
You
are
actually
interested
in
making
fast
endorsements,
so
you
can
actually
quickly
stand
to
the
ordering
service
and
then
your
committing
peer
might
be
distributed
and
the
transaction
committing
phase
is
anyways
asynchronous.
So
it
could
happen
later
on.
Some
of
the
peers
might
be
out
of
date,
of
course,
but
they
will
catch
up
relatively
quickly
after
the
transaction
is
done.
A
Somewhere
on
the
youtube
channel,
I
think
referring
to
the
diagram
what
you
have
on
right
now,
where
you
know
you
talk
about
different
participants
over
five
legend
network
and
specifically,
I
think
small
businesses
like.
I
can
imagine
farmers
in
here.
Whoever
farmers
are
not
always
small
businesses.
B
Yeah,
I
think,
and
that's
that's
what
my
company
is
doing
the
cost
actually,
as
of
now
to
on
board
to
provision
the
network
provision.
The
peers
is,
is
high
and
it
the
it's
it's
not
about
that.
Much
of
the
cost
is
not
that
much
determined
because
of
the
complexity,
it's
determined
because
of
the
people
who
the
skills
of
the
of
the
of
the
people
that
perform
the
task.
It's
it's
highly
technical,
let's
be
honest
and
you
go
and
take
you
know
a
helm
chart.
B
B
You
cannot
expect
that
all
of
those
small
partners
will
justify
being
part
of
a
network
they
just
want.
I
mean
it's,
it
doesn't
make
sense
for
them
it's
about
money
right
and
if
they
don't
get
back
what
they
invest,
even
some
of
them
don't
care
so
and
that's
why
reducing
the
cost
and
and
making
it
user-friendly
easy
is
essential
and
for
the
success
of
of
the
whole
technology.
That's
that's
how
I
see
it
and
that's
what
we're
trying
to
do.
That's
what
we're
doing
at
my
company
trying
to
reduce
that
cost.
B
B
As
I,
I
do
think
that
most
of
the
as
of
now
you
know
the
short-term
kind
of
thing
most
of
the
businesses
that
jump
on
on
a
network.
They
will
go
with
a
service
provider
or
a
software
vendor
right,
maybe
small
companies.
Maybe
it
depends
on
what
they
can
afford
right,
but
do
it
yourself
is
we're
far
away,
maybe
few
years
until
the
the
all
the
things
are
simplified
to
a
point
where
a
regular
person
with
a
regular
I.t
experience
can
do
it
by
themselves.
A
But
I
think
it
never
will
be
like
ethereum
or
bitcoin,
where
you
download,
you
know
a
dump
and
you
you
start
up
your
node
and
you
know
start
making
transactions
on
an
effort.
As
you
know,
one
of
the
essential
show
and
benefit
of
permission
based
network
that
you
you.
You
know
you
create
a
consortia,
you
create
a
collaboration,
you
create
rules
on
the
network.
A
B
A
B
With,
as
I
explained
that
since
2.3
they
actually,
when
you
have
a
conservation
right,
the
the
whole
point
was
about
how
many
channels
you
you
may
have
between
organized
particular
set
of
organizations
right
and
more
channels.
You
have.
That
means
you're
loading,
a
bringing
cloud
on
the
ordering
service.
That
was
the
key
design
issue,
or
it
wasn't
even
designed.
It
was
like
more
of
an
implementation
thing
since
2.3
that's
what
they
changed
so
now.
B
You
actually
may
have
an
ordering
note
serving
x
amount
of
channels,
so
you
you
may
have
the
same
order
or
different
orders
serving
different
channels,
so
you
don't
need
to
actually
have
one
ordering
service
to
serve
thousands
of
channels.
You
can
break
them
down
in
a
way
that
a
particular
set
of
orders
has
to
explain
up
to
nine
or
eleven
to
maintain
a
good
performing
craft
cluster
may
serve
particular
set
of
channels.
B
I
think
they
come
up
with
something.
That
is
how
many
let
me
cross
check
that
I
think
50
channels
on
an
ordering
node.
So
if
you
need
to
grow
more,
you
bring
another
ordering
node,
of
course,
to
serve
the
rest
of
the
channel.
So
that
that's
that's
been
solved
more
or
less
since
2.3,
so
essentially
you
keep
in
heading
ordering
notes
to
serve
your
additional
channels
if
you're
part
of
those,
like
you
know,
hundreds
of
channels,
of
course,
managing
those
channels
is
a
challenge.
B
A
Okay,
so
we
are
just
one
minute
after
the
hour,
if
you
don't
mind
to
just
address
one
more
question
in
the
meantime,
do
you
have
the
time
yeah,
I'm
fine,
okay,
just
one
more
question:
until
you
answer
it,
I
will
make
a
random
selection
and
draw
the
precious
prize
of
today
the
ibm
blockchain
original
socks
for
today.
If
anyone
interested
who
answered
any
questions,
so
the
question
is
from
david
events:
can
you
talk
about
the
msp
organizations
to
a
network
when
they
have
their
own
certification
authorities.
B
So
when
you're
talking
about
a
membership
service
provider,
you're
talking
about
a
entity
logical
entity
defined
by
by
the
certificates,
what
that
certificate
authority
is
behind
that
issues,
the
certificates,
it's
it's
a
it's!
It's
an
open
thing:
you
you,
it
could
be
any
certificate
authority
and
it
could
be
fabric,
ca,
hosted
and
managed
by
the
partner
or
it
could
be
their
own
existing
certificate
authority.
So
I
know
about
deployments
of
you
know,
use
case
where
the
company
already
have
their
own
certificate
authority
and
then
they
use
it
to
define
their
msp
msp.
A
Thank
you
thank
you,
xvatan
and,
having
that
said,
let's
conclude
this
meeting
I'd
like
to
announce
that
the
lucky
winner
is
yakar
josef
johnson,
so
jakar.
If
you
can
send
me
a
private
message
with
your
email
address,
or
I
can
put
my
email
address
into
the
the
chat
in
here
and
you
can
email
me
if
you're
interested
in
the
socks
I'm
more
than
happy
to
mail
it
to
you.
A
I
appreciate
your
time
for
today,
whatever
you
called
in
from
whether
it's
you
know
lunchtime
in
eastern
time,
zone,
eastern
east
coast
or
a
morning
session
was
for
you
in
the
west
coast
strathan,
I'm
always
enjoying
listening
to
you
and
the
knowledge
you
share
as
as
now
as
in
the
past.
I
really
appreciate
your
time
as
well
and
your
contribution
to
this
community.
I
think
it
will
be
great.
A
I'm
pretty
sure-
and
everyone
please
remember-
the
hyperledger
global
forum
is
going
to
be
on
the
june
june,
8th
to
10th.
It
will
be
virtual
this
year
and
remember
to
register
and
participate
last
year
was
amazing,
a
really
good
presentations
and
speakers.
So
I'm
sure
it
will
be
same
this
year
and
you
can
join
from
the
comfort
of
your
home.