Skip to content

Refactor api-server to use controller-service-repository architecture and rpc communication with backend #7459

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

Closed
1 task done
bisgaard-itis opened this issue Mar 31, 2025 · 3 comments
Assignees
Labels
t:maintenance Some planned maintenance work
Milestone

Comments

@bisgaard-itis
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Planned changes

This is a sub issue from ITISFoundation/osparc-issues#675

@pcrespov
Copy link
Member

pcrespov commented Apr 2, 2025

  • three layer design:
    • controllers api/routes --> api/rest
    • service
      • hide rpc/http clients below BaseService class
    • repository (only auth for now but prepare to deprecate)
    • clients
      • rabbit
      • postgress
    • models
      • domain
      • schemas
  • Guarantee atomic operations during aggregations
    • unit of work
  • Gateway (manage request load)
  • Privileges (e.g give priority to paying customers)

@pcrespov
Copy link
Member

image

@bisgaard-itis
Copy link
Contributor Author

Closing this as all subissues have been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:maintenance Some planned maintenance work
Projects
None yet
Development

No branches or pull requests

2 participants