Bogdanovich

7 ms·

1.
by Bogdanovich 9y ago
Not all government officials and police officers are the same. For example Magnitskiy scandal in Russia. https://en.wikipedia.org/wiki/Sergei_Magnitsky#Exposing_the_... TL/DR: police had given the materials taken
2.
by Bogdanovich 9y ago
Not all government officials and police officers are the same. For example Magnitskiy scandal in Russia. https://en.wikipedia.org/wiki/Sergei_Magnitsky#Exposing_the_... TL/DR: police had given the materials taken
3.
by Bogdanovich 9y ago
Not all government officials and police officers are the same. Have you heard of Magnitskiy scandal in Russia? TL/DR: police had given the materials taken during the police raids to organized criminals, who used them to fraudulently re
4.
by Bogdanovich 9y ago
"Building out autonomous technology and having global network is a huge advantage. Because the issue with autonomy and any software, is that you've got these edge cases [...]. If you have a network live and you developing autonomy
5.
by Bogdanovich 10y ago
It is dangerous. This guy's (Alexey Navalny) brother is in jail on a fabricated lawsuit as a hostage. Alexey himself was also convicted guilty and the only reason he personally is not in jail is because he will only get more rating poi
6.
by Bogdanovich 10y ago
Any significant Russian leak will be instantly picked up by the western media. There is a lot of leaks on Russia in the media. No one actually cares anymore since it's mostly corruption stories and everyone is already knows there is a
7.
by Bogdanovich 10y ago
It's US pretends to be the world police and not the Russia.
8.
by Bogdanovich 10y ago
He hiding from the United States in Ecuadorian Embassy for many years. No surprise he is biased against US. Unites States pretends to be the country that does 'good' things, and blames all other countries that do 'bad'
9.
by Bogdanovich 10y ago
I don't really get the comparison with Pony Express part. As you said they shut down because of superior technology (transcontinental telegraph). So the superior technology to Uber and Lyft will be self-driving cars or teleportation. T
10.
by Bogdanovich 10y ago
They've been trying to sell the company earlier without any success: https://www.nytimes.com/2016/08/20/technology/lyft-is-said-t...
11.
by Bogdanovich 10y ago
This regulation was probably a good reason for uber to sell its business as it protects didi's market share
12.
by Bogdanovich 10y ago
From bbc.com: "The deal with Didi Chuxing comes just days after China agreed to provide a legal framework for taxi-ordering apps. Both Uber and Didi have welcomed the decision, having previously operated in a legal grey area in the cou
13.
by Bogdanovich 11y ago
It would only trigger compaction if sst tables have overlapping keys. And if you only write new items, goleveldb implementation would just create 3.7Mb sst tables by default without trying to merge them into bigger chunks (what's the p
14.
by Bogdanovich 11y ago
I added some more benchmarks including packing with 200M small 64 byte messages (20Gb) and consumption of that queue. There is no slowdown because of mass delete. https://github.com/bogdanovich/siberite/blob/m
15.
by Bogdanovich 11y ago
There is no benefit in that except faster startup time. As a downside you'll get a lot head/tail db keys updates.
16.
by Bogdanovich 11y ago
In case of reliable fetch failure each consumer group will keep it's own queue of failed deliveries (persisted on disk), will check that queue and serve these failed items first.
17.
by Bogdanovich 11y ago
Right now it doesn't store any consumer offsets. And you can get either at-most-once or at-least-once guarantees. But I found the idea of multiple consumer groups per queue very interesting. So basically you would still be able to fetc
18.
by Bogdanovich 11y ago
It's really simple. Each queue is a separate leveldb database on disk. Messages are stored as key/value using incremental ids. Head and tail of the queue are kept in memory and get initialized on startup via db scan.
19.
by Bogdanovich 11y ago
Yes, goleveldb was chosen because it's a ready to use library with a decent write and read performance, and no external non-Go dependencies. It can also be used to store multiple consumers offsets in future. Regarding provided guarante
20.
by Bogdanovich 11y ago
Yes, as id/value with autoincrement key. Head and tail ids are kept in memory and get initialized on startup via leveldb database scan.
21.
by Bogdanovich 11y ago
Reliable fetch is a feature, not a protocol requirement. You can use simple 'get work_queue' command to just get a message, or you can use 'get work_queue/open', 'get work_queue/close' - two phase fet
22.
by Bogdanovich 11y ago
You can have large queue sizes (larger than RAM size) and siberite would still consume small amount of resident memory. You basically don't need a separate server with decent amount of memory for it. You can also can get benefit from t
23.
Siberite: A Simple LevelDB-Backed Message Queue in Go(github.com)
77 points by Bogdanovich 11y ago|35 comments
24.
Siberite: a simple, lightweight, leveldb backed message queue written in Go(github.com)
3 points by Bogdanovich 11y ago|0 comments
25.
by Bogdanovich 11y ago
If server is compromised, web app source code would probably change to something else.