Distributed-eStore VS craftsman

After about a month of development in my free time, this is my result: https://github.com/evgenirusev/Distributed-eStore

There’s some stuff I’d tweak on this project but it has some more advanced concepts you can check out. If you want to play around with something similar (several updates since this project) and get past the boilerplate you can check out this project.

If you’re having trouble getting started backend wise, I made a tool that can scaffold some boilerplate for you. You can also check out projects like Jason or ardalis’s clean architecture projects. Here’s one that’s a little dated but still good.

If you’re interested, something like this is a more built out project I built a while back. It’s not done and I’d change several things looking back, but it gives you an idea. If you want to try something similar you can scaffold out an api with this tool, but there are other good projects you can reference as well!

If you’re interested, I made a tool that scaffolds out an API for you. Saves us a lot of time at work and sets up a lot of the boilerplate for you. You can also customize it for yourself with whatever changes you want.

And here’s a project scaffolding tool

I’ve been building out an OSS tool that scaffolds web api boilerplate for about two years now and I’ve learned a lot throughout the process. I wanted to take an opportunity to really dog food a DDD like flow with it and came up with the sandbox project for an Accessioning model within a LIMS (essentially intake for lab orders) since I have some background there.

Lots of resources out there. You can scaffold a vertically sliced ddd project with this tool. Here’s a slightly modded example from what it produces.

About 2 years ago now, I decided to take my .NET template project a bit further and made a code scaffolding tool called Craftsman. The idea is that I can write a simple description of my project using yaml or json and get all the boilerplate set up for me so I could jump right into business logic. These files aren't a source of truth, just a description to get things started. It's getting closer to a stable v1, but it's not there yet.

I don’t think there’s one singular right way to make it good. Personally, I’ve found vertical slice architecture and DDD to encourage a very maintainable codebase. I have this project that I’ve been building and iterating on with what I’ve found works well for me.