Backend on FastAPI with ~9 microservices

Good evening, Alexandr!
In general, the task is clear, but for an accurate response regarding deadlines and price, I would like to clarify some questions that arose after analyzing your task.
Please write in private messages — we will discuss the details and your wishes.

Show original

Translate

Hello,

I’m interested in your FastAPI backend project. The combination of a real commercial product, a well-planned architecture, and a flexible timeline makes this a very attractive opportunity for me.

I have experience building backend and full-stack applications, including APIs, database-driven systems, and structured application logic. I’m comfortable with FastAPI, CRUD-heavy services, integrations, and also giving extra attention to the more complex parts of the system such as business logic, testing, and debugging.

I also like that your architecture is based on DDD, Clean Architecture, and event-driven principles. I prefer working on projects where code quality, maintainability, and long-term scalability are important.

I can help build the backend in a clean and reliable way, keep communication clear, and move the project forward steadily based on the technical task and Figma designs.
…
I’d be glad to discuss the scope and next steps.

Best regards
Nikola

Section - days
Auth 3
Onboarding (with Flow Engine) 4
Abstract content system 60
Learning Services (LRS and packages) 12
Profiles and preferences 3
Gamification 18
Billing and tokens 10
Notifications 3
… Files (integration) 1
Search (low priority) 5
AI generation 15
Flow Engine 10
Automations 15
Additional modules (surveys, reports) 2
Hooks and admin panel 2
Infrastructure, tests, CI/CD 20
Total 183

Rate - $25. - day - 8 hours - $200

183 days * 200 = 36,600 for the project.
I would also add 10-14 days for the entire period - these are additional fun things that will come up (force majeure and various unaccounted items)
Feel free to reach out.

Show original

Translate

Hello

The project looks well thought out and interesting — especially the approach with DDD, Clean Architecture, and event-driven elements.

I have experience building backend systems with a similar approach: separation of domain, infrastructure, working with queues and events. I pay special attention to tests, debugging, and the resilience of integrations — I understand that this is a key part of the project.

I am ready to work at a comfortable pace, with immersion in architecture and business logic. I am particularly interested in it as a long-term commercial case with a release in stores.

I would be happy to discuss the details and format of collaboration.

Show original

Translate

Good day, this is the BeaverIT team. We are ready to take on the project; after reviewing the technical specifications, we can handle both the backend and the frontend parts. We already have experience in developing applications on microservices architecture: We developed an Ed platform from scratch for a startup on microservices architecture, and we also developed an e-shop from the ground up. If you are interested, we can take on your project.

Show original

Translate

Hello!

We and the team are ready to implement the project. The team has experienced developers, so we can create a convenient, modern, and functional product according to your requirements.

We will be able to determine the deadlines and budget accurately after discussing the details and understanding the full scope of work. I would appreciate your feedback; I can send examples of our work in private messages.

Show original

Translate

Good day, I would really like to take on the project, I have experience in this stack, and I use vibe coding very actively. It would be great for my portfolio. The project is quite large and the timeline will not be quick.

Show original

Translate

Hello Alexander!

I am a backend developer who has worked with the stack:
FastAPI, Redis (cache and sometimes rate limiter), Kafka (message broker), and used databases (PostgreSQL and MongoSQL - depending on the situation)

I would be interested in working with you and participating in such a project)

Show original

Translate

Good day.

I have reviewed the description — the approach with DDD, Clean Architecture, and event-driven logic is completely clear, I have experience building similar systems.

With such projects, the main difficulty is indeed not in CRUD, but in proper design, separation of responsibilities, and stable operation of more complex modules.

I am a Full-Stack developer, so I can implement both frontend and backend. I design architecture, write clean and scalable code, and also bring projects to stable production (tests, debugging, integrations).

I would be happy to discuss all the details of the project in private messages, including price and deadlines.

Show original

Translate

I see you need a FastAPI dev to build a backend based on a senior-designed DDD and Clean Architecture. Transitioning from the Figma mockups to a functional microservice ecosystem is clear, especially focusing on the CRUD operations and the specific quiz generation logic. I appreciate the emphasis on technical depth and testing, as maintaining an event-driven system with nine services requires a solid foundation from the start.
My background involves building scalable Python backends using FastAPI and implementing Domain-Driven Design patterns to keep business logic isolated. I am comfortable with event-driven elements and ensuring each microservice remains decoupled. To give you an idea, here is a rough sketch of how I approach the application layer:
class CreateQuizUseCase:
def execute(self, cmd: CreateQuizCommand) -> Quiz:
domainlogic.validatedifficulty(cmd.level)
return self.repository.save(Quiz.from_command(cmd))
Since this is a personal project with a flexible timeline, I can focus on the quality expected for a commercial release. I will follow your technical docs strictly to ensure the code stays maintainable for the final Google Play and iOS launch.

Looking forward to discussing your project in detail.

Good day!

I have reviewed the technical specifications. As I understand, almost all of the system code is written, and we need to develop the business logic. However, I would like to know a bit more about the technologies used in the project: what backend stack is being used, what has already been chosen for the database, authentication, etc.
I am also interested in vibe coding :) I exclusively use AI for machine work.
Examples of backend work where I wrote everything from scratch.

https://rstays.com/

https://ai-desk.ai/
…
Also GitHub:
https://github.com/axbuglak

Write to me, we will discuss everything.

Sincerely,
Buglak Alexey

Show original

Translate

Hello! I can implement it. Write to me privately to discuss all the details. I will be glad to cooperate!

Show original

Translate

Hello! 🚀

I have reviewed the description: the task format is clear — a mobile/web project with Figma as the main source of requirements, CRUD endpoints, a separate block of complex logic for quiz generation, and architecture in the style of DDD / Clean Architecture. This format suits me: I can neatly implement both standard modules and more complex parts with business logic, tests, and integrations.

Technology stack used:

Backend: Python (FastAPI) PostgreSQL
Integrations: REST API, quiz generation, auth, tests, event-driven approaches
Frontend: React / React Native / TypeScript, implementation according to Figma
… Infrastructure: Docker, CI/CD, logging, testing

I am ready to discuss the project details in person and am ready to start working.

Best regards, Andriy

Show original

Translate

Hello!

The Dev Company team is interested in joining this project and implementing the backend according to your technical specifications and API draft, relying on the Figma mockups as the primary source of truth for the product.

We understand that:
- the main part of the endpoints is predictable CRUD for the content system entities and user data;
- the complexity lies not so much in the endpoints themselves, but in the architecture, consistency of layers, tests, and integration (especially xAPI, abstract content system, learning state, flow engine, automations, AI generation);
- careful implementation of DDD / Clean Architecture with elements of event-driven design is important so that the project can be easily developed rather than rewritten in six months.

… Our stack and experience align well with the task:
- we write production backends in TypeScript/Node.js (NestJS), Python, Postgres, event-driven (Kafka/RabbitMQ/Webhooks), and microservices architecture;
- we have built SaaS platforms with flexible content schemas, token billing, AI services (generation, explain/summarize/translate), as well as complex API layers with public/internal separation;
- we are familiar with DDD approaches, modular monoliths, and clean layered architecture.

How we will approach the work:
- we take the Figma mockups as the main product reference (UX, flow, states), and this API document as a technical guide for entities, fields, and edge cases;
- we carefully design the boundaries of modules (auth, content/meta, entries, learning/xAPI layer, flow engine, automations, billing/tokens, AI services) so that future features (gamification, search, feed, etc.) can be integrated without breaking;
- we use **vib-coding / AI assistants only as auxiliary tools (drafts, generation of standard CRUD, boilerplate tests), while key aspects — architecture, complex scenarios, debugging, integrations — are handled manually and through tests;
- from the very beginning, we lay down proper automated tests and regression checks so that the system can be safely developed over months.

We like that this is not a "one-time mini-task," but a living startup with soft deadlines and a focus on quality architecture — this significantly increases the value of the case in the portfolio and allows for careful, rather than rushed, development.

We are ready to discuss:
- what stack you plan for the backend (Node/Nest, Python/FastAPI, Go, etc.);
- priority modules for the first release (auth + content + learning state + basic AI, for example);
- work format and phased payment.

Show original

Translate

Hello!

I am very interested in your project, as I specialize in Python and am deeply immersed in studying software engineering. Your stack (FastAPI, DDD, Clean Architecture) is exactly the direction in which I am developing, and I am ready to devote maximum attention to quality design and tests that you mentioned in the project brief.

Show original

Translate

Hello. I can do your project. I have experience. Write to me, and we will agree.

Show original

Translate

Hello.

I am a NodeJS developer. I am ready to take on the task. Write to me, we will discuss.

Show original

Translate

Good day. I am ready to complete this project and have extensive experience in developing various applications.

Show original

Translate

Hello! I will complete your task quickly and efficiently.

My portfolio: https://freelancehunt.com/ua/freelancer/romas6ka.html#portfolio
Write to me, I will start working today. I will be happy to collaborate with you!

Show original

Translate

Hello
I am ready to complete your work
Write to me, I will be happy to carry out the project efficiently and on time

Write to me, I am ready to start

Show original

Translate

