Hyperledger Foundation Hyperledger Global Forum 2022, 6 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Taking on Challenges of Enterprise Blockchain Infrastructures - Dr. Ravi Chamria & Ghan Vashishtha

Description

Taking on Challenges of Enterprise Blockchain Infrastructures - Dr. Ravi Chamria & Ghan Vashishtha, Zeeve

With more and more Blockchain implementations taking place every day, we must establish best practices for deployment, configuration, and infrastructure. In this session, we will discuss some of the primary challenges of setting up an enterprise-grade Blockchain network and how automation plays a vital role in managing infrastructure, and security compliances as well as saving time to market and achieving desired uptime.
If you are building an Enterprise Blockchain use case or are running one, this session will help you master SLAs, scale with ease, and set up proactive automated monitoring for your network.

Sessions Details & Slides (if available): https://sched.co/14gsR
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

Hi good evening, everyone, my name, is Ravi I'm, the co-founder CEO of zeev and I have with me Khan vashisht he's the co-founder CTO of zeev. Today we are here to talk about the challenges of managing infrastructure in the blockchain space, especially for Enterprises.

A

First, a bit about that we have come a long way. We started in blockchain space in 2016., and um at that time you know, 17 18 19. It was mostly about poc's, Pilots and now. Fortunately, in last two years we are seeing a lot of production implementation implementations. So we are obviously past that stage where nobody is talking about whether blockchain can play a role in Enterprises or not. There are quite a few use cases which are well established. There are quite a few production implementations that are going uh that are happening.

A

One of the Deloitte study uh shows that blockchain is one of the top five strategic priorities for Enterprises, but there are quite a few challenges to blockchain adoption in Enterprises and overall and one of the major challenges managing the blockchain infrastructure.

A

And if you talk about some of the core challenges, one uh the way some of the Enterprise blockchains are implemented. Most of the nodes are the infrastructure resides in one common Cloud within the organization, and that goes and it's against the tenets of decentralization.

A

So what we see is that decentralization per se is missing when we talk about a Consortium use case, the use case itself, uh you know, there's an implicit architecture in the use case that even if the use case has been started by one organization, still uh rest of the party should have an independence where they can host their own nodes, creating a decentralized or distributed structure.

A

Second cost and time uh manually deploying a hyper Ledger or any other permission. Blockchain Network takes a huge amount of time. At the same time, it takes a lot of cost and there's a lot of ongoing cost and I will talk about the cost in the next slide. There's a huge cost of setting up huge cost of owning it, and still there are no standards of benchmarks that one can leverage to uh set up a very standardized blockchain infrastructure, one of the uh core challenges, complexity of scaling.

A

So once you have set up the infrastructure how to scale up, because all the networks start small, they start with six to ten nodes, but as more and more parties join the Consortium, the number of nodes needs to scaled up as well as when the number of transactions keep on increasing.

A

Then again you require scaling up, so we in webto world have been used to uh AWS and other other means where you know we can scale up scale down on on the will same kind of infrastructure, same kind of uh features we require in the Enterprise blockchain Networks complex, to uh understand and adopt the lack of expertise, uh how to deploy a very standardized deployment architecture, how to make a decentralized etc. So that know-how, expertise, skill set, is still lacking and uh and and and sometimes you know, for small to mid-sized companies.

A

It does not make even sense to hire all those skill sets, so it's cost prohibitive at times and then, as I mentioned, you know, lack of standards for security and optimization, because uh we have seen we have few banking customers and, and one of the banking customer in Singapore mentioned that now we have finally got uh around Cloud implementing in the in the bank and talking about blockchain talking about these distributed networks is all together in another ball game, so there are no standards how to manage security.

A

If you talk about Healthcare institutions or other financial institutions, they don't know how to manage when the sum of the nodes are going to be hosted outside how to still manage all the Regulatory compliances and security within the network and as about the cost. So cost is not just about deploying a network. That's uh still I would say a one-time build-up cost but pose that there's a huge amount of monitoring analytics Etc is required.

A

