@therealadam @wycats teams that "gem install" boundaries via frameworks have a head start, since drawing boundaries is very time expensive.
-
-
Replying to @realntl
@therealadam@wycats but OTOH orgs that fail to establish boundaries around application components tend to slow down eventually.2 replies 0 retweets 0 likes -
Replying to @realntl
@therealadam@wycats this is I think why microservices has gained traction. Though I am not a fan of that myself.1 reply 0 retweets 0 likes -
Replying to @realntl
@realntl@therealadam the problem is that "since boundaries are important you may as well impose a zillion boundaries" is counterproductive1 reply 0 retweets 1 like -
Replying to @wycats2 replies 0 retweets 0 likes
-
Replying to @therealadam
@therealadam@realntl in my opinion, the goal of good boundaries is to let you be "sloppy in the small, rigorous in the large"1 reply 0 retweets 2 likes -
Replying to @wycats
@therealadam@realntl Dynamic languages simply don't allow rigorous in the small, and that's has great benefits in many ways.1 reply 0 retweets 0 likes -
Replying to @wycats
@therealadam@realntl Breaking isolation boundaries makes the "sloppy in the small" leak into the large and eventually slow you down.1 reply 0 retweets 0 likes -
Replying to @wycats
@therealadam@realntl But if you have tiny isolation boundaries, you're just trying to recover "rigorous in the small", poor fit for dynlang1 reply 0 retweets 0 likes
@therealadam @realntl yes, ES6 modules have that goal :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.