3 ms·

I don't see how this has anything to do with a monolith (in the sense of the monolith vs. microservices approaches). It's not really front page material either

I don't see how this has anything to do with a monolith (in the sense of the monolith vs. microservices approaches). It's not really front page material either (IMO), it's just a basic article about placing frontend and backend code in the same repo and making a script to run both locally. It doesn't even tackle any interesting problems like handling the separate needs of both codebases in the CI scripts, nor it gets much out of bundling the two together except for opening them in the same editor - which is somewhat conflated with it being a monorepo? (you could simply open a parent folder with two different codebases inside and achieve pretty much the same).

jdsleppy 5y ago
It's surprisingly easy to stay on the front page for a while. Anyways, I always enjoy seeing how other people set up this interstitial stuff, the ergonomics, and little scripts. I get a lot of valuable learning seeing other people do things, even things I know how to do (a different way).
sergiomattei 5y ago
Hi! Author here. My point with the article was to try and solve (and start a conversation) about some of the cognitive overhead problems of a frontend-backend stack. It's definitely not a monolith - hence the pseudo bit. For me, the ease of a monolith comes with having a deeply interconnected system with similar standards. Little context switching. About tackling bigger problems, I'll probably update it later once I face them. I'm a small, indie dev - I don't face huge problems!