Every single book on #Erlang spends 99% of text on reiterating the same basic principles. Most of them are worse than LYSE 1/2
@dmitriid I disagree on this one. Yes, the basic principles are covered, but we cover how by explaining why.
-
-
@FrancescoC One would still expect a book on scalable systems to have less basics (less than 10 chapters) and more scalability (more than 3)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@FrancescoC Setting up, testing, deploying, failover, load balancing, netsplits, discovery of nodes. Not another book on OTPThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@FrancescoC SSL, sockets, working from behind firewalls, flood protection, slow requests, timeouts, sessions, latency etc. etc.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@FrancescoC The book is good as far as I can tell by skimming. It's not really about building scalable systems I'm afraidThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@FrancescoC Remembered this morning: also: logging, debugging, crash dumps, remote inspection, mitigating overflowing mailboxesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@FrancescoC Also: tracing, profiling, various VM options and their impact, securing connection between nodesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@FrancescoC All these could be ideas for a next book perhaps ;) -
@dmitriid I've done two. It is now your turn to write one. Happy to make all the intros ;-) -
@FrancescoC It's high time I did it, isn't it? :) -
@dmitriid Would love your experience documented in a book, as it would be very complimentary to what is out there. -
@FrancescoC I need to find time to finish this first https://dmitriid.gitbooks.io/comparison-of-tools-for-the-erlang-platform/content/ …

-
@dmitriid spend less time on Twitter
-
@FrancescoC Impossible :) - End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.