Once the network has been deployed, you require a network which is of enterprise, Enterprise grade quality in terms of throughput in terms of performance in terms of security and optimization, and at the same time, you would like to scale up anytime as you want, and then you know, especially when you're working with fabric as more and more organizations join your Consortium requiring more organizations how to connect them using into your node and one of the challenged practical challenge people face is when they scale up.

A

The Consortium is that you require a heterogeneous, node, Cloud deployments, because when you, uh when one of your Consortium partner, joins your network, they may be using a different cloud or they may want to set up the network on premise or within a private Data Center. Now how to manage uh that kind of onboarding is again a very big pain point when we talk about Enterprise level consortiums.

A

So what we need is not a a plain, vanilla, automation, framework. What we require is a much more configurable highly automated and which seamlessly integrates with the underlying Cloud as well as on-premise Cloud environments. So what we require is that in-depth configuration so that once you go to a console, you are not you're pretty much. Relying on that console to do everything whether you are deploying on one Cloud environment, whether you're, clouding or deploying on multiple Cloud environments. Everything should be able to.

A

uh You would be able to manage using the same platform same console, and then you know inviting onboarding Consortium Partners on the Chain again should be very seamless, because otherwise what happens is it?

A

The owners falls on the Consortium owner that how to deploy a node for an external party, and then you know bring that node manage all the access controls Etc within the larger Network and heterogeneous Cloud deployment is, is, of course, a need because nobody wants to get login into one single cloud and at the same time, in quite a few Industries, there is a pressing need of on-premise or private data center cloud deployments.

A

Security practices uh as I mentioned, cannot be stretched enough, uh even with blockchain infrastructure. There you require server hardening. You require all kind of security and compliances to be built into the into the deployment itself.

A

So there's no point in having deploying a network using a different tool, and then you know applying all the security features on top of it and then analytics and proactive monitoring is something which is uh very much required to ensure that the health of the network is fine and you would be able to proactively monitor to see if some of the other node is out of sync or is not behaving as it's supposed to or somebody is having access controls which then they are not supposed to, and then control of cost and time to Market.

A

You know, as we know, uh in this comparative market, everybody needs that. So that is where uh zeev comes in. We started in blockchain space in 2016 and initial three to four years. We did a lot of Consulting worked with quite a few Enterprises in financial services, supply chain, manufacturing, retail, Telecom, energy and utilities.

A

Quite a few Industries, and during that time you know, one of the job was to build poc's Pilots, deploy the networks, run the pilots and and we found uh infrastructure management as one of the pressing needs, because the expectation in the Enterprise is the same whether we move from web 2 to web 3. The expectations are of same high throughput security, scalability performance Etc. So we wanted so we built zeev as an internal tool initially for our own customers, and then we realized. This is a wider problem and started seeing a lot of traction.

A

So zeev is a low code, SAS platform that allows you to deploy blockchain networks on the Fly. We support multiple clouds, all the top major clouds, as well as on-premise deployments. We support multiple blockchain protocols, including all the permissions, quite a few uh products out of The Suite of hyperledger R3 Coda flurry Dragon chain and we're adding more and more protocols in the permission side, and not just that. We are also supporting 20 plus public protocols and some of the hybrid deployments like flurry with fabric or fabric, with ethereum different kind of hybrid deployments.

A

We are supporting on the Fly and we have very sophisticated, proactive monitoring and analytics that allows you to uh not just do a cloud resource monitoring, but also the monitoring of the blockchain resources and then, in addition to that, the way AWS did for cloud on the same way we have. We have built quite a few web services that can be directly uh integrated within your application, so, for example, decentralized storage. So if you want to connect, let's say you are storing any use case where you need to store the digital assets.

A

The underlying digital assets on ipf is kind of storage. You don't need to spin up your own nodes. We have a ready service which is backed by hundreds of ipfs nodes running. We have both public as well as private candle deployment for ipfs. You simply use that service plug it into your application, and and that's it. We have decentralized governance. We have iot as a service and quite a few services that you can plug in into your application to build the application much faster.

A

We have 15 000, plus uh developers and web free startups, using the platform 25 plus Enterprises, who are running large consortiums using our platform.

A

