#2,547 in Computers & technology books
Reddit mentions of Scalable Internet Architectures
Sentiment score: 1
Reddit mentions: 5
We found 5 Reddit mentions of Scalable Internet Architectures. Here are the top ones.
Buying options
View on Amazon.comor
- Broad compatibility: Fits single screens up to 24 inches diagonal and 18 pounds; compatible with VESA patterns 75x75mm and 100x100mm
- Versatile mounting: Includes desk clamp that attaches to desktops up to 1.8 inches thick and grommet mount that attaches through a desk surface hole up to 2 inches wide and 1.75 inches deep
- Comfortable working: Offers 8 inches of height adjustment and 19 inches of extension to reach across large workstations; customize how you work or collaborate with 360 degrees of rotation and 180 degrees of tilt
- Budget-friendly: Compact monitor arm is perfect for first-time buyers on a tight budget; easily adjusts to your needs with the push of a button and lifting the display; ships fully assembled for quick installation
- Built to last: Extensive quality testing ensures your monitor stays stable and secure; Ergotron products set the standard for quality with a 3-year warranty and expert technical support
Features:
Specs:
Height | 8.95 Inches |
Length | 7.05 Inches |
Number of items | 1 |
Release date | July 2006 |
Weight | 1.0361726314 Pounds |
Width | 0.8 Inches |
Scalable Internet Architectures by Theo Schlossnagle. He was my boss at OmniTI and knows his stuff.
You should start by learning Go, Erlang, Rust and C.
/trolololololololol
Seriously, though, if you're talking about cramming as many users as onto a single machine as possible then node is not your runtime.
Node is great at building things that scale horizontally. It makes it really easy to write realtime, event based code. Node is really good at doing things that involve a lot of network IO since it's easy to do that in a non-blocking way. It's not a great choice for a high scale game server where memory usage is key.
If you want to know more about horizontal scaling patterns (which Eve only qualifies for if you squint a bit), I'd recommend starting here:
http://www.amazon.com/Scalable-Internet-Architectures-Theo-Schlossnagle/dp/067232699X
And looking at distributed consensus approaches, message queues, and bumming around http://highscalability.com/ a bit.
The ones I see most often are The Art of Scalability, Building Scalable Websites, and Scalable Internet Architectures, although I can't say anything personally about them. There's a question on SO that would be useful if it wasn't closed. And there's often good stuff on the High Scalability blog.
I'm not aware of any recent books, though, no. I've started a book about that and some other stuff, but along with not being finished it's probably targeting lower traffic than you're looking for.
http://www.amazon.com/Scalable-Internet-Architectures-Theo-Schlossnagle/dp/067232699X is good, if a little dated now.
Ok, ok, ok. I used to use it in my past jobs. But, in my past three jobs I haven't used it at all. Unix/Linux is the only way I go now; it's faster for development, it scales faster, open frameworks, and there is no cost or vendor lockin.
> You can't run every application on Linux.
Yes you can; if your application is locked into one system the architect needs to be fired.
> ... in a container and not every application is built to scale horizontally. Pretending otherwise is self-aggrandizing masturbation.
If the application is not built to scale horizontally, it needs to be rebuilt; or the architect needs to be fired. This isn't 2005; you don't just throw more resources at it to "scale". You should be able to spin up a new box in a matter of
seconds
and then add that box the the cluster. If you can't, you need to read Scalable Internet Architectures and then appologize to your peers and clients for building such a shitty environment.> To be honest, I'm really reminded of the "rock star" devs pimping ruby. Yeah, you're doing cool shit. Yeah green field implementations are fucking grand. But you don't have to act like a pompous ass about it. You're already doing cool shit and you should be happy, why are you being such a fucking try-hard?
So having an opinion on poor microsoft tech means I'm not doing cool shit or trying too hard?
Oh, and no troll.