Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
So I did a lot of research last year on how I should be organizing my apps and landed on Clean/Onion as one of the best if not the gold standard of how one should be organizing maintainable and complex apps. I read books and blogs, checked out the eShop projects, saw jason taylor and steve smith's example projects, and tried a few POCs myself. It worked well and I liked it. I even made a tool that can scaffold out a Clean web api that works pretty nicely. Regardless of the below, I can pretty definitely say that a Clean organization is a solid approach.
To give this an initial POC I scaffolded out a Wrapt project (builds it out with a Clean approach) with a couple entities. I kept the SampleContainer entity with a Clean setup and updated the Patient entity to use a VSA approach (check out the repo here). I didn't mess with any domain logic or anything yet as that wasn't the point of the exercise and more-so wanted to see which organizational approach felt the best and most maintainable overtime. After all was said and done, the POC updates I made using VSA seemed to confirm the Jimmy Bogard's assertions and felt really nice to use.
Example Repo