-
Notifications
You must be signed in to change notification settings - Fork 0
Software stack
Stephan Kulla edited this page Mar 8, 2023
·
2 revisions
On the one hand, we want to limit the “default” choices in order to
- enable knowledge sharing
- make transitions between projects easy
- retain productivity when involved developers change
On the other hand, we want developers to be able to pick the right tool for the job and don’t feel constrained in their technology choices.
Therefore, we came up with a list of default choices that should be used for new projects (taking the knowledge & interest of the current devs into account). If you want to deviate from that list, you should have valid reasons for that and discuss it with the software team.
- TypeScript
- Express as framework
- Apollo framework for GraphQL server
- Rust
- Python for data analysis and helper scripts -> maybe we will use it also for microservices
- TypeScript (React) / Next.JS
(SQL is the default choice, NoSQL / graph database only if there are valid reasons)
- Ideally PostgreSQL everywhere (currently only within the user management service)
- Currently still using an older version of MySQL with plans to slowly migrate away from
- Home
- Serlo Infrastructure
- Serlo Infrastructure for Non programmers
- Resources for new programmers
- Setup of the toolchain
- Best Practices
- Data Privacy for Devs
- How Tos
- Single Sign On
- Integration with the Data Wallet
- User-Journey: SSO and Data Wallet
- User-Journey: Collaboration with Serlo Editor + Datenraum
- Integration of "Datenraum" into the Serlo Editor
- Introduction to the Serlo editor
- Core concepts of the Serlo editor
- Packages of the Serlo editor
- Creating a new plugin (outdated)
- Redux process in the Serlo editor
- The content format of the Serlo editor
- Serlo Editor Plugin Initial State
- How the Serlo Editor is integrated into edu-sharing via LTI
- Learner Events and xAPI