The BCware Web2/Web3 Integration and Workflow Automation platform is what leading industry analysts have identified as central to a new generation of networked commerce and community.
Whether your definition of Web3 is decentralized finance, tokengated commerce, or connecting communities around shared values, BCware can help bridge the gap between traditional Web2 applications and protocols and Web3 blockchains and services.
The BCware Web2/Web3 Integration and Workflow Automation Platform enables traditional institutions to reinvent themselves by bridging their existing Web2 infrastructure and applications to the promise of decentralized applications and the tokenization economy of Web3.
Companies have large investments that need to be bridged with, not replaced by, Web3. Data and connectivity is needed between existing applications and protocols, and Web3 services such as IPFS or Fireblocks. Web3 is evolving quickly, with different chains emerging for a variety of use cases.
BCware is a blockchain agnostic, multichain platform that abstracts away the complexity of each chain so teams can focus on delivering business value.
There are four key elements to the platform:
The BCWare Web2/Web3 Integration and Workflow Automation Platform has been built to develop portable and scalable Web3 applications, hiding the complexities of the underlying blockchain platforms and seamlessly connecting with the existing Web2 infrastructures.
The BCware Studio makes it simple to create Flows, the integration workflows that power business automation, enabling and supporting Web3 innovations. Developers can move quickly, taking advantage of Flow reuse, and separating Web2/Web3 integration from application development.
As organizations move to scale Web3 initiatives they require end-to-end visibility into business processes, events, and data to shift their focus away from integration and toward business automation. The BCware Studio’s visual Flow editor helps teams visualize the connections and dependencies between Web2 and Web3 components while exposing events to enable real-time decision making and auditing.
Flows are deployed into the BCflow engine right from BCware Studio where developers can then use GraphQL APIs to expose and incorporate the Flows into their applications. Flows are persisted in a Flow repository where they can be shared and reused; evolving as the business requirements evolve.
BCflow is an on-chain off-chain workflow orchestration engine.
Essential business processes are encapsulated in BCflow then exposed as GraphQL APIs. In BCflow, these digital processes are referred to as Flows while the individual steps within a Flow are called Tasks. Tasks and Flows are the activities that are performed on behalf of client applications, and it is the BCflow engine that orchestrates the work specified.
Flows are event-driven and dispatched in response to an incoming event or in response to a procedure call via a Business API. Message and event sources are the topic of the section following, Connectors.
Flows are built using a graphic user interface in accordance with user stories that define the problem to be solved or business function to be implemented. These Flows are often business vertical specific and provide functions such as KYC ID Validation or a Credit Check for the financial services verticals; Pick, Package, and Ship sequence of Tasks in a Warehouse Fulfillment Flow; or NFT Minting or Crypto Asset Management for an NFT Exchange Flow.
In the drawing above, BCflow is a pipeline processor bracketed by Connectors that serve as data or messaging sources or sinks. When an event triggers a Flow, the event along with its complete context is executed by a BCflow Agent. BCflow Agents run in parallel, and scale as needed, providing the level of performance, scalability, and resiliency desired by application owners.
It’s useful to realize that because Connectors are abstracted away from the Flow implementation, decisions can be made at run-time on which Connector to call. For example, a person purchasing an NFT can decide which chain to mint it based on their preferred choice of wallet or coin. Or, different KYC services can be used based on geography or business requirements. For internal applications, it becomes simpler to plug-in new enterprise applications as sources or sinks of data as the business evolves or use-cases spread to departments using other back-end applications or messaging protocols.
Bi-directional Connectors form the base layer of the BCware Web3 Integration Platform architecture. A Connector is a proxy for a Web2 application, blockchain, Web3 service, or messaging protocol for the Flow’s source or sink. Application teams build BCware Flows without locking themselves in to lower-layer application architecture choices. A Flow that outputs a message, can output that message as a NATS message or put it on a JMS queue simply by connecting the appropriate Connector to the end of the Flow.
A key concept in the BCware Integration Platform design is that of Symmetrical Abstraction. The idea that regardless of the Connector chosen, BCflow Flows are able to use each Connector (of similar type) symmetrically; meaning without developing to the specifics of the Connector.
Connectors are grouped into four types:
For a complete list of Connectors available, please get in touch.
The benefit of the BCware Connector architecture pattern is most obvious in the way multichain solutions are supported; Flows are blockchain agnostic. The Connector packages up the specific routines necessary to communicate with each individual chain. The BCflow Agent grabs the package of routines, along with the Tasks and task context, when a blockchain’s Connector is called.
Symmetrical Abstraction also allows applications created with the BCware Web3 Integration Platform to easily be multichain enabled. As an example, the following shows our initial Shopify NFT Application implementation:
Each chain is represented by a Connector at the terminal point of the Flow, enabling extra flexibility on the part of designers to adapt their applications as new chains emerge, or new requirements (such as gas fees, or environmental impact) demand chain flexibility.
Custom connectors can be written for internal applications or protocols, and then are used in the same way as native Connectors.
A Business API is a BCware Flow exposed as a GraphQL API for a Web2 or Web3 application to consume or trigger events. These APIs can be used in the same way as any other GraphQL API within the organization, or beyond.
BCware’s Business APIs simplify the integration of existing business processes with new dApps for an accelerated entry into the Web3 world while simultaneously preserving their IT investments in Web2 applications and protocols.
GraphQL APIs give application teams a few different benefits: