3 ms·
amen. At first i figured containers were a good way to run code with difficult dependencies and weird operating environments, but that still doesnt make sense.
by nimbius 8y ago
amen. At first i figured containers were a good way to run code with difficult dependencies and weird operating environments, but that still doesnt make sense.
- systemd and uwsgi for example play well when run as a single user per wsgi application under a single nginx/lb.
- php-fpm already handles a ton of overhead from php apps.
- ansible deployments called from gitlab-ci can roll out apps just as well as deploying from the registry.
then i figured maybe they were on to something with the autoscaling thing...but that seems like a meaningless feature. Every good project already has metrics and forecasting...it would be absurd to think a final product like imgur.com or twitter does not know (down to the byte) how much storage theyll need in 4 months and the potential drivers.
auto-scaling infrastructure just betrays the fact that most developers throw resources at load problems instead of waiting for ops to figure out the actual issue.
- latchkey 8y agoI helped build an e-commerce marketplace, which is essentially a shopping cart system that was used by third parties. We had no idea how to predict traffic loads because we had no idea when one of our customers would run a successful campaign. Autoscaling on google appengine was a lifesaver for us. Our very small dev team focused on building features because we had zero devops and we didn't have to carry a pager.
- rhinoceraptor 8y agoI don't think most developers or admins really have the toolset/skills to debug to root cause. Most people see debugging as the process of making problems go away, not as the science of understanding a problem. You need both developer and admin skills, as well as a pretty good understanding of the whole stack - the application, the framework/libraries, the application runtime/support libraries, the database, the kernel and the network.