Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement CRUD operations for Currencys using FastAPI #1

Open
davidsonsalinas opened this issue May 1, 2024 · 0 comments
Open

Implement CRUD operations for Currencys using FastAPI #1

davidsonsalinas opened this issue May 1, 2024 · 0 comments

Comments

@davidsonsalinas
Copy link
Owner

Hi there,

I'd like to propose adding CRUD (Create, Read, Update, Delete) functionalities for [Data Entity] (e.g., currencies, quotes, historical data) to the project using FastAPI. This will allow for a more flexible and efficient way to manage data within the application.

Project Details:

Project Name: Async Currency Tracker
Description: This project utilizes Docker Compose, Arq, Beanie, and MongoDB to capture and store currency data asynchronously.
Proposed Implementation:

Leverage FastAPI for building a RESTful API with CRUD endpoints.
Use Pydantic models for data validation and serialization.
Integrate with the existing MongoDB database (potentially using Beanie or a similar ORM).
Consider security aspects (authentication, authorization) if necessary.
Benefits:

Improved data management capabilities with Create, Read, Update, and Delete operations.
Clearer API definition for interacting with currency data.
Potential for better maintainability and scalability.
Discussion Points:

Are there specific requirements for the CRUD endpoints? (e.g., pagination, filtering)
Should the existing structure of data models be adapted for FastAPI?
How can we ensure proper error handling and logging within the API endpoints?
Additional Notes:

I've reviewed the project structure, including:
Docker configuration (docker-compose.yml, Dockerfile)
Dependency management (requirements.txt or poetry)
Source code organization (src/, configs/, jobs/)
Installation instructions
I'm open to further discussion and collaboration on this feature. Feel free to share any thoughts or questions you might have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant