Register now for CordaCon 2022, taking place in-person in London this September 27-28!
Corda 5 introduces a sandbox to the Corda infrastructure. This is a necessary addition in order to achieve multi-tenancy and high availability. This article will explore the benefits of the sandbox and what it means for Corda users. In follow-up articles we will explore this topic and its implementation more deeply.
Imagine a world where two people in completely different global and political locations could agree to something and see the results unfold simultaneously, with no slow reconciliation, no business processes involving faxes like the 1980s never ended. A world where data can actually be owned, and shared, not licensed through some central party with overarching control. Imagine your industry running on a single shared, yet secure, database. That was the founding vision of Corda. Five years on, how are we getting on and what have we learned?
Imagine a firm needs a new way for employees to book vacation. Or maybe customers want to be able to track their orders online. It’s your job to build the application. What design would you go with? Chances are you’ll build it in much the same way as everybody else does. There will be a database. There will be a business logic layer – you have a lot of choices here. And there will be a front-end – perhaps a mobile app or web-site, or a set of APIs. And then you have to worry about hosting it. Perhaps the HR department will host it in-house. Perhaps the supplier will host it in the cloud.
Corda 5 was designed from the outset to be cloud-native. Specifically, the worker architecture allows for independent scaling and resilience of the components that make up the Corda platform, all loosely coupled via a message bus. The usage of container images as the delivery mechanism for those components and Kubernetes as the runtime orchestrator should be fairly uncontroversial. This article discusses the rationale for the decision to use Helm to package the Kubernetes configuration.
We are really excited to present to you today the first preview of the new peer-to-peer communications layer of Corda 5, which is now open source. If you are not familiar with what Corda 5 aspires to deliver, we highly recommend reading the previous “Corda 5 the road ahead” blog post series from R3’s product management team. This preview is a good indication of how Corda 5 delivers on the areas of multi-tenancy, horizontal scalability and high availability.
The code for the latest version of the world’s most successful enterprise blockchain platform is now open source. Is it finished and ready to use? No. Is it close? Getting there – watch this space. Is it cool? It is very cool. I’m here to explain what the team at R3 have made available, where to find it, and why we’re doing this now.
Performance is an important aspect of any enterprise software application. Blockchain is seen as the next big thing that could change the way we transact in the near future. However, blockchains are slow. This is one of the major reasons why businesses are skeptical about using a blockchain-based system in a major way.
The world is rapidly changing as we continue to come out with new and innovative ways to do things faster, more efficiently, and more cost-effectively. However, banking is still lagging behind—hardly much has changed, and we still take days and weeks to process financial transactions. Modern banking is still inefficient and costly. Why is this and what can be done about it?
The use of distributed ledger technology (DLT) to establish digital trust is increasing rapidly across myriad sectors. R3’s Corda is the industry-standard platform for developers who build DLT applications for highly regulated markets, including banking, trade finance and capital markets. No matter where you are on your blockchain application development journey or which version of Corda you are using, R3 is here to support your build and shorten your time to deployment.
