Deadron

8 ms·

1.
by Deadron 8mo ago
Just do a normal merge, then squash all your commits in into one, using rebase, then a rebase onto a branch is easy.
2.
by Deadron 11mo ago
For when you inevitably need to expose the ids to the public the uuids prevent a number of attacks that sequential numbers are vulnerable to. In theory they can also be faster/convenient in a certain view as you can generate a UUID wit
3.
by Deadron 3y ago
I would hope you are not allowing IoT devices direct access to your database. There is no saving that haha.
4.
by Deadron 3y ago
Most large scale web applications spend their time reading and writing data, both to/from clients and to/from other remote services such as databases. You don't need thousands of hosts. Stackoverflow famously ran 9 server i
5.
by Deadron 3y ago
To be clear pgbouncer does not add connections to postgres or remove the connection bottleneck. Its still there under the covers. If you are saturating your connections it will not be able to improve on throughput. It sounds like you need
6.
by Deadron 3y ago
Don't spin up 50 pods. You have outscaled your database. You can't make IO operations faster by throwing more workers at it and you can only have so many connections working at once. As a side note if your application is a typic
7.
by Deadron 3y ago
Is this because your default approach is to horizontally scale or because you have tried other options? Logically scaling vertically a single server with pooled connections should have a better effect than horizontally scaling to multiple s
8.
by Deadron 3y ago
If you are running aws lambdas I believe you should be using the RDS proxy product(This is a very similar product though).
9.
by Deadron 3y ago
This still doesn't really make sense to me. You can't scale an application that relies on a database heavily to this level because your fundamental constraint IS the database. If you are already hitting your max number of connect
10.
by Deadron 3y ago
PgBouncer has always left me confused in the world of application level connection pooling. I have never quite understand the value of it if we are already using connection pools in our applications. I don't want to pool connections t
11.
by Deadron 4y ago
Poorly vs well structured code.
12.
by Deadron 4y ago
It depends. The come and go based on legislation and the current fixed interest rates. They were very popular for a bit but as the fixed rates kept dipping they seemed to mostly vanish. They seem to only really be popular when financial in
13.
by Deadron 4y ago
Auto generated client code is nice in theory. In practice I find it only really useful as a starting point. There are enough choices to be made in writing even a simple HTTP api that its unlikely that a generic tool will generate useful cod
14.
by Deadron 4y ago
Your example is missing anything actually related to rendering a webpage.
15.
by Deadron 4y ago
The tooling is far from simplistic to setup and the available options can be overwhelming. Its all the pain of the JS stack but with less easily available help and tooling that produces less helpful error messages.
16.
by Deadron 5y ago
I felt literal pain reading this.
17.
by Deadron 5y ago
Surprisingly, or maybe not, slf4j requires an implementation to be provided at runtime to log anything.
18.
by Deadron 6y ago
You can use a redis to distribute messages via PUB/SUB. The sockets subscribe to the events that are relevant to them. It can handle thousands of messages a second in a local environment and probably more in a dedicated hosting enviro
19.
by Deadron 6y ago
Windows....enough said.
20.
by Deadron 6y ago
Strategic missile defense almost entirely a complete waste of money. https://www.ucsusa.org/resources/disastrous-us-approach-stra...
21.
by Deadron 6y ago
12 factor apps sacrifice performance and simplicity of your environment for scalability. Unless you are guaranteed to start with a worldwide audience its complete overkill. A better solution is to write your application with the rules in m
22.
by Deadron 6y ago
Until you attempt to multithread the logic and everything breaks.
23.
by Deadron 6y ago
This article mentions node dependencies and ignores the innumerable number of libraries down the stack to the bare metal. Even if you wanted to spend the time writing your application without using any libraries you still must have some lev
24.
by Deadron 6y ago
One of the bigger problems is that exceptions are slow. Thus the recommendation is not to use them in cases where the caller could branch on. A perfect example is a missing element in a remote system. An old api would throw some sort of a E
25.
by Deadron 6y ago
Type erasure makes deserialization a pain. This has lead to multiple incompatible implementations of ways to indicate what a generic type contains on top of the existing type system. In practice it means using generic types on DTOs is a pi
26.
by Deadron 6y ago
I have never seen anybody migrate out of PostgreSQL, but I HAVE seen people migrate out of Oracle, and DB2 because they are so expensive its worth the cost to migrate.
27.
by Deadron 7y ago
Whoever developed the javascript could benefit from a formatter. Also, synchronous ajax calls?
28.
by Deadron 8y ago
SSH remote port forwarding is your friend. You just need an ssh server somewhere thats publicly accessible.
29.
by Deadron 8y ago
Having moved from the seattle area to the state of maryland, the lack of parks and public land feels very depressing. You drive by giant majestic horse pastures, but the parks are so small that you can still hear cars driving by.
30.
by Deadron 8y ago
Missing the key part that this was done by the police targeting a specific home. Otherwise security cameras would fall under this category.

More ›