tbarbugli

6 ms·

1.
Pgmigrate – Pgcopydb Rewritten in Go(github.com)
2 points by tbarbugli 14d ago|5 comments
2.
by tbarbugli 14d ago
After fighting crash after crash with pgcopydb v17 and v18 I decided to bite the bullet and write my own in Golang. I picked Golang because most issues with pgcopydb were related to concurrency bugs and memory leaks. There is nothing in thi
3.
by tbarbugli 9mo ago
At getstream.io we ended up running Github Actions on Hetzner. The end-result is 4x faster builds for 3x less $$$. Running workers ourselves was the last resort, we tried everything else but it was impossible to get fast (and consistent) bu
4.
by tbarbugli 1y ago
> anyone can see what URLs you are visiting this is not correct with HTTPS (query params are not part of the plain text)
5.
by tbarbugli 1y ago
ofc it depends where you would hire, for me (NL) its above 100x more efficient
6.
by tbarbugli 1y ago
I agree, only reason I read the project readme was to see the drop-in explainer. Very misleading title
7.
by tbarbugli 1y ago
searching for running shoes returns a mix of brands and shoe models
8.
by tbarbugli 1y ago
Plenty of engineers on the market can work professionally in C. Only a small amount of people can write Cobol (or is willing to given that is almost useless). That alone is a good reason to consider Cobol a legacy language and throw away a
9.
by tbarbugli 2y ago
> At Compose, every WebSocket message starts with a fixed 2-byte type prefix for categorizing messages. some of the complexity is self-inflected by ignoring KISS principle
10.
by tbarbugli 2y ago
In my experience, only Swift has a generator that produces good-quality code. Ironically, it’s developed by Apple.
11.
by tbarbugli 2y ago
The list of supported commands looks quite impressive https://kvrocks.apache.org/docs/supported-commands#script-co...
12.
by tbarbugli 2y ago
Using DynamoDB in 2025 is such a weird proposition. Horrible dev experience, no decent clients/libs, complex pricing, weird scaling in/out mechanism, slow, it only works well for well defined use-cases.
13.
by tbarbugli 2y ago
Google is not winning on cloud, AWS is winning and MS gaining ground.
14.
by tbarbugli 2y ago
> Use Postgres for Fulltext Search instead of Elastic pg fulltext search is very limited and user unfriendly, not a great suggestion here
15.
by tbarbugli 2y ago
Ideally it does not run on the awful EBS storage (slow and expensive).
16.
by tbarbugli 2y ago
Possibly because they capture the video from xvfb or similar (they run a headless browser to capture the video) so at that point the decoding already happened (webrtc?)
17.
by tbarbugli 2y ago
Makes you wonder why there were no plane hijacks since 9/11. TSA does not seem a credible prevention mechanism given how easy it is to go around it.
18.
by tbarbugli 2y ago
Nice article which matches my experience when it comes to optimizing for performance: Linux defaults are never good defaults and you don't need webscale or anything before you get bitten by them. To make a few examples: on many distrib
19.
by tbarbugli 2y ago
https://github.com/cockroachdb/cockroach/graphs/contributors
20.
by tbarbugli 2y ago
TL;DR it is a job
21.
by tbarbugli 2y ago
hosted on Vercel and Github...
22.
by tbarbugli 2y ago
isn't China producing more electricity with solar than all other countries combined (with solar)?
23.
by tbarbugli 2y ago
io2 is generally better than io1, one advantage is that you can scale storage size and IOPS independently. That being said, RDS with io2 is still worse than an ec2 instance with nvme (a lot worse)
24.
by tbarbugli 2y ago
RDS is such a depressing database option. It does not matter how much money you throw at it, its performance will always be limited by the awful disk IOPS. Luckily these days you can easily run PG on EC2 (or simply use CRDB). Weird for Hero
25.
by tbarbugli 2y ago
well, they shut this down probably because they cannot afford to keep a product that bring little revenue. I never heard of AWS retiring a product (I am excluding ancient stuff like VPC classic and SimpleDB, both had an upgrade path to some
26.
by tbarbugli 2y ago
it increases the cost for the attacker, forging ID is expensive and against the law. It also leaves behind additional evidence that might be useful to investigators
27.
by tbarbugli 2y ago
I think its around 1TB a day, but indeed still very small.
28.
by tbarbugli 3y ago
we wrap all errors with a stack.Wrap function that adds stacktrace to the error. This allows us to add stacktraces to logs and err reporting tools like Sentry. Huge time saver
29.
by tbarbugli 3y ago
you only do it when there is a not nil err + being able to have a stacktrace is worth more than whatever it costs is CPU
30.
by tbarbugli 3y ago
Citus seems incredibly close to what they built, I wonder why they did not use it

More ›