Welcome to BigLedger Knowledge Center!

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Current »

BigLedger’s architecture is designed to connect, scale, and automate processes for seamless business operations. It functions as a centralized hub for data exchange, real-time communications, and secure transactions across multiple platforms, making it adaptable for a range of enterprise applications and IoT environments. Below is a summary of BigLedger’s main architectural layers:

  1. Client Layer

    Mobile and IoT Support: Compatible with mobile apps (iOS, Android) and IoT devices for data access from any platform.
    Embedded Communication: Supports integrated messaging channels like WhatsApp, Skype, and Twilio for customer and team interactions.

  2. Core Integration Platform

    Central Data Hub: Acts as the main exchange point for business documents and data, such as invoices and purchase orders, integrating with applications like SAP, Oracle, Xero, and QuickBooks.
    PEPPOL Compliance: Ensures international invoicing standards through PEPPOL, simplifying cross-border transactions.

  3. Backend Services and Microservices

    Microservices Architecture: Composed of modular services that handle document management, e-invoicing, and payment gateway integrations (e.g., PayPal, Stripe, FPX).
    Cloud and AI: Utilizes AWS and Azure for scalability, with AI tools like Digital Twin technology for predictive analytics.

  4. Infrastructure and Storage

    Database Layer: PostgreSQL for transactional data, supported by Amazon RDS for high availability.
    Document Storage: Amazon S3 manages large volumes of documents securely, with backup and retrieval integrations.
    Deployment Platform: Uses AWS Elastic Beanstalk to simplify application deployment and manage scaling.

This architecture enables BigLedger to be scalable, adaptable, and resilient, supporting complex business processes with high-performance infrastructure.

  • No labels