professionalssoli.blogg.se - Bounded contexts

#Bounded contexts code

In our last chat together, we discussed developing a Ubiquitous Language together with the business experts and your development team to help your team work more closely together.

#Bounded contexts code

Changing code in one area of the code leads to unexpected and unintended side effects in other areas of the code, because it’s easy to call out to global services and objects.

In fact, nobody seems to be able to understand the system as a cohesive whole

You have an ever-growing list of business objects that are difficult to keep in your head.

Refactoring is difficult and tedious, because methods and classes depend on too many other classes.

You may be experiencing the same pains as well if: When building large applications in frameworks like Rails, the very convention-over-configuration design principles that made Rails such a joy to use begin to get in the way when the application grows in scope.

Monolithic applications are great when you start building your company, but as time progresses, they become difficult to maintain. These codebases, as they grow, easily become Big Balls of Mud. Check out the video of this talk from ElixirConf 2017 below