biokoda

22 ms·

181.
by biokoda 12y ago
And equally bad at concurrency.
182.
by biokoda 12y ago
That was a year ago and they seem to be doing fine since.
183.
by biokoda 12y ago
Erlang is a pretty big omission in that list
184.
by biokoda 12y ago
Those compression algorithms are not really designed for the type of work lz4/density is. It's basically shooting fish in a barrel. You can find plenty of lz4 benchmarks comparing it to other compression algorithms.
185.
by biokoda 12y ago
Individual actors are individual units of replication. What one actor is writing is concurrent to what another is doing. Read/write calls to an actor are sequential. I'm quite sure this is how other KV stores like Riak do as well.
186.
by biokoda 12y ago
High frequency trading is a real problem and a challenge
187.
by biokoda 12y ago
You are forgetting these banks are involved in high frequency trading. Those are some large engineering challenges.
188.
by biokoda 12y ago
FoundationDB was single process. They had no per-node writer concurrency. The reason why I said sqlite concurrency support is irrelevant is because ActorDB serializes requests anyway. It must do so for safe replication.
189.
by biokoda 12y ago
All distributed databases shard data. If you hammer at only a specific shard area, performance will be limited to the speed of that shard. ActorDB fits a specific data model extremely well. Some less so. But that is the case with all databa
190.
by biokoda 12y ago
SQLite's concurrency support is irrelevant. ActorDB is a sharded by default type of database. The point of ActorDB is to split your dataset into "actors". Actor is an individual unit of storage (a sqlite database). As such yo
191.
by biokoda 12y ago
There is also Emit Cloud which I don't see mentioned in that link http://www.emitcloud.com
192.
by biokoda 12y ago
ActorDB has them
193.
by biokoda 12y ago
ActorDB is quite similar
194.
by biokoda 12y ago
I think the closest cousin is ActorDB http://www.actordb.com/
195.
by biokoda 12y ago
ActorDB is a distributed SQL database with ACID transactions http://www.actordb.com/ and open source. Unlike FoundationDB SQL is a fundamental component and not an addon.
196.
by biokoda 12y ago
You can contact us here: http://www.biokoda.com/home#contact and we can sort this out over email.
197.
by biokoda 12y ago
What version of osx do you have?
198.
by biokoda 12y ago
That's strange. Did it segfault on startup or while running? Was it connected to a server at the time?
199.
by biokoda 12y ago
There is also http://www.emitcloud.com/home
200.
by biokoda 12y ago
There are also way cheaper options out there for the same features. Like Emit Cloud http://www.emitcloud.com/home
201.
by biokoda 12y ago
Sounds like you implemented something similar to http://www.actordb.com/
202.
Why we built ActorDB(blog.biokoda.com)
6 points by biokoda 12y ago|0 comments
203.
by biokoda 12y ago
ActorDB takes this concept much further. It replicates the WAL file (not sql statements). http://www.actordb.com https://github.com/biokoda/actordb
204.
by biokoda 12y ago
An easy to use and powerful alternative is: http://www.emitcloud.com
205.
by biokoda 12y ago
There is: http://www.emitcloud.com
206.
by biokoda 12y ago
Saying you are on your own figuring things out with Erlang is false. The community on the erlang mailing list and IRC channel is extremely helpful, especially for people starting out. Finding Erlang programmers is admittedly more difficult,
207.
by biokoda 13y ago
there are some that do. The so called newSql databases like actordb
208.
by biokoda 13y ago
JavaScript isn't a fad. Node.js is.
209.
by biokoda 13y ago
They had trouble finding/training enough Erlang engineers.
210.
by biokoda 13y ago
Video of talk http://vimeo.com/44312354

More ›