So this is a larger snapshot of the summer. Features that we have today and then you know, Ghan will talk about some of the roadmap items that we are going to bring in specifically for hyperledger fabric. So on the network and security side we have multiple Cloud provisioning, so on the same network you can have different clouds deployed different nodes deployed on different Cloud environments and those Cloud environments may be within your organization. Maybe outside the organization there's a one-click node deployment. It's highly configurable. You can see all the configurations.

A

So if we talk about fabric which is much more complex in terms of configurations, you get 100 of the configurations out of the console. You will never need to go back into your Cloud environment to make additional changes or configurations.

B

So I'll pick up from here and I'll talk about you know what is underneath. You know the engine which Powers is even you know what gets you all those benefits which we just talked about, so this stack? You know the focus of the stack is decentralization like you know, we've been speaking from the very beginning that the Enterprise ecosystem, of course it's limited. It's focused, but then you know whatever expansion it requires. It has to be decentralized in the sense that you know it's well distributed under different ownerships and yet monitored.

B

So we ensured that you know this stack. You know which offers you all these asset, tokenization decentralized, iot speak. One line about decentralized iot is that you know when we do supply chain use cases. We say that you know the data is coming out of Amazon cloud iot or Google Azure iot Cloud, which is taking taken up from you know some some truck shipment somewhere for the freshness of the goods. But then you know you're centralizing it if you're pushing it into the iot cloud and then consuming back into the smart contracts or chain codes.

B

For you know, slas and other other kind of you know chain code base functionality, so we ensure that you can directly push the data into the nodes.

B

Through these, you know specific chain codes which you can deploy and consume, and then you know the interested execution is is a must for this stack to have uh then distributed kyc because you're onboarding, multiple organizations, and when you do that, you need a you know wider reach, how your platform is monitoring uh the nodes which you own, but at the same time the other party is able to monitor the notes they own and as in whole.

B

They also see that there are some other organizations which in place they don't control it completely, but they at least see they're there, their health status and all because this network, as one is, is what is running the use case. So everybody is playing their role, but as one they are, you know they are to be monitored as a as a one one as a one network, then you know the products which we offer under zeev is the permission protocols. There are multiple V support, then the you know data apis.

B

So if you're deploying a supply chain use case on apologic fabric and you would require certain analytics Out of You Know The Ledger, which is not given by the platform uh explicitly because platform you know, does analytics on resources clusters, uh you know the status, the blocks, the latencies of different parameters, then you know these apis would give you enhanced capability so that you can pull the data out of The Ledger about you know those specific use case parameters, the supply chain, the traceability parameters and create further analytics on top of it, which could be application specific.

B

You know use case specific, which might be required on your own front-end applications, mobile application or the web application. Then you got you know. Zdfs review already spoke about it. It's it's give you the capability, if you're doing a supply chain use case, and you need to store good Street notifications, uh you need to store POS and invoices in digital form, because they're tokenized on the Chain. That's what your use case does. If it's a trade, Finance use case you're doing a lot of you know, uh letter of credit clearance and all parties are there.

B

You want to store those documents in a way that that they are always accessible, easily accessible and yet distributed. So you can consume these these apis right away. Then this you know, CI cdps at the bottom uh I'll talk about it in a bit when I'll show you the screenshots, but this is uh you know very critical to what happens after you have set up a network, because your Dev team would run into you and will ask you that how do I start get? You know injecting my chain codes into it?

B

How would I upgrade my chain codes once deployed and what, if the ownership is already distributed, you as one organization might be running some orders and peers into your own. You know Cloud, but then other stakeholders would be running it in their own. So how you know, there's the seamless upgrade or instantiation of chain codes consistently happen. While you still benefit from the Legacy tools you, your team is already using, like you know, get Jenkins, Nexa and others.

B

So we have a very specific CLI design, for you know the the purpose uh to solve the purpose of you know the challenges which you have in blockchain specific CI CD. It's like you know, compatible with the Legacy and then yet give you the coverage on. What do you need for a blockchain implementation?

B

So these are, you know uh we are learning every day from these customers of ours and they are like. You know: well, spread it's not just hyperledger fabric over here. It's like you, know, R3 codites, hyperledger base over here and a lot many other protocols and and so many use cases, trade, Finance, fintech supply chain. We got. You know some metaverse use cases as well in here and we're learning from every day and we're improving our platform to serve better and more up in in more optimized fashion as possible.

B

So it's it's a quick case study. You know it's a trade Finance ecosystem uh you're powering. It's live already, it's a singapore-based ecosystem and what I would point at is that you know we have saved them 45 on their cost on running the Consortium. It's a Consortium, multi-party Consortium and we saved them 80 time when they wanted to go to the market. It was just uh you know, it was just a 80 reduction in time. We help them achieve and scale so every next onboarding they had to do in their trade.

B

Finance Consortium, be it another bank, another exporter importer. It was very easy, very seamless without exposing you know the cryptographic artifacts and things explicitly over emails and this and that way, so it happened very seamlessly so of course securely and we help them reduce a lot of time. There are other benefits, but I think I'll focus on these two. uh You know for the session's sake now, I'll, you know run into how how all this happens.

B

What do you get? What do you see when you sign up on zeeve? It's completely DIY. Of course there are certain things which are very specific. We are experimenting, and we are you know, upgrading continuously, so our team comes in and helps you there, but these are diy things which you get on the platform you can create a network and as detailed as that, you can have you know peers getting configured with. You know the Liberty, because DB configurations available to you, you can have persistent storages available to you for these services.

B

You you can, you know, download the blockchain data, the artifacts to extend the network manually. So is not a lock-in. It's not like you commands. If you get stuck. No, you still can scale your network manually. If you want to so it's not a dependency which you're we're passing on to you. It's the flexibility which we are allowing you to have, but then you can still scale manually. If you require, then you know the the visual topology is out there and it's pretty Dynamic. You see whatever is happening in your network.

B

If it is a scaling, more organization is being added. You see it there, you may or may not control them. For example, you can restart your own nodes reset them. You can change things there, but delete them and maybe add more, but you cannot do it with the other organizations, but you would see them still, and this would tell you you know what notes are sinking thinking or not, and these connectivities these are real.

B

So if some node gets out of the network, you would know you would see it as well, and the platform will start. You know giving you a lot of notifications. If you would want them right and then you know this fits in even to this kind of you know a complex implementation.

B

So, regardless of how many you know, Services you're running how many organizations you're having how bigger you're getting, of course it's better for your business, but the platform ensures that you know it remains better for your business.

B

Then you got you know all sort of monitoring analytics punched in right there. So your devops team, your engineering team, they don't have to you- know 24 7, you know have sleepless nights worrying about what is happening. They can, you know simply get to this dashboard anytime. They get a notification and they need to ensure that everything is fine or every morning they can sip coffee and just look at this dashboard and feel safe and don't worry about their bosses ringing them and telling them. No. The network is already done. What I have?

B

What have you been doing, and this gives you analytics not just at the cluster level, I mean kubernetes cluster level or the resource level, which is running in some Cloud Azure, AWS or Google, but it gives you the analytics on the Node level as well. For example, the block count the latency of transactions and those kind of details, and this is the CLI which I was talking about. So we did support.

B

uh You know: node.js golang, Biz, smart contracts, uploading into the panel and all, but then we created this CLI specifically because you know we've been developed ourselves and we know what developers love they need the sound of the keyboard into their ears. All the time and this CLI ensures that, with this CLI they can, you know, connect their old Legacy tool chains like GitHub, Jenkins, Nexa and all and then punch all the chain codes into the network consistently.

B

Every time they upgrade release a bug fix or a patch, and this propagates across the network very seamlessly, and this is what is coming at Zee next, so a plethora of features on appellation fabric, including uh the dmz-based security architecture, which is very Enterprise focused and these protocols, so a checkbox and you'll have Cactus adapters available to your fabric deployments when you will do it after this release.

B

uh Thank you, for you know, listening to all this, this is Eve and we are present uh across U.S, Dubai India and in Europe as well. Now, so you can connect us and we'll help you out. You know with all the challenges you have with your fabric, Networks I think this is it for the day.

B

One last thing: you know: we have a booth here, we are having. You know three thousand dollar credits free for you to start your fabric networks. You can come there, we'll give you those credits, and you can see the demonstration uh Explore More with us.