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

Move database-layer endpoints to API #1243

Closed
60 tasks done
Tracked by #323
AndreasHuber opened this issue Feb 1, 2024 · 1 comment
Closed
60 tasks done
Tracked by #323

Move database-layer endpoints to API #1243

AndreasHuber opened this issue Feb 1, 2024 · 1 comment
Labels
API dev experience Changes to the API gateway that will make feature implementation easier good first issue Good for newcomers refactoring

Comments

@AndreasHuber
Copy link
Contributor

AndreasHuber commented Feb 1, 2024

#1234 already provided the database access to the API gateway and as an example moved a first endpoint, UserSetDescriptionMutation, to the API gateway. Now the other endpoints can be moved in similar fashion. The goal of this is to reduce complexity, as the separation in different services with different programming languages has not added a lot of advantage.

See https://github.com/serlo/api.serlo.org/blob/staging/packages/server/src/model/database-layer.ts

@hugotiburtino
Copy link
Member

Completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API dev experience Changes to the API gateway that will make feature implementation easier good first issue Good for newcomers refactoring
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants