Drasko DRASKOVIC comments

Results 127 comments of


Drasko DRASKOVIC

Switch to NATS 2.0

Related to https://github.com/mainflux/mainflux/issues/1068

NATS 2.0 does not look ready yet (JetStreams are not yet finished). [Liftbridge](https://github.com/liftbridge-io/liftbridge) is also and interesing in-pace replacement with streaming as an additional feature.

Enable reliable publishing of event messages to Redis Streams

@anovakovic01 @nmarcetic do you have any ideas how this can be implemented? I think this can be a `good-first-issue` if defined well.

Add message tracing over NATS using open tracing standard

Great! Thanks @nwneisen.

Add gRPC API to core Mainflux services

We should also consider using [gRPC Gateway](https://github.com/grpc-ecosystem/grpc-gateway), and providing HTTP REST API that way, rather than keeping current implementation once gRPC is in place.

Database design - add ID to the User entity and use it in Owner fields of other entities

@anovakovic01 @nmarcetic @dusanb94 @srados please comment on this.

Database design - add ID to the User entity and use it in Owner fields of other entities

@anovakovic01 my opinion is also that `ID` can be useful here. However - @saeidakbari and @nmarcetic ID we use is also a string - UUID. If I understood well @saeidakbari...

Database design - add ID to the User entity and use it in Owner fields of other entities

@saeidakbari I was talking about [UUID v4 which we use](https://github.com/satori/go.uuid#example) (which is a string), not Prostgres UUD.

Database design - add ID to the User entity and use it in Owner fields of other entities

@saeidakbari we do not want to dependent on a particular DB. This is why we use UUID v4 - which is a string.

Database design - add ID to the User entity and use it in Owner fields of other entities

@nmarcetic are we still for [adding ID](https://github.com/mainflux/mainflux/issues/739#issuecomment-531748354) to the `User{}` struct? If yes, we can add this to `0.12.0`