Data Architecture: Difference between revisions

From Lux-Ear Internal Knowledge Base
Jump to navigation Jump to search
VisualWikitext
(New Data Architecture page)
 
m (→‎Architecture Diagram: clean up text)
 
Line 45: Line 45:
* Stripe: Payment integration via Firebase Cloud Functions.
* Stripe: Payment integration via Firebase Cloud Functions.
* AppCheck: Ensures requests come from verified app clients.
* AppCheck: Ensures requests come from verified app clients.
\=== How to Add This Page to the Internal Wiki ===
1. Log into the Lux-Ear Internal Knowledge Base.
2. In the search bar or URL, go to:
  `https://ikb.lux-ear.com/index.php?title=Luxear_data_architecture`
3. If the page does not yet exist, click "Create this page".
4. Copy and paste the entire content of this document.
5. Save the page.
6. To link this page from another, insert:
  `[[Luxear_data_architecture|Data Architecture]]`
  For example, from your main index or technical documentation section.
7. To upload the diagram:
  * Go to "Upload file" in the left sidebar.
  * Upload `LuxEar_Data_Architecture_Diagram.png`.
  * Make sure the filename matches the one referenced in the `[[File:...]]` tag above.


=== Author ===
=== Author ===
Scott McGregor
Scott McGregor
Lux-Ear Founder and Product Strategy Lead
Lux-Ear Founder and Product Strategy Lead

Latest revision as of 21:29, 19 May 2025

Lux-Ear Internal Wiki[edit | edit source]

Page: Data Architecture[edit | edit source]

Overview This page describes the proposed data architecture for Lux-Ear, leveraging Firebase to provide scalable, real-time infrastructure for kiosk scanners, customer-facing apps, internal tools, and cloud-based services.

Architecture Diagram[edit | edit source]

Proposed Firebase-based architecture for Lux-Ear

Key Components[edit | edit source]

  • Firebase Authentication
 * Authenticates users and devices (e.g., kiosk operators, customers, franchisees).
 * Supports multi-platform logins and enforces secure, role-based access.
  • Firestore (Cloud Firestore)
 * NoSQL database used to store metadata for scans, kiosk statuses, user profiles.
 * Real-time updates across web and mobile clients.
 * Offline caching support for kiosk and mobile operations.
  • Firebase Cloud Storage
 * Stores large files including 3D ear scans, images, diagnostic logs.
 * Access control rules tied to user or kiosk identity.
  • Firebase Cloud Functions
 * Hosts backend logic for events like scan upload, payment processing, and scan-to-CAD conversion.
  • Firebase Hosting
 * Serves static pages and web applications (e.g., Find a Scanner, Admin Dashboard).
  • Analytics and Crashlytics
 * Provides usage statistics, session tracking, and error diagnostics.

Optional Extensions[edit | edit source]

  • Google Cloud Vertex AI: AI-based modeling of ear shapes.
  • BigQuery: Advanced analytics on scan volumes, locations, and trends.
  • Stripe: Payment integration via Firebase Cloud Functions.
  • AppCheck: Ensures requests come from verified app clients.

Author[edit | edit source]

Scott McGregor Lux-Ear Founder and Product Strategy Lead

Retrieved from "https://ikb.lux-ear.com/index.php?title=Data_Architecture&oldid=130"