Skip to content

Conversation

@fowlerrr
Copy link

High level overview of how we're planning on integrating native EVM communication with Corda 5.

Still to come:

  • An overview of Corda 5 and Ethereum networks working together (with a picture)

Signed-off-by: Ryan Fowler <fowlerrr@users.noreply.github.com>
@fowlerrr fowlerrr self-assigned this Aug 11, 2023
@fowlerrr fowlerrr requested a review from a team as a code owner August 11, 2023 14:47
Copy link
Contributor

@gendal gendal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for submitting this Ryan. Just some very basic questions from me. I assume one of the team who is closer to it will do a thorough technical review. But I'm super happy to see it.


Before we continue it's worth revisiting the architecture of Corda 5. Corda 5 operates as a cluster or [workers](https://docs.r3.com/en/platform/corda/5.0/key-concepts/cluster-admin/workers.html), each of which may contain one or more `processors`.

The workers are the runtime applications, while the processors are what do the work. It is possible, and even likely, that we will have multiple workers running at a time, allowing for some parallelism of the processors, giving us the ability to execute multiple instructions (in our case, EVM commands) at the same time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a danger that 'application' is ambiguous here? (ie these are not the 'applications' that a customer writes, right? although they may execute some customer code). Perhaps we call them the 'runtime services' or 'runtime components' of Corda?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll use services. Thanks

Signed-off-by: Katelyn Baker <katelyn.baker@r3.com>
Co-authored-by: Katelyn Baker <katelyn.baker@r3.com>
Signed-off-by: Ryan Fowler <fowlerrr@users.noreply.github.com>
Signed-off-by: Ryan Fowler <fowlerrr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants