Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
valyala
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
17 ms
·
241.
▲
by
valyala
2y ago
VictoriaMetrics CTO here. I don't understand why pure open-source license such as Apache2, MIT or BSD should be replaced with some source available license in order to increase profits from enterprise support contracts: - The license c
242.
▲
by
valyala
2y ago
Open source works great for for-profit companies. Take a look at RedHat.
243.
▲
by
valyala
2y ago
TimescaleDB has not so good performance and on-disk data compression rate comparing to ClickHouse [1]. TimescaleDB is good for cases with relatively small amounts of time series data (e.g. up to a few tens of billions rows) when you already
244.
▲
by
valyala
2y ago
Lack of generics didn't prevent from creating many useful projects in Go such as Docker, Kubernetes, Prometheus, Terraform, etcd, minio, Caddy, Traefik, and many others from the list at https://github.com/search?q=lang
245.
▲
by
valyala
2y ago
> What logging solutions are you using in your Kubernetes environment, and how has your experience been? We store all the logs from all the containers running in our Kubernetes clusters into VictoriaLogs during the last year. It works sm
246.
▲
by
valyala
2y ago
If you need efficient exporting of any amounts of logs, then take a look at VictoriaLogs - the log management system I work on. It is designed in the way which allows exporting arbitrary number of logs via the standard querying API. See ht
247.
▲
by
valyala
2y ago
What to use as a centralized system for `keep things "stupid-simple"`? I'd recommend taking a look at VictoriaLogs - the system I work on. It is designed with KISS principle in mind, so it is very easy to setup, operate and u
248.
▲
How Go Arrays Work and Get Tricky with For-Range
(victoriametrics.com)
1 points
by
valyala
2y ago
|
0 comments
249.
▲
by
valyala
2y ago
Scala is overcomplicated esoteric programming language. It is great for obfuscation contests. It is awful for production code, since Scala code lacks maintainability, readability and simplicity properties.
250.
▲
by
valyala
2y ago
The sync.Map.Range, filepath.Walk and other similar functions with visitor pattern in standard Go packages will remain there forever because of backwards compatibility. This means that new functions must be added to standard Go packages in
251.
▲
by
valyala
2y ago
> Prior to generics I often had to write some quite complicated (and buggy) reflection code to do something I wanted (e.g. allow to pass functions that take a struct and return a struct+err to the web URL handlers, which would then get a
252.
▲
by
valyala
2y ago
Go provides generic types since v1.0 - maps, slices and channels. Go also provides generic functions and operators for working with these types - append, copy, clear, delete. This allows writing clear and efficient code. There is close to z
253.
▲
by
valyala
2y ago
While vendoring is great, generics is bad addition to Go, since they complicated Go type system too much [1]. This makes typical Go code with generics hard to read and hard to maintain. [1] https://go.dev/blog/type-infe
254.
▲
by
valyala
2y ago
Iterators and generics go against the original goals of Go - simplicity and productivity. They complicated Go language specification too much without giving back significant benefits. Iterators and generics also encourage writing unnecessar
255.
▲
Golang Defer: A Detailed Guide
(victoriametrics.com)
2 points
by
valyala
2y ago
|
0 comments
256.
▲
by
valyala
2y ago
Batched inserts to LSM-based databases aren't so uncommon. For example, ClickHouse expects batched writes - https://clickhouse.com/docs/en/optimize/bulk-inserts . Of course, it supports asynchronous inse
257.
▲
by
valyala
2y ago
LSM trees do not need write-ahead log in general case: - When new data arrives, it is converted to SSTable, which is then stored to disk in an atomic manner before returning 'success' to the client, who writes the data. If compute
258.
▲
by
valyala
2y ago
A good example of database, which relies on LSM tree properties for protecting against data corruption on unclean shutdown is VictoriaMetrics [1]. [1] https://valyala.medium.com/wal-usage-looks-broken-in-modern-...
259.
▲
Some notes on Grafana Loki's new "structured metadata" (as of 3.0.x)
(utcc.utoronto.ca)
2 points
by
valyala
2y ago
|
0 comments
260.
▲
What I think goes wrong periodically with our Grafana Loki on restarts
(utcc.utoronto.ca)
1 points
by
valyala
2y ago
|
0 comments
261.
▲
by
valyala
2y ago
My advices to new software engineers: - Always think how to simplify the code you write, since simple code is easier to maintain and debug. - Prefer writing dumb code than smart code. Smart code is good for programming contests. Smart code
262.
▲
by
valyala
2y ago
Software products usually have no publicly available development goals. Probably some of these products have internal development goals, but most of the time these goals are implicit. You can guess these goals by looking at the history of n
263.
▲
VictoriaMetrics Development Goals
(docs.victoriametrics.com)
2 points
by
valyala
2y ago
|
1 comments
264.
▲
by
valyala
2y ago
Thanks for providing the brilliant citations of Rob Pike! I like the most these ones: > Go is a project to make building production software easier and more productive. > Go code looks and works the same regardless of who's writi
265.
▲
by
valyala
2y ago
It would be great if the README.md contained both versions of the code - without using xtract+iterators and with using xtract+iterators, so readers could compare both versions.
266.
▲
Things Get Done on the Go Team with Russ Cox
(changelog.com)
1 points
by
valyala
2y ago
|
0 comments
267.
▲
by
valyala
2y ago
How about allowing users creating pipelines with good old grep, awk, cut, etc., directly in the web UI?
268.
▲
by
valyala
2y ago
Correct for now. I'm sure LogsQL support will be added into other systems for logs' management over time.
269.
▲
by
valyala
2y ago
Diversity is great! Let's see which query language for logs will survive.
270.
▲
by
valyala
2y ago
Canonical pipes were invented ~50 years ago by Unix creators. They are successfully used for logs' analysis to this day. Unix pipes have a simple idea - connecting the output of one program to the input of another program. This allows
More ›