P Sai Lakshman

Hey. Hi. My name is Sai Lakshman. My name is Sai Lakshman, and I'm working in in Marine Intelligence as a senior software engineer, and I have around 7 years of experience in the blockchain technology. And all the 7 years, I have been working with the blockchain technology with various, uh, platforms like hyperledger fabric mainly and and Polygon. And I also have a minimal experience in Quorum technology as well. And my major contributions, uh, in the 7 years of experience is, like, I got a chance to work with, uh, some of the state governments and also the Indian national government. So as we are the technical partners to some other companies in my previous experiences. And, also, I have a responsibility under, uh, my roles and responsibilities for setting up, uh, networks in hybrid Ethereum private networks or the Quorum networks, uh, across my 7 years of of journey and also part of writing the same codes or smart contracts. And, also, I had written some APIs which can communicate, uh, to the blockchain layer, underlying blockchain layer, and also give, uh, the API endpoints to the necessary development teams so that they can integrate, uh, respectively according to the use cases. And, also, I have a little experience on setting up the hyper ledger fabric network, in a distributed environment on using AWS and also in house servers for the government, uh, blockchains.

So while getting the risk conditions, as you know, that the resources are being, uh, tightly coupled with the multiple microservices. So we can handle by halting one of the microservices if it is not so urgent or if it is a blockchain transactions if you want to handle multiple things. Right? Uh, we can we can use, uh, some of those and all that stuff to handle the risk conditions.

What are the key considerations when designing microservices that interact? The key considerations, one thing, are assuming that the docker containers are never down when the microservices are communicating with the blockchain nodes, uh, and also the security while communicating all the, uh, the transport layer security what we are talking about. So all the communications, what's happening between the containers or the nodes with, uh, microservices has to be secured in a way by using certificates. Uh, that is one consideration which I would take. And the 2nd consideration, what I would be taking is, uh, make sure that the Docker is the nodes are not going down. Even if it goes down, you should have all the backup of, uh, the node data, whatever is there in that, and and store the data in the volumes, respective volumes of the docker and the containers and restart the doctors automatically. And in that time, if the if there is a communications happening from the microservice, make sure that you record the transaction. And once the service is up, you retrigger the transaction.

What would be the best strategy to handle data synchronization between the hybrid blockchain and public Ethereum network? So by understanding of the blockchains, right, so the data synchronization between a hyper ledger private blockchain and a public Ethereum network. So we can have 1 interface layer called the synchronization layer where we get the data, and if it is if my understanding about the question is correct. Right? So which we are looking for the interoperability of the questions, interoperability of the blockchains. So in that case, I would write a interface layer of the data synchronization layer between, uh, hyper blockchain and the public Ethereum network. So once because in the hyper ledger private blockchain, once we I mean, we might have the control within the network setup, whereas in the public Ethereum network, we may not have. Right? But if we are looking separately as a hyper private blockchain and the public Ethereum network, there's a 2 individual items. Right? So in that case, the data synchronization by default, it happens, uh, the number of I mean, from the application layer, we can take care of the data synchronization because once it goes to the chain code level or the smart contract level, it's not in the hands of an application developer or it's not in the hands of application directly. It's in the hands of a blockchain. So what I would suggest is the data synchronization, whichever data goes first or which data should go next, has to be, uh, clearly thought and put it in the application layer or the API layer, just the layer before the smart contract layer. The same goes with the, uh, Ethereum network as well. Thank

Integrate in Node. Js with the for the transaction validation. So for, uh, in the hyper logic fabric, uh, the transaction validation, uh, as you guys know that it will be the three way process and, like, a traditional two way process. Right? It's a three way process execute order to validate. So in the Node JS also, we can check, uh, because hybrid uses the fabric SDK. Right? For every transaction, we get an output from the chain code SDK saying that the transaction is successful with the transaction code and the transaction hash. Based on that, we can integrate the Node. Js based service with, uh, a fabric SDK, keeping the fabric SDK as a medium layer, where the fabric SDK based on the configurations can communicate to the chain code layers. Thank you.

This is a blockchain based authentication system. How would you ensure secure communications between AWS hosted microservices? Blockchain based on the system. Okay. How would you ensure secure communication between AWS hosted microservices? So the secure communication can happen in 2 ways. The blockchain network, uh, whichever network we are setting up has to be completely secured using transport layer security, using the TLS certificates, uh, with the help of certification authority or the membership service products, what, uh, in, uh, what use as a modeler thing. So we can set up and generate the certificates according to the use case and also the communication between microservices. Like, we can say that if the services are coming from this certificate or the this endpoint, then you can take it as an, uh, authenticated request or, uh, we can, uh, put it as a fake request or unauthorized request. Yeah.

Given a node this application that utilizes RabbitMQ for handling message queues. A certain message is not being processed by the worker service. Below is a simplified code snippet where the message is published. Can you point out any potential issues that could be preventing the message from being received? So Should not create channel. Okay. We are creating a channel. Okay. Channel. Yeah. Where is the task queue messages? Hello, brother. Okay. Just try not to send a queue. So and so is sent. What if send queue fails? So I think, uh, the answer would be if the sending to queue itself is failed, I think we are not logging that. So that would be one problem, what I see, uh, because that that is channel dot sent to queue of q comma dot from message, but in the same way, if we can handle that error handling in that way so that we can directly check it. We are assuming that, uh, the center queue works always faster. I mean, always correct. So it may not be the case. So that's one thing which I see.

Require Require balances of message not sent Uh, when we get the transfer amount exit's balance, it's because the, uh, the balance of that sender or uh, the one who is initiating the transaction is less than the value what it has. So, basically, uh, transfer balance because, like, uh, for example, if you assume that I have 100 rupees and I'm planning to transfer 200 rupees, which is, uh, uh, so that's when the transfer amount exceeds the balance. Right? So to to set, uh, to issue I mean, to, uh, to solve this issue, we can add a check saying that if the balances of message center, which is 100, is greater than or equal to value. Value what we are transferring. Transferring. So, basically, it has to be less than or equal to instead of a greater than or equal to. If I'm correct. Just a minute. Balance or so, message dot sender, which is whichever that is 100 rupees. The transfer value is 200. 100 is greater than or equal to 200. No. 100 is greater than or equal to 100. No. So this is failing. Yeah. That's it.

How do you scale Python based blockchain nodes to handle massive concurrent operations? Excuse me. Click on these blockchain nodes to handle massive concurrent rewrite operations. Invest blockchain nodes to handle as a concurrently. Right? I would assume horizontally or vertically is called the Python based nodes, blockchain nodes, or the blockchain microservices, and put a load balancer in front of it and try to execute the multiple operations on Python based blocks and nodes. I'm not sure about this answer. Thank you.

What method would you use to manage and operational multiple docker containers? Uh, I would use Kubernetes management or the DocuSwam if you want to offset multiple docker containers in different environments. Uh, so definitely go to answer is Kubernetes. But if the Kubernetes is not, uh, option, then the next, uh, option what we have is Dockerswam overlay networks. We can use that and we can orchestrate multiple docker containers. Uh, so in the different, uh, environments. Thank you.

Troubleshoot to receive with the denial of service that act on blockchain system developed on AWS? By setting up a firewall and taking care of all the ingress rules and the outgress rules by maintaining a distributed denial of service attack and also assuming, uh, a time out on the API layer or the, uh, API layer or the application layer. So putting up the rate limiting and time out options, we can use that and we can stop the DDoS. Thank