Re:How to Design Software Architecture for Startups
by preseinger on Tuesday May 09, 2023 @11:02AM
(#35875382)
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?
I assumed it was done here. Why wouldn't it have been? There's no evidence of that.
> Shared data structures? Common library? Services have an API
I assumed that was what they meant: common data structures being whatever the various APIs emitted and received. You don't need more than that if you're two people shipping a full product. People aren't buying your internal architecture, and it sounded as though they built it so the code could be separated out in future if necessary.