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
I recently completed a .NET 8 Backend API designed for a fictional ERP system. My goal was to go beyond just writing "working code" and build a highly scalable architecture using real-world enterprise design patterns. 🚀
⚡ The most critical aspect of this build is the fully asynchronous architecture. From database queries to AOP interceptors, the entire system is non-blocking (async/await) to maximize performance and scalability.
*Key Technical Highlights:
*Clean Architecture (N-Tier)
*Asynchronous Generic Repository Pattern
*Aspect-Oriented Programming (AOP) for cross-cutting concerns (Caching, Logging)
You can check out the architectural diagrams and technical details in my portfolio. 👇
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
🚀 “From Food Delivery App to ERP Integration”
What if your mobile app could talk directly to your ERP?
That’s what I’m building with Darakai.
Darakai is a food-delivery platform designed around a real business workflow—not just a UI prototype.
The interesting part?
🔗 Darakai can connect with SAP Business One.
The architecture is designed to connect:
📱 Customer App → Orders
🏪 Restaurant App → Menu & Operations
🚴 Driver App → Delivery
⚙️ Darakai API → Business Logic
🗄️ Database → Operational Data
🔵 SAP Business One → ERP & Business Operations
This opens the door to synchronizing things such as:
• Sales Orders
• Customers
• Products & Inventory
• Business data
• Reporting & analytics
• Order workflows
My experience with SAP Business One + SQL + APIs + .NET + Flutter allows me to work across both sides:
Modern product development ↔ Enterprise systems
That’s the kind of engineering I enjoy most—connecting different systems and turning them into one working product.
My goal with Darakai is to build the platform for a real food business first, then create the architecture needed to scale into a larger marketplace.
Build → Integrate → Scale.
If you're building a product that needs mobile apps, APIs, ERP integration, or a complete business platform, I'd love to connect.
#SAPBusinessOne #SAPB1 #Flutter #DotNet #React #APIs #FullStackDeveloper #SoftwareEngineering #ERP #ProductDevelopment #Contra
Building a platform that covers scheduling, customer records, communication, and appointment booking means designing across very different use cases. The risk is that each use case starts pulling in its own direction and the product ends up feeling fragmented.
We established a consistent way to use components early and applied it at two levels.
1/ At the page level, consistent text sizes and layout logic.
2/ At the component level, the interaction patterns show whether you are filtering technicians, service types, or job durations.
The result is a system where you don't need many text sizes, components, or colors because everything follows a coherent logic.
The filter panel is one example of that direction.
I’m a Senior Software Engineer with 10+ years of experience building backend systems, APIs, microservices, and integrations using Java and Kotlin.
I’m especially good at understanding complex systems, troubleshooting APIs, finding bugs, and turning requirements into working solutions. I also use AI-assisted development and advanced prompting to accelerate coding, debugging, testing, and problem-solving while keeping the technical quality under control.
I’m open to project-based and part-time work, particularly backend development, API integrations, API testing, automation, AI-assisted development, and AI/LLM evaluation.
I enjoy taking a problem, figuring out the best solution, and delivering something that actually works.
