rigaspapas's comments

rigaspapas | 4 years ago | on: Zero downtime Postgres migration, done right

A few minutes of downtime wouldn't be that bad, but it would harm the company's prestige. Unlike AWS and Netflix, we are not based on massive consumption, but on a few customers. Losing one good customer can make a difference. We believe it worth the investment of time.

rigaspapas | 4 years ago | on: Zero downtime Postgres migration, done right

You are right. AWS DMS was our very first choice to try out. It is very easy to use, deployed within your VPC and most of the problems we mention in the article are already solved. Unfortunately, we experienced errors during our tests and the logging mechanisms were not quite helpful, so we failed to find out the problem and make it work.

rigaspapas | 4 years ago | on: Zero downtime Postgres migration, done right

That's a good point. We mention latency as "replication lag" and we have devoted a paragraph to the drift that comes as the result of this latency. In our case, we measured the latency to be <1s, and it was totally acceptable. As for the performance, triggers can become a problem with enough write traffic. In a different use case, Bucardo would be eliminated from a potential solution due to this.

rigaspapas | 4 years ago | on: Zero downtime Postgres migration, done right

We didn't mean to be arrogant with the "done right" statement. In the background story we explain how we performed the same migration once again in the past, and we end up with data loss. So this was the time that actually "did it right". Many tutorials on the Internet that describe a similar process have flows that also lead to data loss.

rigaspapas | 4 years ago | on: Zero downtime Postgres migration, done right

AWS can upgrade your database automatically, but with some downtime. AWS also provides DMS for migrations, which didn't work well in our case. So it was rather a simple problem at first, which turned to be a very complex one in the end.

rigaspapas | 5 years ago | on: Discipline Doesn’t Scale

Exactly. With so many people out there advertising themselves as "software engineers" but being "coders", companies fail to produce maintainable code without a bunch of strict rules. Coding manifestos are a must these days, otherwise you end up with a codebase that looks like the Tower of Babel.

rigaspapas | 10 years ago | on: Monitor your local network with Raspberry Pi

Would arpwatch provide any extra information? Ntop sounds like a very interesting idea, I wasn't aware. I suppose you mean you can use a wireless card on you Pi, so the clients can connect through it, and then use ntop to measure the usage... Right?

rigaspapas | 10 years ago | on: Monitor your local network with Raspberry Pi

If you want to see what clients are connected to your network you have to login into your router (typing username & password), navigate to its WiFi or DHCP client tables and then try to match MAC addresses with real clients. What I tried to do is mostly time saving. You can have information about hostnames, MACs, MAC manufacturers and status via the web.
page 1