Architecture guide

The Hikma Health platform is built from the ground up to support offline conditions first through a robust local first approach to data.

Offline Native

Under the hood, SQLite powers the offline first approach allowing for highly performant local queries and mutations that can get synced with the server whenever the user has network availability.

With this architecture, the server is responsible for conflict resolution, and determining what changes each client needs to have during a sync event. To learn more about offline sync refer to this documentation

Deployment Considerations

To keep overall costs low, it is recommended to deploy on a serverless service on any of your favorite cloud hosting providers. There are many options including:

• AWS Lambda
• Google Cloud Functions
• Google Cloud Run
• Digital Ocean Functions
• Render
• Railway App
• Azure functions

... and more ...

Whichever provider you choose to go with, it is HIGHLY recommended to deploy all your solutions to the same provider to reduce the need for multiple logins and authentication processes.

Important: Make sure that whichever "region" or "location" that you choose for our server, you should select the same (or as close to it as possible) for your database. This will reduce the time it takes for the server to communicate with the database (latency).