<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mike Ward on Medium]]></title>
        <description><![CDATA[Stories by Mike Ward on Medium]]></description>
        <link>https://medium.com/@mward?source=rss-622f1f6dbf71------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*U78Y192ep0ZBHZxE.jpg</url>
            <title>Stories by Mike Ward on Medium</title>
            <link>https://medium.com/@mward?source=rss-622f1f6dbf71------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:19:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mward/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Corda 4.6 Beta — our summer release]]></title>
            <link>https://medium.com/corda/corda-4-6-beta-our-summer-release-f33159efe4b3?source=rss-622f1f6dbf71------2</link>
            <guid isPermaLink="false">https://medium.com/p/f33159efe4b3</guid>
            <dc:creator><![CDATA[Mike Ward]]></dc:creator>
            <pubDate>Tue, 25 Aug 2020 15:01:05 GMT</pubDate>
            <atom:updated>2020-08-25T15:01:05.496Z</atom:updated>
            <content:encoded><![CDATA[<h3>Corda 4.6 Beta — our summer release</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJVcNiMjGBsrZEW3hC9qxw.jpeg" /></figure><p>The engineering team at R3 have been hard at work (in their homes) building a bundle of things in our summer release to improve your quality of Corda life. While they are putting the finished touches on this Q3 release, you can get your hands on it with the beta. Please contact our support team for access (support@r3.com). This quarter our focus has been in three areas:</p><ul><li>Flow management</li><li>Membership &amp; network improvements</li><li>Improvements for developers</li></ul><p><strong>Flow Management</strong></p><p>Corda, uniquely among blockchains, has the ability to orchestrate workflows between companies. We recognize that managing these workflows can be difficult and puts an undue burden on developers to solve for this in their code. As such we have put more emphasis on the management of workflows that are in process. Our flow management improvements include:</p><ul><li>The ability to query, filter and inspect flow checkpoints via shell/RPC. The growth of long-lived production deployments had introduced the need for production-grade tools to manage running flows. With this feature we are giving administrators the ability to remotely retrieve rich information on a running flow, such as start time, the step reached, and the parameters passed to invoke it of in-process flows and manage their execution. This builds on earlier ‘flow hospital’ work and begins work on looking at flow management, not just fixing of flows with known errors. Users can query flows and obtain information from a number of filtering criteria such as progress step or CorDapp.</li><li>Retry flows without restarting the node. Node operators can now retry hospitalised flows via RPC, rather than having to restart the node to trigger retries. In addition, node operators can mark problematic flows as “do not restart”, preventing them from being retried automatically when the node is restarted.</li><li>Allows the use of a unique ID to prevent duplicate flow starts. The RPC Client has been updated to allow clients to deduplicate flow invocations, to ensure a given flow is not executed on the ledger twice. This also increases resiliency through allowing a client to take appropriate action should a flow fail to start.</li></ul><p><strong>Membership and network improvements</strong></p><p>Our production use cases are revealing a need to help the CorDapp operators better manage their network of participants. Whether in a private network or a larger zone, such as the Corda Network, operators need to identify their users and manage them leveraging meta-data they establish about those participants. We are releasing initial capabilities in this area.</p><ul><li>Support for membership representation. BNOs are a term we use for business networks who deploy the CorDapps and manage the user base for them. To help this key entity better manage their users, we are introducing a new primitive on Corda that allows developers represent membership attestations, membership lists and ultimately Business Network abstractions. This release introduces tooling to manage the lifecycle of a membership attestation and showcases best practices to manage memberships, drive entitlements and set granular privacy and permissions within your business network.</li><li>Increased support for larger networks. In response to the increase of observed network sizes (measured in terms of participants) we have increased the distribution performance of the network map list to ensure a faster turnaround even when the network passes the several thousands nodes.</li><li>Removal of need for flag days when adding notaries. It is no longer necessary to shut down and restart a node after accepting the updated network parameters whenever a new Notary is added to a network’s whitelist, thus triggering a flag day.</li></ul><p><strong>Developer experience</strong></p><p>We are focused on improving the overall developer experience to ensure Corda maintains it status as an easy to use platform for developers. In this release we have a number of improvements that will help developers build more resilient applications.</p><ul><li>Detection of un-restorable checkpoints. During development flows are now automatically serialised then deserialised whenever they reach a checkpoint. This enables automatic detection of flow code that creates checkpoints that cannot be deserialised. This feature can, and should, be disabled in the node configuration when in production.</li><li>Register custom serializers. Custom serialisers can now be used when serialising types as part of a flow framework checkpoint. Most classes will not need a custom serialiser. This exists for classes that throw exceptions during checkpoint serialisation. Implement the new CheckpointCustomSerializer interface to create a custom checkpoint serialiser.</li></ul><p><strong>More in the box</strong></p><p>In addition to the major areas of our focus we have included a number of improvements you can benefit from. These include:</p><ul><li>Monitoring of ledger statistics. We are releasing a new utility CorDapp that captures statistics related to the Corda ledger, allowing for efficient access via flows and JMX metrics.</li><li>The metrics exposed by LedgerGraph include: size of transaction chain, attachment count and whether all the outputs of a transaction chain have been consumed. This utility will help operators anticipate when transaction chains are too long and should be reissued among other possible uses.</li><li>In-place upgrades. We want to better assist customers moving from Corda open source to our Enterprise distribution. Our first step toward this is ensuring the schemas for open source and Enterprise are in sync allowing for a so called in place upgrade that does not require a larger migration of an instance.</li><li>Metering improvements. To support operators who wish to retrieve Corda Enterprise metering data via the flow framework from a central collector node, we are releasing a standalone client for the metering collection CorDapp. The client can be used out of the box to retrieve metering data in JSON format from one or more nodes in a business network. No direct access to node shells is needed. If any node fails to respond, the client facilitates subsequent attempts to collect missing data.</li><li>Store TLS keys in HSM. TLS keys are used in Enterprise by the firewall to ensure secure connections to other Corda servers. While we have had the ability for this storage to date it has been limited. From this release we’ll now enable storage of TLS keys in an HSM for any configuration.</li></ul><p>While we are still hard at work finishing the third quarter release, we want to hear what you need in the future as our roadmap and priorities are based on our users input. If you have any input as to what you would like to see please email us at <a href="/service/mailto:productfeedback@r3.com">productfeedback@r3.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f33159efe4b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/corda-4-6-beta-our-summer-release-f33159efe4b3">Corda 4.6 Beta — our summer release</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corda 4.5 beta release]]></title>
            <link>https://medium.com/corda/corda-4-5-beta-release-a31d5f619dce?source=rss-622f1f6dbf71------2</link>
            <guid isPermaLink="false">https://medium.com/p/a31d5f619dce</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Mike Ward]]></dc:creator>
            <pubDate>Thu, 28 May 2020 11:53:11 GMT</pubDate>
            <atom:updated>2020-06-03T14:11:58.214Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve been hard at work on our second quarter release within the engineering and product teams at <a href="http://www.r3.com/">R3</a>. This is our second release in our new quarterly release cadence. This quarter we are delivering improvements across our <a href="http://www.corda.net/">Corda</a>, <a href="https://www.r3.com/corda-platform/">Corda Enterprise</a> and <a href="https://www.r3.com/download-corda-enterprise-network-manager/">Corda Enterprise Network Manager</a> products in the areas of performance, operational and deployment improvements. Among the many features, we are introducing large latency improvements in Corda Enterprise and the ability to recover a ledger from your network peers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a9hATuP8P5Y3ymutUdrVOQ.jpeg" /></figure><h3>Performance</h3><p>The biggest areas of improvements we’ve focused on in the second quarter are performance improvements for Corda Enterprise.</p><p>Performance has been a large focus for the blockchain industry for sometime. However, arguably much of it was academic as there were very few implementations where performance was truly the constraining characteristic. We have done work in earlier releases focused on performance. That focus was on throughput, often referred to as transactions per second (TPS). Throughput is a measurement of how many transactions a node can process concurrently. We had some great achievements in throughput performance in <a href="https://medium.com/corda/transactions-per-second-tps-de3fb55d60e3">earlier</a> releases.</p><p>As our customers production systems grow in volume they are starting to push the limits on performance. Our improvements in throughput helped greatly and remain robust. However, we are starting to see that larger networks pose a different performance challenge — latency.</p><p>Latency is a different way to look at performance. Latency is a measurement of how long a transaction takes from the time it starts to finish, among a group of participants. One of the key challenges is the latency in sending and receiving messages between participants in building, finalizing and distributing a transaction. This is our area of focus in the second quarter release. We think you’ll be excited to see the dramatic improvements we’ve made here. All of these improvements come without any breaking changes to compatibility. Our latency improvements include:</p><ul><li>Reduction of latency in back-chain resolution.</li><li>Parallelization of signature requests and collection.</li><li>Using a single checkpoint (instead of multiple ones) when using a flow to contact multiple parties.</li><li>Message compression sending less data over the wire and persisting a more compact format.</li></ul><h3>Operations</h3><p>We are happy to announce new ledger recovery capabilities. As a point-to-point system Corda maintains privacy by ensuring only parties to a transaction are able to see the transaction and record it to their vault. However, one of the benefits of a blockchain system has been perceived as the ability to recover your ledger from a peer in the event of a failure. Without a global state ledger Corda has lacked this ability. In this release we are delivering a similar capability. Corda Enterprise 4.5 brings:</p><ul><li>Tooling to allow nodes to diagnose any inconsistency or missing data in their ledger by comparing their ledger with the one of their peers.</li><li>The ability to recover data from your network peers by requesting transactions from them via the flow framework.</li><li>The ability to recover from network peers via an export / import process to lessen the impact on network traffic.</li></ul><p>Additionally, we have a number of improvements for the operator of the node or the business network.</p><ul><li>Auditing. Nodes now maintain an audit trail of all users who tried to launch an RPC operation. This has been added for compliance and security reasons.</li><li>Flow management. We continue to improve our flow management capabilities. If a node user terminates a flow, counter-parties are automatically notified and any soft-locked states in the vault are automatically released.</li><li>Metering. Tooling to collect metering from network participants. Specifically for Corda Enterprise, the application publisher is able to request metering information from nodes where their CorDapp is deployed. This allows them to have an aggregated view of Corda Enterprise usage, related to their solution. This supports our flexible pricing model and is achieved with full privacy and security considerations.</li><li>Notary auditing. We’re evolving the notary to facilitate easier operations by network operators including auditing capabilities. The notary operator can better audit the log of spent states and requests from clients.</li></ul><h3>Deployment &amp; Management</h3><p>Deployment of a solution into an enterprise environment can be challenging with the highly heterogeneous environments operated by our larger customers. With a few years of experience in deployments in these environments, we have now selected a single set of deployment tooling that we believe best supports the needs of our customers and sets us up for future growth.</p><p>We are embracing a container strategy, specifically with Docker images. Containers are largely the default means by which organizations expect software to be delivered into their data centers. Docker has become the de-facto standard for containers. We are delivering all of our products in Docker containers.</p><p>We will be allowing customers to automate the process of deployment by distributing our containers with Docker Hub. This allows customers to use standard tooling in their environments to obtain and manage Corda Enterprise and Corda Enterprise Network Manager.</p><p>Additionally, we continue to lay the groundwork for a better cloud experience. This release brings:</p><ul><li>AWS HSM support for signing, confidential identity and TLS keys. Note the TLS key support requires use of the Corda Firewall component in configuration.</li><li>Additionally, the notary has the ability to store keys in AWS as the signing occurs in the HSM environment.</li></ul><h3>Corda Enterprise Network Manager</h3><p>Corda Enterprise Network Manager continues to mature as a critical component of the network. In this release we have significant improvements including:</p><ul><li>Availability as a cloud template (available at GA).</li><li>High availability for the CRL endpoint.</li><li>Improved DB permissions.</li></ul><p>We have a large number of smaller, additional improvements. The smaller items will be available in the upcoming release notes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a31d5f619dce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/corda-4-5-beta-release-a31d5f619dce">Corda 4.5 beta release</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[R3’s 2020 Developer Relations Plan]]></title>
            <link>https://medium.com/corda/r3s-2020-developer-relations-plan-f22ca87837e1?source=rss-622f1f6dbf71------2</link>
            <guid isPermaLink="false">https://medium.com/p/f22ca87837e1</guid>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Mike Ward]]></dc:creator>
            <pubDate>Thu, 21 May 2020 17:09:20 GMT</pubDate>
            <atom:updated>2020-05-21T17:48:28.006Z</atom:updated>
            <content:encoded><![CDATA[<p>As a member of the open source community, R3 are familiar with being transparent. But we realize that we can embrace openness further, by openly sharing our developer relations plans. My hope is this helps shapes the best plan to serve our audience — developers. I welcome feedback or questions on the plan to better serve you. I’ve left this as close to our original internal communication as possible, which starts below. Send any feedback or questions to devrel at r3.com or me (mike.ward at r3.com).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgA5cUUeYW37jLZtsWTVGg.jpeg" /></figure><p>This plan is a revised version of the plan communicated internally at the end of 2019. The requirement for many of us to work from home has caused a dramatic shift in how we go about our job. Considering we are unsure how long we will be required to avoid large gatherings of people at public events, our 2020 plan is now 100% online. This revised plan reflects our new reality.</p><p>Embracing might be a better term than reflecting, however. This presents an opportunity for the developer relations team. In the original 2019 and 2020 plans I had called out the need to move more of our activity online to reach a much larger audience. We now have our full focus in an area that helps us reach more developers, and gives us strong metrics to know how well we are succeeding.</p><p>Metrics are key to us — if we can’t measure it, we don’t do it. We also are structuring our activities to think of them in a progression of our relationship with developers. I use the terminology from <a href="https://en.wikipedia.org/wiki/AIDA_(marketing)">AIDA</a>, which is a classic marketing framework that helps us understand where we are in our relationship with the broader community.</p><h4>Developer Relations Objective</h4><p>A reminder on why we exist as a team. The developer relations teams purpose is <strong>driving adoption of Corda by developers</strong>.</p><ul><li>We represent a single audience — <strong>developers</strong>. We target this audience because they represent a critical audience for the adoption of Corda.</li><li>Developers are our <strong>customers</strong>. Our focus is on making them successful in solving complex problems, not selling them products.</li><li>First, we must make developers <strong>aware</strong> of our solution and how it solves problems they may have.</li><li>Next, we lead them to a deeper <strong>interest</strong> through content that will make them productive.</li><li>We are part of the marketing effort and must ensure developers are led from awareness to action in a well formed <strong>nurturing</strong> <strong>program</strong>.</li><li>We recognize we are part of the overall <strong>sales</strong> process and ensure developers in key accounts are shepherded toward teams that can help them further.</li></ul><h3>2020 Activities</h3><p>The remainder of this plan details the activities we will drive in 2020, and how we will structure ourselves to achieve this. We have divided our team into two main areas: evangelism and experience. Our program is built around the AIDA stages.</p><ul><li><strong>Awareness</strong>. The awareness activities are the domain of our evangelists. The responsibility of the evangelist teams is to make a broader target developer community aware of Corda, and how it easily solves difficult problem for them. The end result of these activities should be bringing developers back to the website.</li><li><strong>Interest</strong>. Interest occurs after developers are aware of Corda, and is how we take them on the nurturing journey. This nurture path takes developers who have landed on website and moves them to become deeply engaged, and productive, developers.</li><li><strong>Experience</strong>. Experience captures the tools and process that a developer encounters working with Corda. This includes the experience from landing on <a href="http://corda.net/">corda.net</a>, to training and development of a CorDapp (including IDEs, SDKs and other elements that impact the developer).</li></ul><h4>Awareness</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uw52A_GTSnAjg4cCpfsDtA.jpeg" /></figure><p>Much of our effort in 2019 was <em>satisfying</em> demand for Corda knowledge rather than <em>creating</em> it. Developers are the top of the funnel for R3s go-to-market strategy. Building awareness is difficult, but without it we fail.</p><p>Reaching developers who are not yet aware of Corda, and how it benefits them, will require us to drive activities in areas that are not owned by R3. Our focus will be on engaging developers in other communities. Our specific activities are listed in Airtable or are tracked in the metrics workbook. Many of our original activities for awareness are designed for in-person events. Considering the current environment this is our most challenging area but also the largest opportunity to drive impact. Our activities include:</p><ul><li><a href="https://youtube.com/cordablockchain"><strong>YouTube</strong></a>. Youtube is one of the most widely used channels for developers to learn about new technologies. We can do demos, tutorials etc but we will also strive to learn from more social channels like Microsoft’s <a href="https://channel9.msdn.com/">Channel9</a> in creating a social atmosphere. We will aim to be a part of other technology channels to get new visibility.</li><li><a href="https://twitter.com/cordablockchain"><strong>Twitter</strong></a>. We’ll be active in the <strong>Corda Twitter</strong> account to build out a larger audience of followers by following others and joining in on their conversations. Don’t just tweet marketing copy, say something meaningful and be a part of conversations.</li><li><strong>Online communitie</strong>s. Online communities are the primary way developers interact and discover new technologies. We’ll focus our effort in being a part of the online communities to drive awareness. We will identify and target online communities that are key to Corda adoption. For example, we should be active in Java groups on <a href="https://gitter.im/">Gitter</a>, or other areas where they convene.</li><li><strong>Guest blogging</strong>. We’ll continue to have regular blog postings on our <a href="https://medium.com/corda">Medium blog</a> from our community, but we should focus on blogging in other communities to draw in new developers. We’ll develop a list of blogs we can partner with.</li><li><strong>Hackathons</strong>. We will participate in hackathons as a way to drive more awareness around Corda. We will not run our own events as this will not help us reach a new audience. Rather, we will participate in existing hackathons by sponsoring the event to ensure Corda is a platform that can be selected by developers. We will then support teams who select Corda with direct help during the event.</li></ul><h4>Interest</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N5mafEWtpFXG0kEm1tn5SQ.jpeg" /></figure><p>Interest takes place after a developer is aware of Corda, and has some idea of how they will benefit from using it. Included in this category are the efforts we make with developers to make them successful while learning.</p><ul><li><a href="https://stackoverflow.com/questions/tagged/corda"><strong>Stack Overflow</strong></a>. We’ll continue to maintain regular support for the community on these key channels. Stack Overflow is the #1 most visited website by developers. While it is not a community website, developers go here with issues allowing us to form a public Q&amp;A that is readily discovered in Google searches. It is important to be quick to respond to give a feeling developers are supported, and a part of a community.</li><li><a href="http://slack.corda.net/"><strong>Slack</strong></a>. Slack is our main tool for conversational engagement with our community. We will monitor the general channel as well as the developer relations channel on a daily basis. However, for anything that a broader community can benefit from post the answer on SO and put a link back in Slack. Slack content is lost to the scroll. 90%+ of the Slack conversations are private. Let’s get people to converse in the open and foster shared knowledge.</li><li><a href="https://www.corda.net/blockchain-bootcamp/"><strong>Boot Camps</strong></a>. While we are suspending roadshows, we have successfully converted our boot camps to be delivered online in a shorter format. We’ll continue to deliver these on a regular basis in each region while we see sufficient demand. We’ll run one per month in Asia, India, EMEA and the US on YouTube live. We’ll promote these as local boot camps to prevent overly large sessions to keep the quality up.</li><li><strong>Topical webinars</strong>. We’ll add further webinars for specific topics targeting both more advanced Corda developers (e.g. Tokens) and more general appeal sessions (e.g. Corda for Java developers and Corda Blockchain Introduction for Developers).</li><li><strong>Office hours</strong>. Specific times when developers can ask questions of somebody live. We’ve experimented with us over the years and believe the most effective way to run it is on Slack. Let’s give times where we can help with challenging questions.</li></ul><h3>Experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DV3gvWA3se3wZAjiTwnWZg.jpeg" /></figure><p>Corda is a straight razor. There are too many ways to hurt yourself, and it requires too much skill to learn how to use it effectively. We need to move to the era of the safety razor.</p><p>The developer experience team<strong> </strong>has this mission: <strong>make the Corda developer experience best of class</strong>. While the other teams are responsible for making developers aware of Corda, this team is responsible for creating a glide path for their success. The evangelist will land the developers on <a href="http://corda.net/">Corda.net</a> and this team will take them on the rest of the journey.</p><p>The team’s remit is to take developers from aware to interest with Corda, purely online. This includes:</p><ul><li><strong>Strategy and Requirements.</strong> A document located in the product strategy that details the current state and desired state for a developer. It will detail a roadmap for functionality related to developers. It will detail the requirements and eventual features that will go through our standard delivery process.</li><li><strong>Corda.net. </strong>The most important part of a developers experience with Corda is the landing page, and journey through, <a href="http://corda.net/">corda.net</a>. We’ll partner with marketing to refine this page, targeting a lower drop-off rate as well as conversion to the next stage.</li><li><a href="http://training.corda.net/"><strong>Training</strong></a><strong> &amp; Certification</strong>. Our goal with training is to get as many developers as possible skilled up. As such, we are investing in world class online training. Additionally, we are building a formal certification program. The goal of certification is to ensure our customers are able to trust that the developer they hire with our certification is truly skilled and productive. Our new training went live today!</li><li><strong>Online tooling</strong>. We will ensure the developers experience is as productive as possible through an online developer environment. Our remit as developers is limited to the Visual Studio Code hosted IDE environment which is critical to our success in online activities.</li><li><a href="https://github.com/corda/samples"><strong>Samples</strong></a><strong> and Tutorials.</strong> DevEx own the samples currently in the Corda repository, and future samples. These samples and tutorials will be kept up-to-date. We will create new samples and tutorials as new developer oriented features are released each quarter. We will revise these samples to be sure they are simple and are structured against a standard learning path.</li></ul><h3>Metrics</h3><p><strong>If we can’t measure it, we don’t do it</strong>. Our execution metrics are tracked in our internal spreadsheet, but our main metric is the rich set of data provided by Google Analytics for <a href="http://corda.net/">Corda.net</a> (including training and docs).</p><p><strong>Awareness</strong></p><ul><li><a href="http://corda.net/">Corda.net</a> visitors. <strong>New visitors</strong> as the single metric that is a proxy of awareness growth.</li><li>Value Proposition. Website <strong>bounce rate</strong> as a measure of how well our message resonates with developers.</li><li>Local city reports on <strong>key markets</strong> as discussed below.</li></ul><p><strong>Interest</strong></p><ul><li>Corda.net <strong>return visitors</strong>. How engaged are developers. Note we consider docs.corda.net as a part of our metric and anticipate developers return there, not the general website.</li><li><strong>Stack Overflow questions</strong>. Execution metric to show how quickly we respond to issues. Interest metric on how we see growth in questions indicating growth is use.</li><li>Youtube views. <strong>YouTube channel subscribers + views</strong>. This also gives us a chance to <strong>benchmark</strong> against related, or competitive, products using public metrics.</li><li>Trained &amp; certified developers. Count of individuals who have <strong>completed our online training </strong>showing deep engagement and interest. Certified developers should not be a metric we try to push as that drives the wrong behavior. R3’s belief in the ability of the developers who have this certification is our goal.</li><li>Activated developers. Count of <strong>Maven Central downloads</strong> as an indication of a developer having commenced work with Corda by compiling a CorDapp.</li></ul><h3>Target audience</h3><p>The developer universe is large (25m+) and we need to stay focused on those that will make the most impact for R3. This is a narrower audience for us to ensure we are focused on reaching the right developers with our limited resources.</p><ul><li><strong>Professional developers</strong>. Where possible, we will target developers who work in ISVs and SIs.</li></ul><p>This means that specific audiences are out of scope for focused activities beyond broad awareness. Of course, we will support all developers but we’ll not target these audiences:</p><ul><li>Startups — we’ve got a whole team for this now who we will partner with to support startups.</li><li>Students or hobbyist developers — are out of scope as we have limited time to help grow the next generation when we haven’t secured the current one.</li><li>Desktop or mobile developers — we target developers that work in the server part of the application stack layer as is natural for Corda.</li></ul><h3>Team structure</h3><p>DevRel is split into three teams. We are currently a team of 8, with open headcount.</p><ol><li>Evangelists — America’s and Asia</li><li>Evangelists — EMEA</li><li>Developer Experience (DevEx)</li></ol><p>The America’s team is based out of San Francisco, closer to Asia time zones. As discussed below, ‘Silicon Valley’ is one of the most important areas for us to build awareness. We also have a presence in Hong Kong, targeting China reporting into this location.</p><p>The EMEA team is based in London near the engineering team and cover Europe, the Middle East and Africa. India is one of our most important regions and we have a Mumbai based team there.</p><p>The DevEx team is London based team to be near the development team. This team is responsible for a developers experience after landing on <a href="http://corda.net/">Corda.net</a> discussed below.</p><h3>Geographical focus</h3><p>Globally developers are highly concentrated in three key locations: the US, India and China. The EU comes next with Germany and the UK. The recent Github <a href="https://octoverse.github.com/">report</a> provides more evidence of this.</p><p>We need to win these locations before we spread ourselves thinly in other, far less impactful, locations. We’ll make very few exceptions for activity outside limited key locations.</p><ul><li>India (Bangalore, Hyderabad and Pune)</li><li>USA (New York and SF Bay Area)</li><li>China (Hong Kong, Shanghai and Beijing)</li><li>Europe (London, Berlin, Frankfurt, Paris)</li></ul><p>2020 is set to be an amazing year for us as a team to capture the awareness and interest of developers for Corda. We have an amazing solution to help them build distributed applications that connect organizations. I’m looking forward to working with you and our community. See you online.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f22ca87837e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/r3s-2020-developer-relations-plan-f22ca87837e1">R3’s 2020 Developer Relations Plan</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corda Enterprise 4.3 is now GA]]></title>
            <link>https://medium.com/corda/corda-enterprise-4-3-is-now-ga-e3e760a8e0cc?source=rss-622f1f6dbf71------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3e760a8e0cc</guid>
            <category><![CDATA[corda]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Mike Ward]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 12:38:58 GMT</pubDate>
            <atom:updated>2019-12-18T11:54:41.436Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2-r7lMPWKhta84H9bLmJ5w.jpeg" /><figcaption>Enterprise, now with accounts. Credit: Adobe Stock</figcaption></figure><p>We are happy to announce the release of <a href="https://www.r3.com/videos/corda-enterprise-4-3-explainer/">Corda Enterprise 4.3</a>. This release builds on the capabilities introduced in Corda 4.3 and brings new functionality that meets the specific demands of enterprise deployments.</p><p>Corda Enterprise 4.3 continues our focus on the themes important to our customers and for putting Corda Enterprise into production: operational capabilities, security and resilience. We have also introduced a new capability that underpins a flexible pricing model for Corda Enterprise. We will discuss the new pricing model in a separate blog posting.</p><p><strong>Building on open source</strong></p><p>Corda Enterprise builds on the open source distribution of Corda. This maintains our promise that a network can operate with a mix of Corda Enterprise and Corda nodes, and contracts can be deployed to either distribution without modification. Corda Enterprise users benefit from the enterprise grade capabilities of the latest version, as well as core features delivered in open source.</p><p>In Corda 4.3 we <a href="https://medium.com/corda/introducing-corda-4-3-b342b7a011c">introduced</a> accounts, a major new capability that we anticipate will help expand the use cases for Corda. Corda Enterprise brings support and maintenance to this capability.</p><p><strong>Operations</strong></p><p>2019 has been a great year as more and more Corda Enterprise nodes go into production, with great applications like <a href="https://www.r3.com/videos/nick-short-from-hqlax-and-jens-hachmeister-from-deutsche-borse-on-their-dlt-journey-with-r3/">HQLAx</a> now up and running, supporting live transactions. With this momentum, we have seen new requirements related to operating nodes in enterprise data centers.</p><p>We have introduced the ability to gain insight into the operational state of a node, with node health check capabilities. In <a href="https://docs.corda.r3.com/releases/4.0/release-notes-enterprise.html">4.0</a> we laid the groundwork by enabling the collection of information about the node to help the R3 support team to provide better service to our customers. Corda Enterprise now provides insights to the node operator on key indicators of whether a node is healthy and performing transactions as it should. The node health survey allows the node operator to verify the node is configured properly by checking it can reach the necessary local components (the bridge and float) and that the configuration files are in proper order (for the node and the Corda Firewall). It can also check that nodes can reach other necessary components on the network (such as the Network Map and the Identity Manager).</p><p><strong>Notary</strong></p><p>In Enterprise 4.3 we have increased our focus on the notary, targeting operations and performance.</p><p>We recognize that customers operating notaries have a varied set of preferred databases. Our new Java Persistence API (JPA) expands the set of databases that can be used, giving you the flexibility to use any supported database with the notary, which will support performance increases as networks grow. The JPA interface expands support in this release by adding <a href="https://www.cockroachlabs.com/">CockroachDB</a> and Oracle 12c RAC to be used as the notary database.</p><p>We have also increased performance of the notary by selecting CockroachDB to replace Percona as our preferred database. The challenge with the notary is it contains a simple data set that grows over time leading to long lookup times. We evaluated a number of technologies to address this while looking to satisfy all three demands we have for a notary database — High Availability (HA), ease of configuration and, of course, performance. Cockroach has great characteristics to support HA and performance that matches our use case well. The notary needs to be highly available to ensure business continuity in the network. CockroachDB helps greatly with this, for example, making it easier to add or remove nodes from the cluster. We are deprecating Percona in this release to give customers time to migrate to CockroachDB.</p><p><strong>Security</strong></p><p>We continue to make progressive improvements on security, with a focus on HSMs. We’ve added Securosys and Azure Key Vault support for the Notary signing keys. We will continue to round out support for all key types across the platform in the supported HSMs. TLS keys that are used for the connection between a standalone Artemis MQ instance and the node can now be stored in the HSM. We’ve also made general improvements to our HSM integration ensuring any failure to connect to the HSM, or an HSM failure, is handled properly with retries and eventual failure of the flows giving control at the transaction level.</p><p><strong>Metering</strong></p><p>With Enterprise 4.3 we are introducing a new pricing model. We will have a separate posting on pricing to explain how you can benefit from a flexible pricing mechanism that grows with you. The new pricing model is usage based, in line with modern pricing we have become familiar with.</p><p>In order to support this pricing, we’ve introduced a new capability — metering. Metering is used for tracking activity related to Corda Enterprise’s pricing model, but it can be used by you to track your own usage across your network. Metering records the activity of signing a transaction locally in the node. This activity is a central event in Corda, or any blockchain, as it represents a definitive moment when you’ve agreed to a state transition that will be recorded on the ledger.</p><p>In order to help our customers, we also capture the command that is signed in the transaction. This gives more insight into what activity has occurred on the node. It allows CorDapp publishers to capture detailed information they can use for various purposes, including their own billing. With insight into the command signed you can create custom billing models where the price could, as an example, vary based on the activity. We are excited not only to provide our customers with a new flexible pricing model for Enterprise, but also to empower you to build out your own pricing models leveraging our platform capabilities.</p><p>All of this was designed to ensure it respects privacy. Information is captured locally in the node only. It is not automatically reported back to R3 or the CorDapp publishers. The node operator can run a flow to query for this information and then must manually send this information to the CorDapp publisher. In a future release we will automate this process, while still ensuring the node operator has opted in to provide information in a transparent manner.</p><p>Head over to <a href="https://www.r3.com/download-corda-enterprise/">r3.com</a> to download an evaluation copy of Corda Enterprise to check out these new capabilities for yourself. You can also read about the minor improvements and bug fixes in our <a href="https://docs.corda.r3.com/release-notes-enterprise.html">release notes</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3e760a8e0cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/corda-enterprise-4-3-is-now-ga-e3e760a8e0cc">Corda Enterprise 4.3 is now GA</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corda Enterprise 4.2 GA]]></title>
            <link>https://medium.com/corda/corda-enterprise-4-2-ga-425720b1baa?source=rss-622f1f6dbf71------2</link>
            <guid isPermaLink="false">https://medium.com/p/425720b1baa</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[corda]]></category>
            <dc:creator><![CDATA[Mike Ward]]></dc:creator>
            <pubDate>Sun, 29 Sep 2019 20:32:25 GMT</pubDate>
            <atom:updated>2019-09-29T20:38:04.697Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Corda Enterprise 4.2</strong></h3><p>I’m happy to announce the general availability of Corda Enterprise 4.2 to our customers. 4.2 continues R3’s leadership, and commitment, to enterprise grade blockchain capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQcH7onmiTWZlTmcckWAww.jpeg" /><figcaption>4.2, now shipping.</figcaption></figure><p><strong>Further support for Hardware Security Modules</strong></p><p>Our main focus with this release is to continue work on securing the cryptographic keys using hardware security modules typically found in enterprise environments. In Corda 4.0 we introduced the ability to store signing keys in an HSM. In this release we add the ability to store the other key types in a participant node. These include keys related to the TLS (transport layer security) as well as confidential identity keys.</p><p>Note that confidential identities may result in a significant number of key pairs being generated by the node. HSMs handle this in different ways so it is important to select the HSM that best fits your intended deployment architecture.</p><p>We also have added additional HSMs requested by our customers including Securosys. We are continuing work to ensure all our HSMs support all three key types, so please check the HSM support <a href="https://docs.corda.r3.com/cryptoservice-configuration.html">list</a> to determine the support level for your HSM including model and firmware versions.</p><p><strong>General Improvements</strong></p><p>We’ve also added a smaller set of improvements in this release that you can take advantage of. Operational capabilities of the node is a key focus of our work as we see more instances Corda Enterprise being deployed into production systems. Improvements include:</p><ul><li>Logging improvements for the HSM and vault to give more insights into what is happening in the node.</li><li>A notary registration <a href="https://docs.corda.r3.com/notary-reg-tool.html">tool</a> that assists in distribution of a shared key among the nodes of a notary cluster.</li><li>Corda firewall deployment improvements. The firewall can check CRLs (certificate revocation lists) to ensure it does not connect to unlisted nodes.</li><li>Flow management improvements with the checkpoint <a href="https://docs.corda.r3.com/checkpoint-tooling.html">tool</a> which outputs information about flows currently running on a node.</li></ul><p>As always, you can get a full breakdown of what is in this release from the <a href="https://docs.corda.r3.com/release-notes-enterprise.html#release">release notes</a>. Be sure to select the correct release number from the navigation. If you have priorities that you want to ensure are reflected in our product roadmap feel free to notify our Product Management team at <a href="/service/mailto:product@r3.com">product@r3.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=425720b1baa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/corda-enterprise-4-2-ga-425720b1baa">Corda Enterprise 4.2 GA</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corda release versioning changes]]></title>
            <link>https://medium.com/corda/corda-release-versioning-changes-6281b02348fc?source=rss-622f1f6dbf71------2</link>
            <guid isPermaLink="false">https://medium.com/p/6281b02348fc</guid>
            <category><![CDATA[r3]]></category>
            <category><![CDATA[corda]]></category>
            <category><![CDATA[versioning]]></category>
            <dc:creator><![CDATA[Mike Ward]]></dc:creator>
            <pubDate>Tue, 03 Sep 2019 15:25:35 GMT</pubDate>
            <atom:updated>2019-09-05T09:01:46.604Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ED8A5sgD9vv1U5mRKayP4A.jpeg" /></figure><p>With the next major release of Corda, we’re revising our versioning to more closely align to industry norms for Enterprise software.</p><p>Internally, we adopt the convention of platforms like Android or Chrome, which have frequently incrementing version numbers. These reflect the rapid progress the platforms are making in capability and is well suited to Corda’s fast-moving improvements. We call this Corda’s “platform version”. As Corda’s original users were developers, we also used this number to name Corda releases themselves. Corda’s version numbers match the platform version they embody. As such, Corda’s own versioning has been developer-centric with a version incrementing when a new API was made available to developers. This would indicate to developers if the API their CorDapp may have depended on was available in the platform it was deployed to.</p><p>As Corda moves deeper into mission-critical environments, Corda’s version number is visible to a larger community. Given how much meaning a version number can hold to different stakeholder groups, it’s time to revisit the policy.</p><p>Large enterprise organizations deploying software often view an incremented version number as disruptive to their current tested configuration. Corda’s frequently incrementing version numbers triggered the policies of these organizations to require retesting of their configuration, which can be an expensive and lengthy process. Often, the release would not deem such a re-test, but tying the Corda version number to underlying (API) platform version lacked the fidelity to indicate this. So this has led to some challenges:</p><ul><li>Major version increments were made whenever a new API was added, even if it did not require any network-level upgrades. This didn’t provide information on the impact of a release to operators of Corda.</li><li>Corda versions jumped even when the underlying change was trivial (e.g. as happened from Corda 1.0 to Corda 2.0).</li><li>We did not attempt to align version numbers for open source and Enterprise. It was difficult to ascertain which Enterprise release contained the same functionality as the open-source release.</li></ul><h3>Review of the release versioning changes</h3><p>As such we have decided to revise our numbering scheme. Our aim is to align with norms for IT operations. Additionally, we aim to give more information on the impact of a release for both developers and IT operations. The new numbering policy has a standard format:</p><ul><li>Major version increments (integer) of Corda are now reserved for cases where an entire network would need to upgrade before all the functionality of a release could be utilized. This includes wire protocol changes or capabilities where network consensus is impacted.</li><li>The first decimal is a simple incrementing release indicating a set of new capabilities that can be adopted unilaterally by node operators or application developers without requiring the whole network to have upgraded.</li><li>We will align the release numbers for Corda and Corda Enterprise. Versions that provide the same functionality will, wherever possible, have the same version number. This means we will sometimes ‘skip’ a minor version if required, as will shortly happen (see below).</li><li>When a new API is added to Corda, we continue to signal this to app developers this through an increase in the “platform version”. The platform version will be indicated in release notes and continue to move as sequential whole numbers. It will no longer move in lockstep with the Corda release number.</li></ul><p>The practical impact will be that the major (integer) version of Corda will be incremented less frequently than before, and OS and Ent versions will be more closely aligned. We anticipate this will give far better information to both developers and other IT professionals and give more clarity on the impact of a release to users.</p><h3>How does this affect you?</h3><p>We’ll be making some changes in our upcoming releases to align with this change.</p><ul><li><strong>The next release of Corda will be 4.3 </strong>(we’ll have more on this soon in a separate blog post). We have previously referred to this internally as ‘Corda 5’. The significance of the release hasn’t changed. The meta-data we will indicate includes the <em>platform</em> version 5 (a detail of importance only to developers).</li><li>We will align Corda and Corda Enterprise starting with the next release. <strong>The next release will <em>skip</em> Corda 4.2 so that Corda 4.3 and Corda Enterprise 4.3 are aligned from a functionality perspective.</strong></li></ul><p>We will not be revising past release numbers to align with the new versioning. Luckily, turns out that had we done such a re-alignment we’d actually be at the same number! Releases through Corda 4 would have necessitated whole number increments as they were either consensus or wire protocol breaking changes. For example, reference States correctly necessitated a bump from Corda 3.x to Corda 4.0.</p><p>We think this simple change will lead to greater clarity in what’s in a release and its impact on all stakeholders. If you have any questions on the above please reach out or visit our <a href="https://stackoverflow.com/questions/tagged/corda">Stack Overflow</a> and <a href="https://slack.corda.net/">Slack community</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6281b02348fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/corda-release-versioning-changes-6281b02348fc">Corda release versioning changes</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transactions Per Second (TPS)]]></title>
            <link>https://medium.com/corda/transactions-per-second-tps-de3fb55d60e3?source=rss-622f1f6dbf71------2</link>
            <guid isPermaLink="false">https://medium.com/p/de3fb55d60e3</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[corda]]></category>
            <category><![CDATA[performance-testing]]></category>
            <dc:creator><![CDATA[Mike Ward]]></dc:creator>
            <pubDate>Fri, 09 Feb 2018 10:49:31 GMT</pubDate>
            <atom:updated>2019-07-15T08:43:35.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8EEQvi4GHc5xViNWbdQNw.jpeg" /></figure><p>[note: with the release of Corda Enterprise 4 we have significantly improved our performance metrics. I’m updating this posting with the new performance metrics where appropriate. Note with Enterprise 4 you can download the test suite and prove it for yourself!]</p><p>The Corda team are involved in a number of projects globally that are looking at how they can ultimately scale their solution to perform at a level demanded by real world use cases. A key criterion in scaling up any blockchain platform is the number of transactions the system can manage. This is top of mind in our engineering team, in particular for our dedicated performance team. We’d like to share our current work and thinking in this area.</p><p>Let’s get right to it with a snapshot of throughput per node we are getting internally at R3 right now as we measure and tune our forthcoming R3 Corda distribution. There is much still to be done but we wanted to share progress to date in our test labs with two specific scenarios.</p><blockquote>1678 TPS &amp; 600 TPS [formerly 170]</blockquote><p><strong>Defining ‘transaction’</strong></p><p>Before we explain these figures, we’d like to put the notion of measuring transactions per second into context. What are the different ways to represent TPS?</p><ul><li>What a <strong>network</strong> can achieve. First generation blockchain systems are constrained at the network level because a large part of the network participates in transactions.</li><li>What a <strong>node</strong> can achieve. For a specific configuration and transaction how many transactions can a node participate in during a single second.</li><li>The <strong>duration</strong> of a transaction. For a single transaction how long does it take to span all nodes from inception to finality.</li></ul><p>In stark contrast to first generation systems, the network figures for Corda will increase as you add more nodes. Corda does not require a shared consensus mechanism across a large percentage of nodes. It is a point-to-point system so as peers transact it does not affect non-participants to those transactions. Hooray!</p><p>The key constraints that we worry about on the Corda team are the nodes ability to transact in many transactions in a set duration, and the duration of a transaction.</p><p><strong>1678 TPS</strong>. This figure has been obtained for a type of transaction that takes place on a single node demonstrating the performance the flow state machine can obtain. This transaction type is for an issuance of a new state to the ledger of the local machine.</p><p><strong>600 TPS</strong>. This figure is for a complete transaction from the perspective of a node. A payment with two parties, as an example. We believe this is a more realistic assessment of measuring what matters in a Corda network.</p><p>These are real transactions and constitute real measurements of performance in terms of TPS. Of course, we are working feverishly to keep pushing the 1678 and 600 TPS figures higher and have begun this work in earnest following our 1.0 release.</p><p><strong>Making comparisons</strong></p><p>The reality is TPS is only relevant when compared against a transaction of a similar nature on an identical set of constraints. Ultimately, what we are seeking broadly is an aggregate view of how many transactions a single node is capable of participating in across a variety of transaction types.</p><p>The various distributed ledger technologies differ in how they define a transaction. For Ethereum and Fabric the transaction is measured from the submission of a contract to the network for consensus and the adding of the transaction to a block. In contrast, Corda has three characteristics that are unique and must be understood in order to determine how to effectively measure performance and, importantly, how to compare it to other platforms.</p><ul><li>Transaction building</li><li>Transaction finality</li><li>Consensus algorithm</li></ul><p>Flows are a component of the Corda Platform not found in other systems. The purpose of the framework is to build a transaction between parties. We recognised that building the transaction is a common technical challenge that developers were faced with continually. With no consistent and agreed upon framework in place developers solve this same problem over-and-over again. Corda tackles this problem directly in the platform by abstracting away the challenges of maintaining state across systems, obtaining and verifying signatures and obtaining data in a deterministic manner.</p><p>Corda transactions are final at the time of signature by the service responsible for consensus over uniqueness of the transaction inputs. Corda networks operate this service, known as Notary Pools, as a set of distrusting entities operating in consensus. This separation is what allows Corda to to operate as a point-to-point system while retaining all the blockchain characteristics. In contrast other systems require consensus across nodes and transactions are not final until sufficient block depth is achieved.</p><p>The Notary Pools are able to use ‘pluggable’ algorithms for consensus. While a pool must consistently use a chosen algorithm, they may initially select any algorithm that has been established for use in the Corda platform. This means they may select RAFT and BFT currently, or alternate algorithms that may be offered by other vendors.</p><p>With these unique characteristics in mind we believe the following are key variables that will affect how you measure performance:</p><ul><li>Transaction building. To compare to other platforms the transaction would need to be built and measured from the point of submission to the Notary Pool.</li><li>Number of parties in a transaction. If measuring with the transaction builder, the complexity of the transaction increases with the number of parties involved.</li><li>The consensus algorithm must be comparable. Among the tradeoffs in selecting an algorithm performance is the main variable.</li><li>The transaction should be defined as validated or non-validated. This should be consistent across platforms.</li></ul><p><strong>Consistent variables</strong></p><p>Unlike the more mature spaces of relational databases or virtualisation the DLT space lacks a standard definition of what a transaction is and how to compare across platforms. In the database realm this is the responsibility of an independent organisation, <a href="http://www.tpc.org/">TPC</a>. TPC has a standard measurement for comparing the performance of database platforms against a well-defined set of constraints including a consistent data set, a consistent query in ANSI standard SQL run against a consistent hardware and operating system configuration. Without such consistency the measurement would be unscientific in nature as it would be unable to isolate performance issues to the database engine vs. other variables.</p><p>Our internal testing is against a consistent hardware and network configuration. As a part of our performance work we’ll be publishing this specification along with the specifics of the transaction properties. We are working against a defined set of variables held consistent for accurate measurement:</p><ul><li>Transaction payload: for a validated transaction the definition of the payload and business logic must be consistent. This consists of a consistent set of data fields with defined types and length equating to a measurement in kilobytes.</li><li>A consistent business logic based on the validation logic for the transaction. This should be provided in pseudocode and may be optimised on each platform.</li><li>A consistent hardware and network environment.</li><li>Latency between the participant and other nodes must be consistent if measuring overall network performance (vs. single node performance).</li><li>CPU performance, memory and other hardware characteristics should be consistent.</li><li>The operating system must be consistent, and the system should be clear of any auxiliary software (antivirus etc).</li></ul><p>For our test noted above we used Microsoft’s Azure infrastructure running SQL Azure. Specifically, we used the VM standard D32 v3 (32 vcpus, 128 GB memory) machine and 4000 DTU database (P15). For future published benchmarking operations, we shall denote the specific hardware and environment in order to ensure we can control all variables.</p><p><strong>Comparing Corda to other platforms</strong></p><p>R3 believes organisations such as Hyperledger are well placed, and should take a leadership role, in working toward a consistent definition and measurement similar to the aforementioned TPC. In the early stages of evaluating this metric, however, care must be taken to ensure the comparison is done in a like-for-like manner. We offer the following standard for consideration on comparing Corda’s performance to alternate platforms. The following is how you should measure a transaction on Corda to be able to make a comparison:</p><ul><li>Start should commence from the point at which the party that is building the transaction (contract or other terms) does its own verification and submits the transaction to the Notary Pool for a uniqueness check. This matches platforms without a transaction building capability.</li><li>Finish should be regarded as the point at which the transaction has been acknowledged as being added to the record which is used for assurance of double spend (the ledger).</li><li>All variables such as the transactions, hardware and network properties should be consistent.</li></ul><p>While we have seen published claims for TPS performance we have not discovered how those transactions are measured on alternate platforms, or what they believe constitutes a transaction. But currently <strong>Corda measures between 15 and 1678 TPS</strong> depending on how it is measured. This is contrast to other platforms:</p><ul><li>Bitcoin <a href="https://blockchain.info/charts/transactions-per-second">peaks out</a> at around 7 TPS</li><li>Ethereum is <a href="https://www.coindesk.com/information/will-ethereum-scale/">limited to</a> around 15 TPS</li><li>Quorum has stated a target of “dozens to hundreds of transactions per second depending on configuration” in their <a href="https://github.com/jpmorganchase/quorum-docs/blob/master/Quorum%20Whitepaper%20v0.1.pdf">white paper</a>.</li><li>Hyperledger Fabric. As Chris Ferris <a href="https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-October/001896.html">noted</a> “We haven’t published performance figures for Fabric because there isn’t a standard benchmark.”. A recent <a href="https://www.ibm.com/blogs/research/2018/02/architecture-hyperledger-fabric/">blog posting</a> noted Fabric achieves 3500 TPS. We believe this measurement is a view of the total network transaction and incomparable as Corda does not have this constraint.</li></ul><p><strong>Conclusion</strong></p><p>Organisations that are viewing TPS in isolation are doing themselves a disservice. They should view throughput as one variable in the overall performance of a system. Other characteristics such as resiliency, ability to make a trade-off in performance for assurance are as critical if not more so. A highly performant system that has little privacy and no high availability configuration would be an unbalanced trade-off that would introduce risk into the overall system.</p><p>As we lead up to our upcoming releases of Corda, in both the open source and R3’s commercial distribution, we’ll be publishing more statistics around performance. Our vision of building a network capable of supporting some of the largest workloads that amount to billions of daily transactions puts performance as a key target for our own engineering efforts. While we continue to push Corda forward in performance we are also <a href="https://medium.com/corda/dlt-performance-considerations-7e1a2cc964b0">collaborating with IBM and others</a> in the Hyperledger working groups to drive an industry standard for performance evaluation and general principles for performance. Look for more postings from our performance team on our blog to follow our progress.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de3fb55d60e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/transactions-per-second-tps-de3fb55d60e3">Transactions Per Second (TPS)</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>