📁
shine
  • Introduction to the Shine Blockchain platform
  • Shine overview
  • Shine USP
  • About EOSIO
  • Consensus mechanisms
  • Shine Proof of Authority consensus
  • Data privacy
  • Scalability
  • Business details
    • Why Blockchain
    • Why another Blockchain platform
    • Applications of Shine
      • Assumptions
      • Precious metals traceability
      • Food traceability
        • Spices
        • Perishables
        • Seafood
      • Carbon footprint monitoring
  • Tools, Technologies, and Architecture
    • Docker
    • MongoDB
    • Encryption
    • Server Security
    • Server requirements
    • Architecture
    • Transaction flows
  • Protocol
    • Microservices and APIs
    • Account management
  • Shine Blockchain Setup
    • SHINE Software Installation
    • Create Private/Public key pairs
    • Start the Blockchain node
    • Deploying System Smart Contracts
    • Add Producer/Validator Nodes
    • Node Security Setup
    • Deploying Traceability Smart Contracts
  • Backend Setup
    • Installing Prerequisites
    • Starting The Application
  • Front end Setup
    • User Interface
Powered by GitBook
On this page
  • Shine Platform Architecture
  • Blockchain Deployment Architecture

Was this helpful?

  1. Tools, Technologies, and Architecture

Architecture

Application architecture, Blockchain architecture, Deployment architecture

PreviousServer requirementsNextTransaction flows

Last updated 4 years ago

Was this helpful?

Shine Platform Architecture

User will have to log in with the given credentials and import/generate a to interact with and perform actions on Shine. The architecture and data flow of the platform is given below:

  • User sends an authentication request to the api gateway server.

  • The api gateway forwards the request to the authentication which returns the JWT token to the user.

  • When the user modifies or adds new data, he signs the request with his/her private key.

  • Once the microservice receives the data, it checks for user authorizations and binds the data to ensure the validity of the request.

  • Microservices then forwards the signed transaction to the blockchain middleware (which enables all of the communication between the api services and the blockchain).

  • If the transaction is successfully executed and validated (signatures and smart contract validation) or fails, the blockchain middleware enables sending the relevant responses back to the microservice.

  • Microservices then sends the response to the web application and the relevant information is shown to user.

Blockchain Deployment Architecture

Our deployment model is totally compatible with on-premises servers, any cloud service provider, or a hybrid. Each of the nodes in the network implements the same consensus algorithm and transacts using the same consensus protocol in order to communicate with other nodes in the same network. Deployment of each node can be done based on the business requirement, so some nodes can on-premises and others in the cloud.

Cloud environments have some benefits over on-premises and could typically provide availability zones, load balancers, DDoS mitigations, and so forth; these can be easily deployed, further simplifying and accelerating cloud deployment of nodes and enabling accelerated deployment of the Shine blockchain.

The following is our architecture framework:

Below is our IaaS model (Infrastructure as a Service) which helps in reducing the costs, and enables easy maintenance of the deployment of the Blockchain. This enables to create and host nodes as needed.

microservice
actors
blockchain account key
Shine Architecture
Deployment Architecture