The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Just finished OrderFlow: an event-driven microservices system built with .NET 9, RabbitMQ and SQL Server.
Orders and inventory run as independent services that talk through events, so a failure in one doesn’t take down the other.
Open to .NET backend projects: APIs, integration and microservices.
rabbitmqmicroservices.NETBackend DevelopmentDot Net Backend DevelopmentSoftware DevelopmentDockerMicrosoft SQL Server
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Crenaly: a booking SaaS I designed and built end-to-end for appointment-based businesses in France: salons, barbers, beauty and wellness.
The core idea: when a client cancels, the freed slot is automatically offered to clients who asked for an earlier time. The first to accept gets it, their appointment moves in place, and the slot they leave is offered next. No double booking, no manual work.
Around it, a full product:
→ Branded booking page for each business, embeddable on their own site
→ Mobile-first booking flow, no account needed
→ Agenda, client management, team roles & permissions
→ Verified reviews, analytics, Stripe billing
Product, UX/UI, frontend and backend.
Next.js · TypeScript · NestJS · PostgreSQL · Redis
Automatically offering a cancelled slot to the next client is such a practical feature for salons and barbers. Designing and building Crenaly end to end must have made those flows much tighter.
B&R Order Extractor: purchase orders turned into production-ready order lines. B&R Products commissioned me to cut the time it takes to turn customer purchase orders into something the factory floor can use. What we created: an order extractor that reads PDFs and photos, pulls out every order line, and lets the operator check and fix each field before export. What we did: built the upload and extraction flow; made customer, order number, description, quantity, tinting and comments editable; set up a daily batch queue with numbered exports for traceability; added picker names and ordered versus invoiced quantities; built the spreadsheet export for store, dispatch and invoicing; built the tinting list; managed the backend database that archives every order and batch with duplicate protection. Live and used by the team.
Your point about needing reminders to review before dispatch suggests a useful regression case: approve an order, then change its quantity or tinting before export. The old approval should no longer cover that changed version. One approach is to tie approval to an order revision...