Re:Japanese textile factory still uses tape cassette and pun...
by giovannibonetti on Monday July 10, 2023 @08:51AM
(#36665605)
Parent was probably talking about the application server, which is the typical example of K8s usage, whereas most databases don't fit well there and are usually separate from the K8s cluster.
[ Parent
| on HN ]
Re:Japanese textile factory still uses tape cassette and pun...
by benglish11 on Monday July 10, 2023 @10:23AM
(#36666904)
Yeah. They must be. I’ve had several k8s enthusiast dissuade from putting a db in k8s for performance reasons. This may change overtime but I believe there is a performance bottleneck in disk I/o (or at least that’s how it was explained to me)
Re:Japanese textile factory still uses tape cassette and pun...
by mschuster91 on Monday July 10, 2023 @10:39AM
(#36667138)
That really depends on your k8s environment. If you're running on bare metal and use host bind mounts for storage, you won't have a problem. But as soon as you introduce shared storage it gets messy...
Re:Japanese textile factory still uses tape cassette and pun...
by tjoff on Monday July 10, 2023 @11:12AM
(#36667599)
Doesn't that defeat the promise of k8 in the first place?
Because then it won't scale.
And the moment you do you run into other bottlenecks.
Re:Japanese textile factory still uses tape cassette and pun...
by mschuster91 on Monday July 10, 2023 @12:14PM
(#36668470)
Meh, not having to worry about configuring load balancers and letsencrypt alone is worth the effort to get k8s running.