I'll build the backend for your product as an ASP.NET Core API on PostgreSQL: the data model, auth, the endpoints your front end or mobile app needs, and OpenAPI docs so whoever builds the client isn't guessing.
I keep it as one well structured service unless there's a real reason to split it, with tests on the parts that handle money or permissions, migrations that run on deploy, and a CI pipeline that builds a container and ships it to your server.
Recent ones: a vehicle marketplace with listings, uploads and phone OTP login, and a task dispatch system that sends jobs to workers on WhatsApp. Send me what the app needs to do and I'll come back with how I'd structure it and what it costs.
I'll build the backend for your product as an ASP.NET Core API on PostgreSQL: the data model, auth, the endpoints your front end or mobile app needs, and OpenAPI docs so whoever builds the client isn't guessing.
I keep it as one well structured service unless there's a real reason to split it, with tests on the parts that handle money or permissions, migrations that run on deploy, and a CI pipeline that builds a container and ships it to your server.
Recent ones: a vehicle marketplace with listings, uploads and phone OTP login, and a task dispatch system that sends jobs to workers on WhatsApp. Send me what the app needs to do and I'll come back with how I'd structure it and what it costs.