{{ __('Matching via server') }}: {{ __('The server fetches order ready for assignment, also fetch nearby driver base on order location, then notify each paired driver about new order. All from the server') }}

{{ __('Fewer read/write to firebase firestore. Less/No extra billing cost on firebase.') }}

{{ __('Sometimes the order alert can take a bit longer to deliver to the driver device.') }}

{{ __('On Driver Device') }}: {{ __('The server fetch order ready for assignment and push it to firestore, then each driver device will fetch the order and check if they are within range to handle the order') }}

{{ __('Driver alert order is store on the firestore for the driver app to read from. Its faster in most cases') }}

{{ __('Sometimes not accurate. Addes to a lot of firebase read and write, making your billing go up depending on the volume of orders') }}

{{ __('Server Fetch API') }}: {{ __('Direct try fetch nearby drivers from firestore from the server via api') }}

{{ __('No need for uploading firebase functions. No extra billing cost on firebase.') }}

{{ __('Might not always be accurate. Need to create extra indexes, check the firebase section in the project documentation for the needed firebase indexes') }}

{{ __('Firebase Cloud Function') }}: {{ __('Fecth driver via the firebase functions.') }}

{{ __('Addes to a lot of firebase read and write, making your billing go up depending on the volume of orders') }}

{{ __('Websoket') }}: {{ __('On Server Websocket') }}

{{ __('Self-hosted & Scalable:') }} {{ __('No external vendor lock-in; you control scaling and infrastructure.') }}
{{ __('Low Latency:') }} {{ __('Real-time messaging with minimal delay') }}
{{ __('Cheaper:') }} {{ __('There is no price on number of read and writes') }}

{{ __('More DevOps Overhead:') }} {{ __('Requires managing your own WebSocket server (Reverb,SSL, scaling).') }}
{{ __('No Offline Sync:') }} {{ __("Missed events aren't retained") }}