Architecture description

For a better scalability and utilization of blockchain technology benefits, BRIXBY uses microservice architecture. Each business function is allocated in a separate microservice.

Two Ethereum networks (public and private) are used to store and verify each transaction (communication unit between any two microservices).

Users and third-party systems interact with the platform via BRIXBY and third-party interfaces. Such interactions are regulated by the rules defined in the Business Service Smart Contract (the only public Smart contract available for BRIXBY users).

In case of using complex business logic (e.g. Parking, EV-charging or Car sharing), Business services interact with Core services via RESTful APIs. Such interactions are regulated by the rules defined in the Core Service Smart Contract (not available for users and third party-systems).

  • The architecture consists of:
    • Microservices
    • Core microservices
    • Business services
  • Interfaces
    • User/Applications interfaces
    • 3rd party interfaces

Core microservices

Core microservices can be used as a separate application by users, the terms of use are determined by smart contract. There is also a possibility for users to combine core microservices into any other business services they may desire, if the business services provided by BRIXBY do not satisfy their needs.

Core microservices are distributed under BRIXBY open license that allows using the microservices as separate applications according to the tariffs and provides access to the source code with right to modify it. In case of modification, changes should be merged to a specific BRIXBY’s repository fork on GitHub. Currently BIXBY ecosystem has the following core microservices: Billing, CRM, SMS/USSD gateway, Payment gateway, SSO, Business analytics, Enforcement, Assets registry.

Core microservices that will been designed during next phase are: Loyalty Services and Users Profiles.

 

Business services

Business services are based on a set of core microservices. All the internal transaction generated between core microservices for business services are calculated in a private blockchain. For the sake of transparency, these transactions can be monitored in BRIXBY ledger explorer and are periodically transferred as a bulk transaction into the public Ethereum blockchain, thus public network is used for verification of internal private transactions. Also, all business transactions, conducted via the public smart contract, are calculated in public Ethereum blockchain. The ledger explorer also allows linking private to public transaction.

Business services are distributed under BRIXBY closed license that allows usage of the services according to the tariffs, however does not provide access to the source code. The terms of use are determined by smart contract for each business service.

Currently BRIXBY ecosystem provides three primary business services:

 

  • Parking. Users will get all needed functions to setup, manage and provide digital parking service, including inventory of parking assets and mobile payments. Parking service also includes protocols for third party hardware integrations, modern and convenient user apps.
  • EV charging. Users will get EV-charging functionality, including but not limited to: hardware integrations using OCPP and other protocols, charging stations inventory and modern and convenient user apps.
  • Car sharing. This service allows vehicle owners rent  their vehicles to other consumers at times when they are not using them. The service includes owner’s and consumer profiles with rating, vehicle search and mobile payments, as well as modern and convenient user app.

 

 

Third party services

Priority of BRIXBY modules are universal, for instance, billing, CRM, payment gateway, enforcement, and so on. We offer any service provider, be it quality control or medical equipment sales, use BRIXBY modules as an open source software to fulfil their needs and be more transparent. What is more, any 3rd parties may register their business modules on BRIXBY ecosystem if using Core microservices, each business module is subject to BRIXBY’s team approval.

User/Applications interfaces

BRIXBY and white label interfaces provide such modern communication channels for BRIXBY users as apps, chatbots, SMS, web apps, etc. Various user interfaces can be used to work with the same business module, based on the market preferences. If using BRIXBY service brand, service operators may request BRIXBY user interfaces to be adapted based on market needs, such as local language, payment or communication channel needs. The requests will be evaluated by BRIXBY team and features will be provided based on BRIXBY business roadmap. If an operator wants more modifications than changes described above or what to create a separate service brand, white label user interfaces shall be used for this purpose.  

BRIXBY and white label interfaces — are distributed under BRIXBY open license that allows using the microservices as separate applications according to the tariffs and provides access to the source code with right to modify it. In case of modification, changes should be merged to a specific BRIXBY repository fork on GitHub. User interfaces may be customised in color and branding if users are looking for something extra for their consumers. 3rd party interfaces allow connecting services to 3rd party hardware and software, which is essential for providing full scale centrally managed digital services.

Currently there are 4 applications for parking module, 2 applications for EV charging module, parking chatbot, SMS/USSD channel for parking, EV charging and car sharing. Car sharing app still needs to be developed.

Smart Contracts

Smart contracts are protocols intended to facilitate, verify, or enforce the terms and performance of a contract between microservices, business services and 3rd party applications.

The best part of BRIXBY’s modular structure is that businesses may use only those services, which are currently applicable for their size and processes, thus allowing for lean IT infrastructure. However, one of the most important benefit is that there is no need to use back office for reconciliation since each transaction is confirmed by a blockchain network.