Re:Super small Docker image based on Alpine Linux
by detaro on Wednesday December 23, 2015 @12:25PM
(#10784383)
Agree in general, but you can overdo it with splitting services up. E.g. would you really run a extra container just for a cronjob that runs once a night to e-mail some data from a database? Esp. if you run on a platform where you essentially pay per container that seems like a waste.
[ Parent
| on HN ]
Re:Super small Docker image based on Alpine Linux
by koffiezet on Wednesday December 23, 2015 @01:15PM
(#10784679)
Most of the things I described assume you have full control over your host's OS.
For stuff like you mention - you should maybe reconsider not using containers if you're on a pay-per-container platform? They are just a tool, and certainly don't fit every single use-case. Also - paying per container seems like a silly thing to do - since containers can be very short-lived. Resource-based billing would be a better fit - although that could be tricky to measure I guess.
Re:Super small Docker image based on Alpine Linux
by detaro on Wednesday December 23, 2015 @02:02PM
(#10784954)
I'm currently toying with IBM bluemix (mostly because they have a relatively big free tier) and they have resource-based billing, but you since can't make containers arbitrarily small and you pay for RAM reserved for a container, it is effectively per container. So even if you only need 1 GB for 30 min every night, you either build something that starts a worker container on schedule or you pay for resources you don't use 98% of the time. I guess other platforms are similar.
But of course, if you can afford to use that in production it probably doesn't matter very much, and you might choose a different platform if it bugs you. Just came to mind because I just was wondering how to split stuff up.