4 ms·
I have found that this applies all the way up to the loftiest levels of abstraction. For instance, we partition our problem space in terms of logical business p
by bob1029 6y ago
I have found that this applies all the way up to the loftiest levels of abstraction. For instance, we partition our problem space in terms of logical business process once you get to a certain altitude in the architecture. But, the most obvious way to represent these discrete process domains was with... objects. So yeah. It's objects all the way up. The only difference between good and bad code is how the developers handle namespacing, drawing abstraction hierarchies and modeling business facts.
Microservices are about organization, not about requests being sent on wires throughout some abomination of a cloud infrastructure. Developing a UserService class and having the audacity to just directly inject it into your application for usage is probably one of the most rebellious things you could do in 2020. Extra jail time if you also decide to use SQLite where appropriate.
- systemvoltage 6y agoWriting straight SQL will land you in a prison.
- collyw 6y agoThings were so much easier 15 years ago. I see very little gain for all the complexity we have added since then. Ok we can scale easily on demand, but the vast majority of places won't need to.
- fxtentacle 6y agoActually, we still can't scale easily on demand. Let's say you get 2x the traffic. Sure, your front-end instances in the cloud can scale to 2x the capacity, but that just moves the bottleneck over to your database. And then you noticed that scaling an Amazon RDS database to a larger instance requires downtime...
- soulofmischief 6y ago> The only difference between good and bad code is how the developers handle namespacing, drawing abstraction hierarchies and modeling business facts. I wish those were the only indicators of bad code, but illegible aesthetics, over-engineered complexity, under-engineered fragile modules, etc. are to be found everywhere.
- eecc 6y agoI’d also add “not a shred of documentation” to the list. Not a comment, no issue- tracker IDs in the commit comments; just a confabulating pile of generically named “things doing things”. Sometimes I’d rather go farming
- soulofmischief 6y agoYes, programming keeps me straddling the line between futurism and going full luddite. Come on people, nobody is a mind reader, document your intentions in comments at the very least!