@jmoiron @inconshreveable different parts of "one system" scale differently b/c have different costs, complexities, deps eg. ALU vs FPU or RAM vs CPU
@jmoiron @inconshreveable heterogeneity is a big perf problem even inside a processor, but the Nemonolith the model looks a lot like my "process"
@jmoiron My #GothamGo talk was going to be about this :( I'll hopefully still get it out there in the form of a #Golang NYC Meetup talk
@jmoiron One of the reasons I think it's caught on in the microservice world so heavily; it's distsys (or turtles) all the way down
@jmoiron Cleanly separated interfaces upfront (designing non-distsys like distsys) is one of the knock on effects of using channels to make pipelines
@jmoiron The Nemonolith (https://t.co/HUDFWLJxNY) by @inconshreveable is interesting but I wonder how many distsys problems loopback actually avoids
@jmoiron Gutted I wasn't able to give my talk at #gothamgo yesterday. Feeling a ittle better today. Looks like the event was a real blast!
@jmoiron @_peggyli i don't think it was hers, sorry! she doesn't know what it is either. thanks for asking
@jmoiron @peterc latest golang weekly sponsored post from datadog has 'underdog.io' under the blurb (link is right though)
@jmoiron @rf @kisielk i also like the approach of dep updates getting pushed through code review, just highlighting that the focus is different
@jmoiron greenkeeper.io shows how different the philosophy is towards dependencies in the #JavaScript community vs the #Golang community
@jmoiron RT @clofresh: The scalability of a database is inversely proportional to the niceness of its website