Evaluating bids

Api Gateway + Auth/User/Profile Microservice (Nestjs, Kafka, Elasticsearch and Postgres)

Published on the July 07, 2024 in IT & Programming

About this project

Open

I need an "api-gateway" that handles requests from my "clients" and forwards them to the microservices via kafka, in addition to the auth/user/profile microservices, for my mvp ticketing system. It should be production-ready, have documentation, error handling, tests, JWT and oAuth (Google/Facebook/Twitter), it should also be scalable and easy to maintain, deliveries should be made via Github in a private repository, it should follow good code practices, clean and readable code, following some standard, in addition, commits should be accurate and not polluted, commits should follow the "Conventional Commits" standard and branches should also follow a standard, please use PRs and include a description in them, important: also use branch staging.

Any suggestions for implementation, modifications or ideas are welcome!

You should use at least (negotiable): NestJS, some ORM (I prefer Prisma), Kafka, Postgres, Elasticsearch.

API Gateway (must be capable at least):
It should receive requests from different clients (Desktop/Mobile/PoS App).
It should communicate with the other microservices via Kafka.
It should have a cache.
It should check user authentication/verification (and trigger the auth service if necessary).
And so on.

Auth Service (Must be capable at least):
Should handle all user authentication and authorization.
It should handle user roles and future organizations. (To be implemented)
It should create/renew/suspend JWT tokens.
Manage the renewal of JWT tokens.
Create specific short-lived tokens for sensitive operations.
Maintain an audit log of sessions.
Must follow security standards.
And so on.
(Can be traded for a service such as Keycloak, for example)

User/Profile Service (Must be capable at least):
Should be able to handle user-related CRUDs.
It should have /me (like) and the like.
It should handle the user's Profile.
And so on.

The user's personal information, such as: name, addresses, phone numbers, photo, etc., Will be stored in the User Profile, while system information, such as: email, password, etc., Should be stored in the User.

Note: Users can own (or be part of) one (or more) organization(s), for context, organizations are event producers, who can register events and sell tickets and so on, so the User/Profile Service should be built in a way that anticipates the future implementation of organizations.

These are the basic requirements (which can be negotiated), the rest is up to the developer.

Project name: Rolêzim.

Project overview

I need an "api-gateway" that handles requests from my "clients" and forwards them to the microservices via kafka, in addition to the auth/user/profile microservices, for my mvp ticketing system. It should be production-ready, have documentation, error handling, tests, JWT and oAuth (Google/Facebook/Twitter), it should also be scalable and easy to maintain, deliveries should be made via Github in a private repository, it should follow good code practices, clean and readable code, following some standard, in addition, commits should be accurate and not polluted, commits should follow the "Conventional Commits" standard and branches should also follow a standard, please use PRs and include a description in them, important: also use branch staging. Any suggestions for implementation, modifications or ideas are welcome! You should use at least (negotiable): NestJS, some ORM (I prefer Prisma), Kafka, Postgres, Elasticsearch. API Gateway (must be capable at least): It should receive requests from different clients (Desktop/Mobile/PoS App). It should communicate with the other microservices via Kafka. It should have a cache. It should check user authentication/verification (and trigger the auth service if necessary). And so on. Auth Service (Must be capable at least): Should handle all user authentication and authorization. It should handle user roles and future organizations. (To be implemented) It should create/renew/suspend JWT tokens. Manage the renewal of JWT tokens. Create specific short-lived tokens for sensitive operations. Maintain an audit log of sessions. Must follow security standards. And so on. (Can be traded for a service such as Keycloak, for example) User/Profile Service (Must be capable at least): Should be able to handle user-related CRUDs. It should have /me (like) and the like. It should handle the user's Profile. And so on. The user's personal information, such as: name, addresses, phone numbers, photo, etc., Will be stored in the User Profile, while system information, such as: email, password, etc., Should be stored in the User. Note: Users can own (or be part of) one (or more) organization(s), for context, organizations are event producers, who can register events and sell tickets and so on, so the User/Profile Service should be built in a way that anticipates the future implementation of organizations. These are the basic requirements (which can be negotiated), the rest is up to the developer. Project name: Rolêzim.

Category IT & Programming
Subcategory Web development
What is the scope of the project? Create a new custom site
Is this a project or a position? Project
I currently have I have an idea
Required availability As needed
API Integrations Social media (Facebook, Twitter, etc.)
Roles needed Developer

Delivery term: Not specified

Skills needed

Node.js PostgresSQL Elasticsearch Microservices Typescript REST API Nest.js

Want to start working on this project?

Log into your Workana account or Register today. Boost your freelance work!

Other projects posted by A. N.