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

Application Architecture #3

Open
pozsa opened this issue Nov 9, 2021 · 2 comments
Open

Application Architecture #3

pozsa opened this issue Nov 9, 2021 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@pozsa
Copy link
Member

pozsa commented Nov 9, 2021

This issue is meant to document our initial decisions regarding the architecture of the application.

Auth related:

  • external OIDC auth service to be used
  • backend receives and does authn and authz based on JWT tokens
  • apps are configured with accepted OIDC service providers via env vars
  • web frontend to use auth code + pkce grant flow (all endpoints implemented on the frontend)
  • sdk frontend to use resource owner password credentials grant flow
@pozsa
Copy link
Member Author

pozsa commented Nov 15, 2021

Are we all in agreement that we go for separate frontend and backend from the get-go? (i.e. minimal server-side rendering if any)
Do we want an SPA (single page application)?

I wouldn't break down the backend into smaller microservices. Authn and authz are already separate components which is good. I think the rest we can keep as a monolith. Any thoughts on this?

@pozsa pozsa added the question Further information is requested label Nov 15, 2021
@sbliven
Copy link
Member

sbliven commented Nov 16, 2021

Agree with single backend service (I'm not sure we'll have enough endpoints to qualify as a 'monolith')

I think SPA is a bad design, both for development and for users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants