Technical Details
WebsiteDiscordOverviewSupport
  • Overview
  • Identity Protocol
    • Overview
    • Registry
    • Nodes & NFTs
      • Manufacturer
      • Vehicle ID
      • DeviceID
      • License
    • Auxiliary Contracts
      • Access Control
      • AdLicenseValidator
      • Eip712Checker
      • Mapper
    • Architecture
    • Pairing
  • Device Canonical Name
    • Overview
    • Contracts
      • DcnRegistry
      • DcnManager
      • PriceManager
      • Resolvers
  • Token & Governance
    • Token
    • Rewards
    • Governance
  • Data
    • Platform Components
    • DBC Decoding
    • Software-Only Connectivity
    • Data Storage
    • Validation
    • Data Dictionary
      • Sample Data
  • Hardware
    • Ecosystem
    • Open Hardware Spec
    • Manufacturing License
      • DIMO Memorandum of Understanding
      • Staking $DIMO for a Manufacturer License
    • Device License
      • Device Minting Certificate
      • Hardware and Security Audit
      • Testing and Quality Control
  • Abstraction
    • Sign In With Ethereum
    • Metatransactions
  • Security
    • Methods
    • Audits
    • User Privacy
Powered by GitBook
On this page
  • Hosting
  • Authentication
  • Core Services
  • Ethereum & Polygon
  1. Data

Platform Components

The makeup of the DIMO Core Platform

PreviousGovernanceNextDBC Decoding

Last updated 2 years ago

Deployment

Hosting

It is very important for DIMO that the platform is hosted in a manner which guarantees high uptime, great user experience, and rapid development.Today, the application is hosted on Kubernetes utilizing major cloud providers. Kubernetes allows the web2 and web3 components which are not yet decentralized to be run by DIMO Web Services team, and will enable decentralization as the platform grows.

Authentication

Core Services

To deliver the full suite of functionality required by the platform, multiple microservices have been developed. They broadly fall into 2 categories:

  • Streaming Analytics

  • Rest/GRPC Apis

Ethereum & Polygon

DIMO utilizes both Ethereum and Polygon for storing the most important data within the platform. Making this data available on a public database provides a decentralized solution to answer a few key questions:

  • Who owns a device

  • Definition of what a device is

  • Link(URI) to verified data stream

IPFSDIMO plans to leverage IPFS for storing device data. At the current time IPFS has a limited role to play in cold-data storage.​

When it comes to authentication, DIMO supports both oAuth and Sign In With Ethereum for most user flows. This is implemented in , an open source CNCF project.

You can find the code available publicly under the DIMO-Nework organization on .

dex
github