Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geartrack v2 Architecture #29

Open
carlosflorencio opened this issue Jun 26, 2017 · 2 comments
Open

Geartrack v2 Architecture #29

carlosflorencio opened this issue Jun 26, 2017 · 2 comments

Comments

@carlosflorencio
Copy link
Member

Need opinions about the achitecture of the next version of Geartrack which will have authentication and notifications.

architecture

Concerns:

  • Should we add auth to the tracker api to prevent other apps to depend on us? (bandwidth can be expensive)
@fabiocatalao
Copy link

Which type of notifications are you thinking to handle with the Service API?
From what I'm understanding it will not be connected with the Tracker API and all the tracking updates will be requested by the Client APP, right?

@carlosflorencio
Copy link
Member Author

There is a missing call from the Service API to the Tracker API to handle the notifications, this job will be scheduled in every x hours (and maybe divided into chunks).

The notifications will have multiple implementations, the first to be implemented will be email. When the mobile apps are ready we will add push notifications too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants