Long functions are hard to work with. They are often contained in large classes that have many dependencies. The work that it takes to bring such functions and classes into a test harness is often significant. The Break Out Command Object refactoring technique can help with that.
Wrapping 3rd party libraries can be a challenge when dealing with Angular directives. The four steps laid out in this article should help.
I recently upgraded my computer's RAM to 32GB from 16GB. It was running fine but ever since I started doing more work with Docker containers, it felt like it would get sluggish once in awhile.
He rightfully reminded me that "all models are wrong, but some are useful". So the question is, despite the fact that, according to our analysis of the DDD literature, viewing the SPA as part of the same BC as the server-side API is more "right" than viewing it as a separate BC, is it more useful?
Does a Bounded Context only contain the classes and interfaces that are part of the domain model (entities, value object, domain services, domain events and repositories) or does it extend to the classes (application services, controllers, etc.) in other layers?
I quickly realized that the concept of a Bounded Context was not that easy to define. This is precisely why it seemed hard to find a clear cut answer to our question. So, before we can go any further, a discussion on what constitutes a Bounded Context is in order.