►
From YouTube: Demo: Are Hyperledger Fabric and Microsoft SharePoint Frenemies? - Dominik Zyskowski, Espeo
Description
Demo: Are Hyperledger Fabric and Microsoft SharePoint Frenemies? - Dominik Zyskowski, Espeo Blockchain
We will provide a real case demo presenting Hyperledger Fabric with Microsoft Sharepoint. Connecting enterprise blockchain and standard cloud-based solution for sharing and processing documents shows a new angle on blockchain use cases. With over 200 million users SharePoint - based solutions are used in multiple industries. This solution can be enhanced with blockchain technology. The audience will get an understanding of the business and technical aspects of integrating those two enterprise technologies.
Sessions Details & Slides (if available): https://sched.co/19HDy
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
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
Discord: https://discord.gg/rVCn4j7UFd
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 #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
A
It's
done
for
our
clients,
hrp
International,
so
they
are
somehow
SharePoint
based
organization
and
they
still
wanted
to
to
use
blockchain
as
a
backbone
of
the
Iran
Solutions.
So
why
the
title
I
it's
a
bit
tricky.
We
wanted
to
also
show
you
that
it's
probably
it's
possible
to
combine
closed
Source
projects
like
and
paid
software
like,
like
SharePoint
with
with
open
source,
my
name
iskowski
I'm
Consulting
director
in
a
store
blockchain,
and
we
as
a
company,
are
one
of
hypers
certified
sales
providers.
So
we
are
service
based
component.
A
A
So
as
I
as
I
told
you,
Fabric
and
SharePoint
are
totally
kind
of
different
words
from
one
side,
we
have
open
source
project
that
is
maintained
and
developed
by
many
people
around
the
world.
On
the
other
hand,
there's
a
Microsoft
based
system
that
is
their
proprietary
software,
and
it's
it's
not
open
source.
You.
A
Maybe
about
storing
the
data
in
the
secure
and
and
trustworthy
way,
although
they
have
totally
different
philosophies
behind.
So
from
one
side,
we
have
a
centralized
solution,
it's
a
centrally
kept
access
rights
and
permissioned
roles.
On
the
other
hand,
fabric
is
about
trying
to
provide
a
decentralized
way
of
accessing
the
data
still
with
allowing
for
having
different
permissions
across
different
different
users.
A
Data
government
models
are
also
a
bit
different
in
fabric.
We
have.
The
part:
is
that
somehow
allowed
to
to
determine
the
access
rights
of
of
other
organizations
and
and
users
that
form
the
network
in
SharePoint
we
have
centrality,
managed
user
management,
permissions
management
and
also
the
data
storage.
A
A
The
business
case
is
about
exchanging
referrals
between
the
members
of
hrb
Internationals,
so
hlb
is
a
Global
Network
of
academic
and
advisory
companies.
They
work
on
under
umbrella
of
hrb,
but
in
fact
every
country
has
its
own
kind
of
business
entity
that
is
independent
from
one
from
another.
There
is
totally
different
invoicing
systems,
Erp
systems
and
and
all
the
systems
that
handle
the
operations
of
the
companies
and
the
only
common
common
tool
that
is
used
worldwide
is
SharePoint,
which
is
a
communication
platform
for
them.
A
A
Up
till
now,
it
was
happening
through
kind
of
emails
or
phone
calls,
or
some
some
kind
of
of
offline
messages
and
therefore
it
it
was
quite
cumbersome
for
the
Global
office
of
hlb
to
handle
the
disputes
between
the
member
firms
to
to
settle
the
the
payments
that
were
due
and
in
fact,
the
team
of
of
a
few
people
in
the
in
the
Executive
Office
of
the
company
was
spending
like
a
few
weeks.
Every
year
to
to
handle
manual.
A
Of
course,
there
was
no
single
sort
of
friend
and
and
therefore
it
was
quite
hard
to
follow,
who
referred
the
company
to
who
and
whether
that
that
lead
was
really
converted
to
the
client
and
what
were
the
payments,
Associated
and
so
on.
So
although
the
process
looks
kind
of
quite
quite
simple
because
having
a
referral
offered
to
the
company,
the
company
that
receives
a
referral
can
either
write
a
data
accept
and
then
they
need
to
contact
the.
A
Need
to
to
make
a
proposal
and
the
proposal
may
be
successful
or
not,
and
after
the
proposal
is
successful,
the
cooperation
start
started
to
the
client
there's
some
some
Billings
on
invoicing
and
the
company
that
referred.
The
client
should
should
be
awarded
with
some
percentage
from
the
total
value
of
the
of
the
deal.
A
We
to
cover
with
our
client,
wanted
to
automate
and
somehow
digitalize
the
process
with
using
the
tool
that
everyone
in
company
is
using.
So
we
do
using
the
user
interface
from
the
SharePoint,
but
still
to
have
the
centralized
place
in
which
the
data
is
trustworthy
and
it's
validated
and
no
one
can
I
can
say
that
the
the
data
or
the
referral
was
kind
of
fake
or
not
not
valid.
A
A
We
have
two
virtual
machines
with
with
blockchain
nodes,
so
one
one
fabric
note
is
actually
each
each
fabric.
Node
is
in
different
region
and
the
the
topology
of
the
network
is
is
quite
simplistic,
but
that
was
kind
of
good
enough
for
the
kind
of
for
this
first
implementation
for
HIV,
because
in
fact
it's
the
the
first
boxing
project
that
I
that
they
realized
and
the
first
option
product
that
is
going
to
be
released
to
the
production
and
it's
happening
today.
A
A
B
A
So
here,
basically,
we
have
a
kind
of
normal
dashboards
that
that
HIV
users
can
see.
Of
course,
this
is
the
admin
view,
which
means
that
we
are
able
to
to
switch
users,
but
normally
the
users
can
see
only
the
the
elements
that
they
are
able
to
see
on
on
their
on
their
boards,
and
this
particular
widget
can
be
used
to
to
create
new
referrals
and
send
them
to
the
to
the
other
company
from
the
hrb
group.
A
A
It's
also
important
that
we
store
on
the
on
the
blockchain
all
the
data
associated
with
the
with
the
referral.
It's
it's
not
a
big
amount
of
data,
so
we
decided
to
to
store
everything
here.
We
also
determine
the
the
field
of
the
service,
the
type
of
the
industry
of
the
client
and
and
we
can
send
the
referral
yeah
with
sending
the.
Therefore
we
also
specify
the
predicted
value
of
the
of
the
deal.
A
A
So,
for
now
this
new
client
is
is
handed
over
and
the
Vietnamese
entity
will
be
able
to
to
see
it
on
the
dashboard
when
it
it
gets
to
the
to
The
Ledger,
it's
quite
important
also
for
the
users
that
they
are
able
to
see
whether
the
particular
refiller
already
made
it
to
the
to
the
blockchain.
So
we
also
added
this
type
of
indicators
that
show
that
the
particular
referral
particular
event
or
building
was
was
added
to
the
to
The
Ledger,
and
now
we
are
switching
the
context
to
the
Vietnamese
entity.
A
We
see
that
in
the
in
the
receive
referrals
we
see
the
the
new
one
and
now
what
what
usually
happens.
It's
that
the
discussions
with
the
client
they
last
for
the
last
several
months
yeah.
So
all
the
all.
These
statuses
of
the
of
the
particular
referral
will
be
also
stored
on
the
on
the
blockchain
on
the
fabric
level.
In
order
to
to
see
when
the
particular
status
was
changed
and
what
was
happening
with
that,
we
need
to
somehow
go
faster
with
that.
So
we
we
change
the
statuses
like
from
the
accepted
through
contacted.
A
A
The
amount
of
data
of
the
two
chain
is
quite
minimized.
It's
simple
Json
file
that
that
gets
gets
saved
in
the
chain,
but
it's
also
quite
important
to
the
to
the
user
that
they.
They
may
really
trust
that
this
data
is
is
really
stored.
They
will
not
be,
it
will
not
be
changed
and
it
also
increases
the
amount
of
trust
between
the
companies
yeah
that
are
still
in
the
the
same
network,
but
they
they
may
not
before.
A
So
here
we
we
can
see
the
list
of
transactions
and
you
can
see
that
the
company
was
the
status
was
changed
to
contacted
so
another
transaction
in
another.
It's
it's
a
new
status.
It's
the
status
proposal
to
send
next
one
will
be
hopefully
succeed,
which
means
that
that
the
deal
was
was
done
and
the
client
restarted.
The
cooperation
with
that
particular
company.
A
A
And
that's
basically
it
from
the
scenario
point
of
view,
so
all
the
data,
as
you
can
see,
the
billing
pro
has
been
added
to
the
system.
So
when
the
user
logs
in
next
time,
she
will
see
that
that
the
data
was
synchronized
with
the
with
a
blockchain
with
fabric
and
from
now
on
this,
this
data
may
be
used
as
a
as
a
way
of
settlement
and
way
of
having
the
transaction
between
the
those
two
companies.
A
So
that
was
the
demo
and
what
we
have
learned
from
this
project,
so
we
really
wanted
to
to
really
wanted
to
introduce
blockchain
as
something
that's
really
transparent
for
for
the
end
users.
Since
this
this
system
is
going
to
be
used
by
by
a
few
few
thousand
people
around
the
world.
We
didn't
want
to
kind
of
to
introduce
something.
That's
that
has
a
very
a
complicated
UI.
A
B
B
A
This
yeah
I
will
repeat
that
question
for,
for
those
who
are
online,
so
the
question
is
about
handing
her
gdpr
within
that
system,
so
the
regulations
is
that
that
those
clients
are
already
there,
because
the
company
has
clients
that
they
are,
they
have
been
working
with
and
they
may
refer
to
this
class.
These
particular
clients
to
the
other
entities
and
the
client's
data
is
not
on
the
blockchain.
A
So
so
so
only
the
the
events
related
to
to
referrals
are
stored
for
now,
and
there
are
no
plans
to
to
handle
the
kind
of
right
to
forget
about
the
client.
We
might
kind
of
somehow
make
a
workaround
by
adding
only
the
hash
of
the
client
to
the
to
The
Ledger
and
leaving
the
clients
data
into
the
the
original
system.