HackerTrans
TopNewTrendsCommentsPastAskShowJobs

ananthakumaran

no profile record

Submissions

ClickHouse Table per Tenant in Production

ananthakumaran.in
2 points·by ananthakumaran·letzten Monat·0 comments

OpenAI deprecation notice: upcoming model shutdowns in 2026

developers.openai.com
3 points·by ananthakumaran·vor 3 Monaten·0 comments

Moving a tenant across PostgreSQL instances

ananthakumaran.in
1 points·by ananthakumaran·vor 3 Monaten·0 comments

Overlay Bar Chart

ananthakumaran.in
1 points·by ananthakumaran·vor 4 Monaten·0 comments

Moving tables across PostgreSQL instances

ananthakumaran.in
85 points·by ananthakumaran·vor 8 Monaten·5 comments

comments

ananthakumaran
·vor 2 Monaten·discuss
For those who are using Emacs, https://github.com/federicotdn/verb provides similar UX, I have been using it as a postman alternative for quite some time.
ananthakumaran
·vor 4 Monaten·discuss
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions. LSP is hit or miss; in some languages, it works great, while in others, the implementation is not so good. I have been thinking about a middle ground based on Tree-sitter. GitHub uses Tree-sitter to power code navigation, but unfortunately, I can't find anything good that I can use offline. Why is there no ctags equivalent powered by Tree-sitter?
ananthakumaran
·vor 5 Monaten·discuss
No, it's a background job. We can easily control the Python process count by controlling the job queue concurrency on the Elixir side.
ananthakumaran
·vor 5 Monaten·discuss
We have a similar use case. All Elixir code base, but need to use Python for ML libraries. We decided to use IPC. Elixir will spawn a process and communicate over stdio. https://github.com/akash-akya/ex_cmd makes it a breeze to stream stdin and stdout. This also has the added benefit of keeping the Python side completely stateless and keeping all the domain logic on the Elixir side. Spawning a process might be slower compared to enqueuing a job, but in our case the job usually takes long enough to make it irrelevant.
ananthakumaran
·vor 6 Monaten·discuss
ES should be thought of as a json key value store and search engine. The json key value store is fully consistent and supports read after write semantics, refresh is needed for search api. In some cases it does make sense to treat it as a database provided the key value store semantics is enough.

I used it about 7 years ago. Text search was not that heavily used, but we utilized the keyword filter heavily. It's like having a database where you can throw any query at it and it would return a response in reasonable time, because you are just creating an index on all fields.
ananthakumaran
·vor 6 Monaten·discuss
https://ananthakunaran.in
ananthakumaran
·vor 7 Monaten·discuss
Exactly, I was reading the blog and wondering the whole time how it's better than --update-refs, which I have been using a lot recently.