Blog

By: Maciej Swierad – DevOps Engineer at R3 I, for one, welcome our new robot overlords. For they are the future, and the future is automated.George Devol Have you ever wondered how software actually makes its way into the real world? How it’s published and distributed? How it’s built and secured? Have you thought about ...

By: Miljenko Brkic, Principal Software Engineer at R3 This article is a follow-up to the Corda 5 Sandboxes blog post. It will explore in more detail how Corda 5 uses Java Security Manager to secure sandboxes. Corda 5 supports multiple virtual nodes sharing a single Corda installation and multiple CorDapps (Corda distributed applications) running within the same ...

By: Steph Paine The opportunity of moving to a new department is often an exciting thought for many, but for me it came with a level of doubt. Business Resources, the central admin and support team to the Engineering team is like going from a small, fun outgoing team to what is seen by many ...

By: Ramzi El Yafi In our previous blog post, we discussed what a notary is, and why it plays a fundamental role in securing Corda’s UTXO ledger. In this blog post, we delve into the details of the notary architecture in Corda 5, delivering a solution which allows new notarization protocols to be introduced with ...

By: Katelyn Baker, Head of Software Engineering How does one wrap up a year, summarizing 8760 hours in hopefully fewer words in a manner compelling to readers? If anyone has any bright ideas, please let me know. However, in the absence of talent, we must rely on perseverance, so let’s give it a good old ...

A journey into running Corda 5 on an Apple Silicon Mac or other ARM processor-based hosts Write Once, Run Anywhere A couple of months back, a brand new shiny ARM-based Apple Silicon Mac dropped onto my desk here at R3. Figuratively that is, first impressions were that it’s a little more “robust” than the previous ...

We are going to describe some of the lessons learned in Corda 5 CorDapp packaging since Dev Preview 1 last year. In the year since that release, we’ve tackled some interesting issues and developed solutions that will serve us well into the future. First, let’s do a recap of Corda 5 CorDapp packaging. Corda 5 ...

It will always be tempting for enterprise industry players to try to reshape the world of decentralized computing and distributed consensus in the image of their own priorities: central command and control, with everything legible and accountable from a single standpoint. I’ve seen these dynamics playing out in sales pitch after sales pitch, conference presentation after conference presentation. The tech isn’t terrible, and the incentives are understandable, but isn’t it all missing the point? Shouldn’t we stop and think about what we’re actually trying to build?

In recent years, event driven architectures backed by a fault-tolerant and highly-available message bus have become popular. They allow for systems to be designed to share loads across multiple workers, be more easily scaled to handle very large loads and in the event of failures, replay messages that were not completed by faulty processors. We at R3 wanted to harness the power of KAFKA for this very reason.

One of the key features of Corda 5 is high availability (HA). A highly available system is one which guarantees some level of uptime by being resilient to faults that may occur during operation. In order to achieve this, the system needs to provide redundancy. This article will explore what kind of high availability that Corda 5 provides in contrast to previous releases of Corda, and how this is implemented in the context of executing flows.