strivitech / mu-hub-backend Goto Github PK

1. Include EF Core packages for the backend project.
2. Set up database with Postgres Provider.

Add functionality that allows user to add coins to watch list

Create a new validation service using FluentValidation to validate input DTOs in Application and Infrastructure layers.

1. Investigate if ELK stack suits our needs.
2. Add Serilog package.
3. Add appropriate ElasticSearch package.
4. Add ElasticSearch and Kibana to the docker-compose file.
5. Optionally, add Logstash.
6. Tune essential dependencies and provide logic for logging in application services.

• Provide basic communicating with Market Library
• Provide logic to store coins data to the database
• Create mapping ids for fetched data from Market Library when saving to the main database
• Create a hub that uses WebSocket protocol or SSE to send updated data in real time

Coins data includes:

• Coins, containing info about used coins in application such as ExternalSymbolId, SymbolId, Symbol, Name. It contains mapping ids, so she knows relationship between coins from the application and Market Library (ExternalSymbolId <-> SymbolId)
• MarketCoins, containing info that users should get using a hub such as SymbolId, Symbol, Name, ImageUrl, CurrentPrice,, MarketCapRank, High24H, Low24H, LastUpdated, IsValid
• MarketCoinsUpdateTimestamp, containing LastUpdated - time when MarketCoin data was updating last time

• Add a new service for interacting with Users, including creating, updating, deleting entities from the database.

• Add Jwt service for operating with tokens
• Add authentication service using the above-mentioned Jwt service

The task is to investigate and provide basic implementation with CoinGecko that allows to fetch some data. This task doesn't impose any optimization or performance requirements.

The result should satisfy following points:

• API endpoint that is used to fetch data by simple filter.
• Application service that gives an ability to use fetched data in other services later.
• Separate library containing all inside logic associated with a chosen library and market provider.
• Thus, the logic similar to this:
  API controller -> Application services -> Separate library with inside or low-level logic for the market provider -> Market provider's library.

Every user should be assigned to one role. Role contains one or more permissions.

1. Add roles and permissions to user model.
2. Provide mechanism that gives an ability to allow or forbid access according to permissions.

Additional info about JWT and permissions:

• JWT Access token and Identity token must include user role.
• Investigate pros/cons of both following appropriate approaches. JWT Access token and Identity token can contain compressed user permissions since the token lifetime will be small enough assumedly and changing roles are not planned. Alternatively, allowed to create fetching permissions by role on every API call from database + distributed cache (Redis is an example). The decision about the flow must be discussed and clarified later.

Add tests for testing all actions in Identity Provider.

• Add logic that encapsulates errors from services
• Add unified responses, containig errors for controllers according to RFC 7807

Add swagger and set up it to support API versioning.

Provide functionality to store Identity Users into the database. It must be only adding a database set of User models as IdentityUsers to the database context. There is no need to provide services for interacting with this model.