6 ms·
if you're two people then there is absolutely no reason to introduce a network API boundary between functional components if you do have an API boundary then i
by preseinger 3y ago
if you're two people then there is absolutely no reason to introduce a network API boundary between functional components
if you do have an API boundary then it's important to understand that interactions against that boundary are resolved at runtime -- in contrast to data structures which are resolved at compile time
if you break something out to a service that's only accessible over a network boundary then there's not much sense in requiring access to go thru some SDK library, right?