3 ms·
What you are complaining about is completely solved via microservices.
by ReflectedImage 3y ago
What you are complaining about is completely solved via microservices.
- alexvitkov 3y agohow?
- ReflectedImage 3y agoYou restrict the code area you need to search via strong encapsulation.
- pdimitar 3y agoThis does not address the example given above.
- ReflectedImage 3y agoIt actually does.
- alexvitkov 3y agoAdd microservices and typos are still runtime errors, except now on another, except inside a container on another computer. You still have to grep for callsites, although the scope is smaller. A much better way to reduce the scope is with modules - if a function is module-internal, you only have to grep that module for callsites. Better than having to scan the entire codebase, worse than not having to do it at all. Performance with microservices + dynamic language is unjustifiably terrible if you're the one who's paying for the servers. You're already eating a 100x slowdown for using a scripting language, add microservices and you're eating easily another 100x for replacing regular function calls with network packets. I'm not willing to run a k8s cluster for a program my laptop could handle had I used the hardware better. That's all assuming microservices are even an option, which is a very tiny percentage of all software.