R3 Developers Blog

Corda 5 Developer Preview, which you can consider an alpha release, allows you to assess our new set of modular APIs and how they might impact your development velocity. In this blog post, we will deep dive into what API modularity means for developers and touch on our motivations behind them.

The new Corda 5 architecture and deployment methods are designed to deliver high availability and scalability. We placed these two crucial aspects of any high-dependency system at the center of our development mindset. After a process of careful planning and re-architecting, we are excited to share the direction we are taking for the new Corda 5 node architecture — designed to maximize reliability, availability, and scalability.

This post is a high-level summary of the how, introducing some of the big new concepts we are working on as part of the development of Corda 5 to address those takeaways and meet the objectives in the previous post.

Following CordaCon we are excited to announce R3 is working on the next major platform version — Corda 5 — and that the first public milestone — Corda 5 Developer Preview — is available!

We are pleased to announce the release of Conclave 1.2, which delivers two data persistence features, a key-derivation service to simplify cloud development, a common host, and other features that improvement the developer experience.

KDS derives the key from a master key. This master key can be a key stored in an HSM, Azure KMS, or it can be a hardcoded debug key. For the 1.2 release, there is only one master key which KDS provides, and this is hardcoded in KDS and is called the DEBUG key.

Conclave 1.2 is here. It brings with it a load of important features, an important one being the Enclave Persistent Filesystem and the Persistent Map.