Hacker News new | comments | ask | show | jobs | submit login
9.5 Low Latency Decision as a Service Design Patterns (forter.com)
54 points by itaifrenkel on Oct 28, 2015 | hide | past | web | favorite | 6 comments

OP here. If you have any questions I'll be happy to address them.

Really outstanding article, OP. Well done. Slacked to the rest of our engineering team. We're using Google kubernetes to solve some of the fail-over/self-healing challenges you noted, and some of the other ideas as well (proxies, data store fit-to-function, etc.) but there are a couple of things in here that we either hadn't thought of (Nagle algorithm) or needed to be reminded of (timestamps at every layer, the cost of logging/eventing). Thanks for the good lunchtime read.

Thank you for this outstanding article.

Perhaps I missed it, but how exactly do you implement the timestamp logging? Do you use your normal application logging, or some other mechanism?

We use riemann which includes timestamp with each event.

Some of the formatting in the blog post seems to have been lost. Words appear to start mid sentence.

Apart from that, really enjoyed the article. Would love to see more.

thanks. Ill check.

Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact