2 ms·
Im secretly a fan of the boring tech statement. Sometimes all of the new containerization and microservice paradigms just feel like an excuse to overengineer ev
by nlstitch 4y ago
Im secretly a fan of the boring tech statement. Sometimes all of the new containerization and microservice paradigms just feel like an excuse to overengineer everything. Running solo and starting from scratch (no code, no infra, no cloud subscriptions) means you'll have to simplify and reduce moving parts.
- guhidalg 4y agoYes! Boring tech is working tech, never choose an untested technology if there's any real stakes in the work.
- outworlder 4y agoMicroservices are difficult to justify with a small team (or a single person team in this case). If your monolith has obvious modules that can be carved out, you _need_ to scale them independently and for some reason you can't just deploy multiple monolith copies, then it may be worth it to do microservices. At large companies, the calculations are different. Even when monoliths would be the best fit, they may still carve out microservices. How else would they be able to ship their org chart? :)
- intelVISA 4y agoKISS but unironically
- XCSme 4y agoI still believe the LAMP stack is the future for most non-realtime applications. With PHP you just FTP copy a file to the server and it works instantly, no builds, no compilation, no restarts. Compared to Node.js the server feels a lot more robust by default and an uncaught exception doesn't bring down the whole server until restarted. The biggest plus: you can host a lot of applications on the same stack and by default ALL parts of the stack (Apache, MySQL, PHP) can handle concurrency and load distribution well (with Node.js, for example, by default each application will be mostly single-threaded, you have to manually spawn multiple Node.js instances/workers for it to properly use all the server resources).