PegaSys Orchestrate FAQ
What is PegaSys Orchestrate?
Orchestrate is a blockchain Transactions Orchestration system that abstracts blockchain complexity and can operate multiple chains simultaneously. It provides production grade and agnostic mechanisms for transaction crafting, nonce management, transaction signing, transaction receipt listening, transaction receipt decoding, faucet and more.
Orchestrate is a Plug & Play component, as a user only needs to send a business protobuf message to Orchestrate input topic. Orchestrate then manages the full life cycle of the transaction from crafting the transaction to decoding event logs data. Allowing enterprises to accelerate, standardize and strengthen all blockchain implementations.
Orchestrate can be a fully-managed service, SaaS or on-premise.
To which kind of users is PegaSys Orchestrate addressed?
Orchestrate users are Solutions Architects, Developers, Integrators and Operations Engineers developing, deploying and scaling blockchain solutions.
What kind of architecture has been used to build PegaSys Orchestrate?
Orchestrate has been built with a containerized Microservices architecture, appropriate for enterprise implementation. Orchestrate is made of workers and APIs that communicate using Protobuf through GRPC and a message broker (by default Kafka). By default, stateful containers use a Redis for key value & cache), a PostgreSQL database and a HashiCorp Vault.
Will PegaSys Orchestrate be open source?
While Orchestrate is not open source today; our team is strongly supportive of Open Source solutions and we hope that part or all of Orchestrate will be open-sourced one day.
Which use cases are a priority for PegaSys Orchestrate development?
Orchestrate is use case agnostic, as such it can be used for any business use case (Supply chain, Finance, etc.).
Therefore, there is no priority business use-case(s) other than the ones adopting Orchestrate. In future releases, we foresee features which will enable specific use-cases.
Is PegaSys Orchestrate specific for financial services?
No, Orchestrate is aimed at being part of the ConsenSys reference architecture and as such can be used for any blockchain use case.
This being said, Orchestrate provides features which are highly relevant for financial services (e.g. bridges, which enables to move digital Assets from one chain to another).
Is PegaSys Orchestrate for Track & Trace?
Orchestrate is not use case specific and can be integrated in Track & Trace solutions.
Why PegaSys Orchestrate does not use plasma group as a layer 2 solution?
Orchestrate uses bridges to interoperate sidechains and move digital assets between them, at difference from the Plasma Group that solves for scalability.
Use cases with a need for bridges presented to Orchestrate need to make 2 EVM chains interoperate. Thus an approach closer to Parity Bridge was chosen. (Instead of Plasma which is UTXO).
Are private keys leaving Hashicorp vault? If so is there any plans to use vault plugins to sign with vault?
The Vault plugin is not supported by the latest version of Hashicorp Vault. That’s why we have decided to isolate the Hashicorp Vault with a component signing the transaction.
How should backend and PegaSys Orchestrate interact?
Orchestrate makes integration smooth by relying on well established and battle-tested technologies Apache Kafka and protobuf standardized message. For a quick-start, a NodeJS SDK is already available. In order to allow seamless integration with Kafka, we intend to soon propose SDKs in most common languages like GO, Java and Python.
How are disaster recovery and transaction recovery handled?
By default, Orchestrate provides high availability and strong resilience. In case of disaster recovery, Orchestrate is able to replay transactions from any point in time. We use storage persistence for both transaction recovery and disaster recovery.