Versioning business rules
TL;DR Storing ever-changing business rules so that an app can behave like it did at moment X in the past. Can it be done? If so, how? Long version At this very moment, this is more of a thought exercise than an actual need, though things could change in the not so distant future. The […]
Models, types, different views and meta data
We have a software which purpose is to be used to help users build their own applications. It has to be very loose coupled with the infrastructure: for example, I can imagine users running it on MySQL database as well on MongoDB.
How do you keep control in a large software project? [duplicate]
This question already exists: How to manage a relatively large one-man project? [duplicate] Closed 9 years ago. I’ve a large-ish software project that I’m the sole developer for (~80KLOCS and counting – I know there are much larger projects out there, but it’s an order of magnitude larger than I’ve ever had to deal with […]
Collections, relationships and tracking changes (in DDD)
Let’s say we have a Book that has a List of Authors. Order of Authors is important.
Calling Web API vs adding reference to underlying dlls [closed]
Closed 8 years ago.
Plugin/modular architecture – deployment concerns
I’m developing a desktop application in .Net that follows a plugin architecture, something like this:-
Encapsulate one business story/use case in one class?
I don’t like classes like *Service, with bunch of business methods – aka anemic model. I was thinking, instead, to have a class per use case. This was inspired (if not the same) from CQRS. Even if we are not using event sourcing, I believe that this kind of encapsulation would make sense. Then the service layer (application layer) would simple consist of commands that user can instantiate and pass to some executer.
Using entityManager/repository Class/session factory directly in controller
I wonder what is your approach on following subject:
Batching immutable object changes?
With immutable models, what would be the best way to batch several changes?
How to introduce Google Analytics code in a modular way?
We are working on a very large codebase. It’s basically a web-based operating system, with its own file system and applications. The system’s UIs are generated dynamically with Javascript.