e15a8042a1
* BREAKING: Make eduserver/appservice use userapi This is a breaking change because this PR restructures how the AS API tracks its position in Kafka streams. Previously, it used the account DB to store partition offsets. However, this is also being used by `clientapi` for the same purpose, which is bad (each component needs to store offsets independently or else you might lose messages across restarts). This PR changes this behaviour to now store partition offsets in the `appservice` database. This means that: - Upon restart, the `appservice` component will attempt to replay all room events from the beginning of time. - An additional table will be created in the appservice database, which in and of itself is backwards compatible. * Return ErrorConflict |
||
|---|---|---|
| .. | ||
| api | ||
| consumers | ||
| inthttp | ||
| query | ||
| storage | ||
| types | ||
| workers | ||
| README.md | ||
| appservice.go | ||
README.md
Application Service
This component interfaces with external Application Services. This includes any HTTP endpoints that application services call, as well as talking to any HTTP endpoints that application services provide themselves.
Consumers
This component consumes and filters events from the Roomserver Kafka stream, passing on any necessary events to subscribing application services.