Hello. I work with Fast API. I am ready to help with the backend. Feel free to contact me.

Show original

Translate

Hello.

I have processed the documents and Figma. Together they show that this is a mobile-first learning product, where the backend should not just provide CRUD, but manage learning states, progress, subscriptions, tokens, dashboard logic, and admin settings. From Figma, it is clear that the foundation of the project is better built as a backend-driven system with clear contracts, because what matters are not individual screens, but the onboarding, progress, and completion scenarios.

I can take the first priority within the current budget as a technical foundation:
- FastAPI skeleton according to your architecture;
- PostgreSQL, settings, DI, structured logging;
- versioned API /api/v1;
- one end-to-end CRUD service;
… - basic tests;
- preparation of contracts and structure for the next microservices.

This will provide a clean foundation that can be further expanded without restructuring. If needed, we can separately go step by step through Auth/User, Content, Learning, or Subscriptions.

Please let me know which service is a priority for you in the first iteration.
We can continue the discussion in a language convenient for you (Ukrainian, Russian, English).

Show original

Translate

Hello.
I looked at the materials in the open folder FastAPI DEV/README, Educational App PRODUCTION - CLEAN, and Common best practices.
From the description, I see that your project is not about just throwing together CRUD, but about a proper backend assembly with a well-thought-out architecture, service boundaries, tests, validation, logging, and further scalability. This is exactly the format where the careful construction of the foundation is more important than the speed of the draft.
A separate plus is that the heaviest parts have already been removed from the current scope: quiz generation, file upload, and gamification. In this composition, the task looks realistic and can be approached sequentially: Auth / User, Content, Learning, Tokens / AI usage, Subscriptions, Automations, Flow engine, Notifications, Dashboard.
From my side, I would approach this not as 9 microservices for the sake of microservices, but as a working backend framework for a real product with proper decomposition, clean architecture, async-first approach, dependency injection, API contracts, and clear deployment.
I work with backend logic, APIs, Telegram/web/mobile integrations, and projects where it is important not just to assemble an interface, but to create a working product that can then be maintained and developed.
GitHub: https://github.com/vitalivo
It is optimal to proceed step by step here: first, build the basic core and infrastructure layer, fix the service contracts and general API rules, and only after that calmly expand the other domains without chaos and unnecessary refactoring along the way.
I am ready to take this on.

Show original

Translate

Is the implementation of the backend being considered on a different stack? I can do it on ASP.NET Core. For event-driven / less coupling, you can use the MediatR library - the endpoints will be as thin, lightweight, and clean as possible - usually, this is just sending an event, where there will be a corresponding handler for that event + it isolates components, which simplifies, for example, testing. Logging with Serilog. I don't want to praise ASP.NET Core, but in terms of performance, it outperforms FastAPI; you can look for independent benchmark tests.

Show original

Translate

Good day. I can write in Go language. It will work quickly and efficiently. I will do it quickly and efficiently. I have written complex APIs (for example, for an application like Telegram).
P.S. Do not pay attention to the negative review, it was a misunderstanding. I understand everything very well.

Show original

Translate

Good day, Alexander. I am interested in collaborating with you. If it is still relevant, I would be happy to participate in the project.

Show original

Translate

Subject: Backend Developer FastAPI — ~9 Microservices for Educational Application (Coding Train APP)
Good day!
My name is Vova, I am a backend developer with experience in FastAPI and building microservice architecture. I have commercial experience with Clean Architecture, DDD, and event-driven approaches.
I am ready to take on your project — the development of the backend with ~9 microservices for a mobile educational application.
Here is how I plan to approach the task:

I will thoroughly study the technical specifications, README, Figma layouts, and recommendations from the documents.
I will design the architecture of the microservices considering Clean Architecture and DDD.
I will implement the main part — CRUD endpoints (the majority of them).
… I will separately work on complex logic (quiz generation and related edge cases).
I will write unit + integration tests, ensure quality debugging and integration between services.
I will prepare everything for further release on Google Play and the App Store.

I understand that the project is real, commercial, with a well-thought-out stack and soft deadlines (a few months). This allows for quality work without haste.
I am ready to start working in the near future.
I would be happy to discuss the details, answer questions, or show examples of previous projects.

Show original

Translate

Hello. I am interested in your project. I work with Python/FastAPI, designing backend with clean architecture, proper domain decomposition, CRUD logic, integrations, and complex business processes. From your description, I see that the main part is a clear API layer and working with the database, and the key focus should be on design, quiz generation, tests, and system stability. I can carefully implement the backend for such a project:
— FastAPI
— PostgreSQL
— microservice/module approach
— clean architecture
— API documentation
— testing and phased delivery

Show original

Translate