A collection of 5 posts
I recently participated in the js13k game jam, a yearly competition where developers create games in just 13 kilobytes of JavaScript code. It runs for a whole month, from August 13 to September 13. I've been toying with game development…
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.
We often consider the location of execution as defining an architectural boundary. We think that code that runs in the browser is necessarily GUI code. That’s not quite true, however. Business code can run in the browser, and formatting code run on the server.