Database
Choosing the right database management system (DBMS) is critical for the success of any modern application, especially when it spans multiple technologies such as React, Node.js, and blockchain. For Authentify It, MongoDB has been selected as the primary DBMS for its flexibility, performance, and scalability, aligning perfectly with the hybrid Web2/Web3 architecture of our platform.
Why MongoDB for Authentify IT?
MongoDB is a NoSQL, document-oriented database that integrates naturally with JSON-based data models used in Node.js and React. This makes it an ideal choice for a project that combines traditional web applications with blockchain-based assets.
Key Advantages
Flexible Data Structure
Stores data in JSON-like documents, making it easy to integrate and process heterogeneous datasets.
Facilitates synchronization between Web2 databases and Web3 blockchain metadata.
Horizontal Scalability
Distributed architecture allows adding nodes seamlessly to accommodate growing datasets.
Critical for handling large-scale blockchain data, where transaction volumes and NFT issuance can grow unpredictably.
Optimized Performance
Supports complex indexing and querying for high-performance access.
Ideal for blockchain-heavy applications with frequent, complex queries across certificates and tokens.
Node.js Compatibility
Native drivers simplify integration with the Node.js backend.
Reduces development time, simplifies maintenance, and improves reliability.
Community & Ecosystem Support
Widely adopted with an active developer community.
Access to tutorials, libraries, and technical support ensures robustness and reduces risk.
Hybrid Data Management
Authentify It implements a hybrid Web2/Web3 architecture to harmonize traditional database management with blockchain-based data:
Each physical product has a digital twin, represented as an NFT or Fungible Token on Solana.
Certificates are generated in batches and linked to a brand (for NFT) or unique with multiple owner (for FT).
NFTs are used for unique metadata or low-supply collectibles.
Fungible Tokens are used for mass-market certificates to minimize gas fees.
Practical Implementation
User-specific updates (Web3): Immutable events for individual products, stored on-chain (e.g., repairs, ownership transfer).
Brand-wide updates (Web2): Shared information for all certificates, stored in MongoDB to reduce costs (e.g., user manuals, updates to product info).
Certificates become unique once in the user's wallet, reflecting the hybrid management of shared and user-specific data.
Example NFT Life:
Verticals in the Sport Ecosystem
Gear
NFT
Unique, evolving metadata for each product lifecycle
Collectibles
NFT
Low-supply verification and authenticity
Merchandising
Fungible Token
Mass-market certificates, one token per user, ownership verification
You can see all database schemas for both APIs in the Models section of:
LifePass App REST API documentation:
REST API (private)LifePass Studio REST API documentation:
REST API (private)Data Models & API Integration
MongoDB collections support two REST APIs (LifePass App and LifePass Studio).
Robust cross-checking between collections ensures consistency and enables seamless product lifecycle tracking.
Data models are designed to handle both Web2 queries and on-chain interactions, providing a unified experience.
Hosting & Backup
Hosted on MongoDB Atlas, leveraging cloud-native architecture for reliability and performance.
Automatic snapshots allow point-in-time recovery (every 6h).
Snapshots can be restored in one click, ensuring data integrity and business continuity.
Last updated