noctarius

Thank you very much :)

Happy to get any idea on how to make it even better!

It is complicated to initially wrap your head around, I agree. That's why I thought a demo application is the best way to show that it doesn't have to be super complicated once understood.

Like many things in PG, they aren't always easy to get right away I remember my first time with it years and years ago.

It handles authentication on a request basis (which was its own issue just a little while ago): https://www.infoq.com/news/2024/05/aws-empty-s3-bucket-billi...

Not sure I'm really surprised. As far as I know, AWS hasn't been the fastest in resolving issues. I just remember the "S3 Bucket - We Charge You For Unauthorized Requests" issue a few months ago

I guess your biggest issue may be the multiple writer problem, but you'd have the same issue on a local disk. The second multiple writer are supposed to update the same files, you'll run into issues.

Have you thought about TCP sockets between the apps and sharing state, or something like a redis database?

You need some type of cluster-wide shared memory?

I bet there are lots of mistakes yet. It's not really automatically generated, but I started from the list at https://kubernetes-csi.github.io/docs/drivers.html and split the table into a YAML file, marking the features that are mentioned in the docs.

Fixed a few, where I saw thinks in their respective docs, and added features like file or object storage. Also added a few that weren't mentioned.

Topology is https://kubernetes-csi.github.io/docs/topology.html, ReadWriteOncePod is supposed to mean https://kubernetes.io/blog/2023/04/20/read-write-once-pod-ac...

Simplyblock sponsors the domain, yes. Good point. Should have mentioned that. It's not on the simplyblock github account though and as you can see on GitHub, I've built it over the weekend :)

Guess you want a block storage?

Uh! Thanks for mentioning. Also wasn't aware that plausible is blocked, thanks for the hint, even though I wonder why it breaks the search. I'll figure it out. Thanks again.

Disclaimer: host of the podcast

Nicolas Fränkel explains how API gateways help to implement customer-specific behavior into the API management and how this can help improve security. Obvious focus is Apache APISIX but also the broader topic of API gateway in general and why you want to use them.

I hope you're right. Apart from that, yes I think it's necessary.

Didn't think of this suspicion beforehand, but doesn't sound like a total miss.

Ouch. Glad you had the alarm (and that it reacted "early enough"). Anyhow, I think you may not be along with that surprise.

Seems like I'm a lucky one. Neither using RDS nor MySQL. But seriously, ouch. I mean, I get why they want people to migrate to supported versions but ...

True, but I guess it'll be a surprise to many. And, unfortunately, upgrading isn't always the easiest thing with deprecations and stuff

Article by Mary Henry. I was shocked to see how much more the extended support (per hour) cost is for Kubernetes on AWS.

Haven't had that situation myself on AWS yet, but ran into it a few times on Azure

I can't remember to have paid extra on Azure though, but maybe we did. Certainly not 6x the price though.

PS: not sure why it got flagged the first time, but I think because I used a different title. Sorry.

Article by Mary Henry.

I was shocked to see how much more the extended support (per hour) cost is for Kubernetes on AWS.

Haven't had that situation myself on AWS yet, but ran into it a few times on Azure

I can't remember to have paid extra on Azure though, but maybe we did. Certainly not 6x the price though

Kubernetes is around for about a decade by now. How much longer is it going to stay? Will it decay into the void soon, or is it here to stay?

Álvaro Hernández Tortosa from OnGres, a company providing the necessary tooling to run a production-grade PostgreSQL in Kubernetes. Álvaro talks about the issues with the many-solutions-to-a-problem situation in Postgres and how it can be overwhelming and alarming to newcomers.

"A persistent volume is a slice of storage, provisioned by an Kubernetes administrator, that can be attached and mounted to pods." Sounds important, doesn't it? But what does it actually mean and how does it work? When deploying stateful workloads, such as a database, into Kubernetes, persistent storage is a must-have. For that reason Kubernetes provides persistent volumes. But what are those specifically and how do they work internally? Our newest blog post, "what is a Kubernetes Persistent Volume?" answers them in a technical, but not super-technical fashion, making it possible for people to really grasp the how and why aspects. https://www.simplyblock.io/post/what-is-a-kubernetes-persist... Question: Do you use Persistent Volumes in Kubernetes? If so, tell us your preferred storage plugin is or if you have any issues.

The terms container attached storage and container storage interface are important terms when it comes to stateful container workloads. On the other hand it's one of the questions we don't like to ask "what is ...?". So I took the chance to answer it before it needs to be asked. I hope somebody finds it valuable and helpful.

Yes you can have both in the same database. We actually use TimescaleDB exactly that way, well at least for now. We'll in the process of separating certain tables out, so make it possible to select a pg database based on async or sync replication.

In terms of creating a Hypertable (TimescaleDB table) you create the normal table first and then transform it into a Hypertable.

That is a pretty good and detailed blog post. I wonder, however, if I can use any aggregate call to build out a continuous aggregate. I'm specifically think about things like sketches and hyperloglogs.