Versions Compared

Version Old Version 30 New Version 31
Changes made by

Nico

Nico

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Microservice nameCodeResponsibleDiscussAPIDescription
Micro service example (and node version)EXAMPLE
Confluence - Development

An example module.

Responsibilities and functionalities:

  • Make the development of a new micro service easier.
    • Core registration example
    • Frontend display example
    • Retrieve core data example
CoreCOREDerk, NicoConfluenceAPI

The core module providing the very basics required for all other modules.

Responsibilities and functionalities:

  • General
      • Providing Single Sign-On (SSO) for all (new and existing) AEGEE online services using oAuth
      • Endpoint for attaching new microservices and comunicating with them via secure key
      • "Fault Tolerance": Internal monitoring of the connected microservices and admin notification in case of connection problems.
  • General frontend
    • Render general frontend
    • Render other modules' frontends
      • Using templates and corss-site requests
  • Managing microservices connected to OMS
    • Enable and disable microservices
    • Module management
      • Enable and disable modules
  • Member management
    • Differentiate between member type: member, suspended, applicant
      • Offer an (member)application method
    • List, add, edit, suspend and group members
    • List, add, edit and delete groups (bodies)
    • Define permission roles
    • Assign roles to members and groups
  • Logging ability for microservices communication as a bug finding capability
Events (and frontend)EVENTSNico, SergeyConfluenceAPI

All event-related stuff. Creating, modifying, displaying and deleting events, approving events, managing events' organizers

Responsibilities and functionalities:

  • Managing events
    • Creating, listing, updating and deleting events
  • Managing lifecycles and events workflow
    • Creating, listing, updating and deleting lifecycles
    • Events lifecycle workflow (assigning a default event status, changing the event status)
  • Managing organizers
    • Adding and removing organizing persons and antennae
Applications (and frontend)
NicoJIRA - Issue

Everything related to the events' applications for the generic events (not statutory and not SU). Applying for the events, managing applications, approving participants.

Responsibilities and functionalities:

  • Managing the generic application process
    • Events application process
    • Participation listing
    • Participants selection by the organizers
    • Participants' evaluation for the event
    • Application comments by the organizers
Service registryREGISTRYNicoJIRAAPI

Helps with service discovery based on categories or servicenames and provides an access token registry.

Responsibilities and functionalities:

  • Provide a JSON interface to the current service setup
    • Get services by name or category
  • Register auth token for internal communication
    • Register and verify auth tokens
AlastairFOODNicoConfluence

Food planning module - A private project from Nico

LDAP support

JIRA - Issue

Notifications - pipeN-PIPE
JIRA - Issue
Would allow observers to register and push and receive notifications.
Notifications - emailN-EMAIL


Emailer: Most likely will not write something ourselves, should use something existing. Flaviu mainly used sendgrid

Notifications - pushN-PUSH


Push Notifications

Cron Module

JIRA - issue
Regularily reoccuring tasks
Statutory microservice



Application procedure for the statutory events and stuff that happens during statutory events (agorae, epms): Agenda, Proposals and voting on proposals, members, etc. - Not parts of events module
Voting



Candidatures, Evaluation (like impact measurement for events), also Recursion (-;
Reporting



Generate anonymous reports with user and member statistics.
Finance



Fee management. Event budgeting. Parts of this are inside the core module at the moment, will be moved out of oms-core for this.
Storage



A possibility to backup data to external systems easily.
Travel



for example: AEGEE-couchsurfing
Gamification



E.g. create badges like "Visited 5 events" or "Attended 3 Agorae in a row"
Comments



Make commenting everything possible. Reuse of disqus might be the way to do it.
SU Webfrontend



Summer University Website: Will be a little different from the usual events frontend, maintained and developed by SUCT.

...