branchtalk-io / backend Goto Github PK

• add metadata to Session model
• when creating Session store what is known about the creator: IP, operating system, browser, etd
• list that data to User so that it could remotely sign-out out

• design functionality
• implement domain logic
• it-tests
• API

In Program

Calculation and handling of permissions should be done inside Users domain.

• make User.Email an ADT - New, Confirmed, Updated
• create reads/writes to enable email update and confirmation
• expose this functionality via endpoints
• it-test it

In PostgresDatabase or DoobieSupport

• add UrlTitle length limit to configs
• pass config into services
• make sure that data respects that

• require request ID in request which modify state
• store IDs of received requests in some cache for some time
• return calculated value instead of processing request again
• apply this only to commands - queries should be not be cached
• apply this logic after authentication to make all changes in permissions reflected

• configure groupID for each subscriber
• log it
• make batch commiting configurable

• store IDs of events that were processed successfully
• filter out events which have IDs on processed events list
• use this logic to make sure that events are idempotent even if offset is commited every once in a while
• separate Command -> F[Event] translation from Event -> F[Unit] projection, to make events replayable

If User is not logged in, some subscriptions should be used instead.

• create a config
• pass it into domain and respect it
• test changes
• update PostServer

See https://blog.softwaremill.com/correlation-ids-in-scala-using-monix-3aa11783db81 and https://olegpy.com/better-logging-monix-1/ for inspirations.

• add timestamps (created/modified) to APIPost and update all relevant pieces of code

• design how controversial topics could be recognized
• implement domain logic
• expose it via API
• test it

• add CORS handling (there is a HTTP4s middleware for it) in AppServer
• add Prometheus instrumentation (there is a HTTP4s middleware for it) in AppServer
• create special HTTP thread pool Resource for BlazeServer in Program

• make default algorith configurable
• make bcrypt cost configurable
• wire and and changes

Implement Jsoniter codecs for: NonEmptyList, NonEmptyChain and other used structures that aren't supported out of the box - right now they are handled as ADTs which is wrong.

Implement it in io.branchtalk.api.

• implement logging JSONs to e.g. elasticsearch
• expose methics e.g. by prometheus
• add elasticsearch and kibana and graphana to docker-compose

• pick the right tool for the job
• project events into database (if other than Postgres)
• implement domain logic
• it-test
• API

• coments table needs to store channelID so that it would be possible to partition all: channels, posts and comments by channelIDs.

Log each access by user

• subscribe to events
• send notifications to a websocket in real time
• store notifications until marked as read by user

• better readme
• design decisions
• how to build, run, use

• design how hot topics could be recognized
• implement domain logic
• expose it via API
• test it

• create a new table to track who voted and who didn't - consider looking at other databases as well if that would make it easier and faster
• create reads, writes and events
• it-test side-effects

In UUIDGenerator implementation