In-House Systems vs. Third-Party Integrations
The LearnWay ecosystem combines proprietary in-house platforms with enterprise-grade third-party infrastructure to deliver a performant, gasless, and gamified learn-and-earn experience.Ecosystem Boundary Map
1. In-House Built Systems (Core IP)
All components in this category were developed in-house to power LearnWay’s unique business logic, gamification rules, on-chain execution, and user experience.2. Integrated Third-Party Infrastructure & APIs
LearnWay integrates best-in-class external services to ensure enterprise scalability, global payment accessibility, and high availability.Architectural Separation Principles
- Decoupled Failure Domains: Failure in any third-party service (e.g. Gemini LLM outage or Fonbnk API maintenance) is isolated by circuit breakers and does not bring down core lesson navigation or local user progress.
- Abstracted Interfaces: Third-party providers are wrapped behind internal NestJS services and providers (e.g.,
PaymentService,BlockchainProviderService,AiService), allowing providers to be swapped or multi-homed without modifying domain business logic. - Optimized Cost Architecture: In-house caching layers (such as the 24-hour deterministic Redis cache for AI responses) minimize external API token consumption and vendor costs.