Tonic Application Architecture

Tonic Application Architecture

I presented this on an internal session to all the team members of Telenor Health including developers, dev ops, QA and all.

778ab3e12267bd05ff7bac226fb2027d?s=128

Nuruzzaman Milon

March 29, 2018
Tweet

Transcript

  1. Tonic Applications Architecture Nuruzzaman Milon https://milon.im

  2. Projects Maintained by me • CAAS • Castro • Doctor

    Appointment Booking • Tonic SMSC • Tonic App Backend • Tonic Admin
  3. CAAS

  4. CAAS - Technology Stack • PHP 7.1 • PostgreSQL •

    Laravel Framework 5.6 • Cache: Redis • File Storage: Amazon S3 • Testing: PHPUnit • Cron: Laravel scheduler with Crontab
  5. CAAS - Architecture

  6. Castro

  7. Castro - Technology Stack • PHP 7.1 • MariaDB (Migrated

    from MySQL) • Laravel Framework 5.5 • Queue: Redis • Cache: File • Testing: PHPUnit • Cron: Laravel Scheduler with Crontab • Process Controller: supervisord
  8. Castro - Architecture

  9. Appointment Booking

  10. Appointment Booking - Technology Stack • PHP 7.1 • PostgreSQL

    • Laravel Framework 5.6 • Cache: Redis • File Storage: Amazon S3 • Testing: PHPUnit
  11. Appointment Booking - Architecture

  12. Tonic SMSC

  13. Tonic SMSC - Technology Stack • PHP 5.5 • PostgreSQL

    • Lumen Framework 5.2 • Queue: Redis • Process Controller: supervisord • Testing: PHPUnit • Cron: Laravel scheduler with Crontab
  14. Tonic SMSC - Architecture

  15. Tonic App Backend

  16. Tonic App Backend - Technology Stack • PHP 7.1 •

    PostgreSQL • Laravel Framework 5.5 • Cache: Redis • File Storage: Amazon S3 • Push Notification: Pushwoosh(Deprecated), Firebase Cloud Messaging • Testing: PHPUnit
  17. Tonic App Backend - Architecture

  18. Tonic Admin

  19. Tonic Admin - Technology Stack • PHP 7.1 • Laravel

    Framework 5.1 • PostgreSQL • Queue: Redis • Cache: Redis • Testing: PHPUnit • Process Controller: supervisord
  20. Tonic Admin - Architecture

  21. ? Feel free to ask anything