Magister web version – backend development & integration

As a backend Systems Developer I contributed to the new web‑based version of Magister. Magister is used by over 80% of secondary schools for student information systems (tests, assignments, etc.), calendars, digital learning materials, and insight for teachers and parents.

We delivered REST services for communication with databases and external parties. Development was done in C#/.NET following Domain‑Driven Design (DDD), and SQL was used for data extraction and mutations. After a team reorganisation I joined the team that built generic functionality for other teams (the “back‑backend”), including integrations with external parties. We implemented applications to import test results and propagate them into the correct customer databases.

RabbitMQ was used for messaging and decoupling; Magister modules exposed their functionality via microservices. Software architects set the direction; the designs were worked out into detailed, production‑ready implementations by the developers.