2 ms·
>If different components of your system are talking over a pretend network you've already architectured yourself face first into a pile of shit. How do you hav
by mhuffman 3y ago
>If different components of your system are talking over a pretend network you've already architectured yourself face first into a pile of shit.
How do you have your file delivery, database, and business logic "talk" to each other? Everything on the same computer is a "pretend network" to some extent, right? Do you always architect your own database right into your business logic along with a web-server as a single monolith? One off SPAs must take 2-3 months!
- alexvitkov 3y agoYes, replacing a full duty database with an in-process SQLite generally simplifies things if you can afford it. Even if not that's a bad example, since in prod your fat database will be om another computer for real, so you'd never use a Unix socket when developing locally.