itaifrenkel

14 ms·

91.
by itaifrenkel 12y ago
Interesting. Could you please elaborate?
92.
by itaifrenkel 12y ago
You are right about IronMQ, they are said to have a very strong product. For the record, we haven't actually checked redislabs and cloudamqp either, but since they are based on opensource that is mentioned in the blog post, I added the
93.
by itaifrenkel 12y ago
Sure we have. Kinesis was considered because it was inspired by Kafka, and Kafka is known to work well. The thing is that any distributed stateful service, by design, requires DevOps experience and takes time to manage. We try to stay lean
94.
by itaifrenkel 12y ago
thanks. The Pros/Cons were supposed to refer to the complete architecture setup, and not to the Q component by itself. I can see how that could have been read that way...
95.
by itaifrenkel 12y ago
We are currently not using nodejs streams. The nodejs components are the event dispatchers placing the events in a queue, they do not include much even processing. Most of the event processing is done in Apache Storm. We have also contribut
96.
by itaifrenkel 12y ago
I used Lucid Charts. It felt easy to work with. https://www.lucidchart.com/ http://aws.amazon.com/architecture/icons/
97.
by itaifrenkel 12y ago
Do you have a document showing the results of the Flotilla tests ... how beanstalkd compares with RabbitMQ for example?
98.
by itaifrenkel 12y ago
We haven't done comparative throughput performance. SaaSiness, Low Latency and use case matching was the main concern of choosing the queues. As for throughput, the main concern was for the event stream processing pipeline. Redis and K
99.
by itaifrenkel 12y ago
The event stream processing is probably worthy of another blog post, but to be brief... we try to align all of our API servers (or event dispatchers) to be nodejs and have all of the processing in Storm (java). But reality is a bit more com
100.
by itaifrenkel 12y ago
Your are correct. The sentence you referenced is in the section that describes RabbitMQ without clustering. The next section talks about the tradeoffs of RabbitMQ clustering.
101.
by itaifrenkel 12y ago
OP here... I would be happy to discuss any comments you have.
102.
Comparing Message Queue Architectures on AWS(tech.forter.com)
87 points by itaifrenkel 12y ago|42 comments
103.
by itaifrenkel 12y ago
At Forter (www.Forter.com) a big part is the screening of CVs. HR and RnD work closely to contact only relevant candidates, and when we a CV could be relevant the RnD manager or the lead developer calls the candidate for 15 minutes focusing
104.
by itaifrenkel 12y ago
Were you actually able to get 1ms latency from Kafka? How long does it take an event to enter then exit Kafka?
105.
by itaifrenkel 12y ago
Three days ago I had the most amazing experience playing in playback theater for a room full of (~100) grownups of the autistic spectrum (living in hostels in the community, mostly with high verbal skills). The stories they chose to share w
106.
by itaifrenkel 12y ago
PagerDuty is awesome and so is their android App. We've hooked our entire probing(system test) and code instrumentation through riemann to pagerduty. Each time a developer starts a new branch she can deploy it on the cloud, get into pa
107.
by itaifrenkel 13y ago
How does it work? It doesn't say.