10 ms·
There's Just No Getting Around It: You're Building a Distributed System (2013)
- spcelzrd 9y agoI'm going to join ACM just to see what happens. Who even is in this thing?
- davidcuddeback 9y agoI joined ACM several years ago. It took filing charge backs with my credit card company to cancel my membership. Even after canceling, I still get non CAN-SPAM compliant emails from them from which I've found it very difficult to unsubscribe. If you're interested in joining a professional society for computer scientists, software engineers, and electrical engineers that doesn't resort to dark patterns, I'd recommend checking out IEEE. I don't get spam from them and they respected my decision to cancel my membership. I generally find their digital library to be of higher quality as well. My two cents. YMMV.
- spcelzrd 9y agoThanks for the warning. I was serious about joining, so I'm still going to give it a try. I'll use a disposable credit card.
- tostitos1979 9y agoSo .. I'm a professional scientist. ACM isn't a fly-by-night operation. It is very similar to IEEE in terms of stature. In CS, I consider ACM conferences slightly higher tier but this is not a hard and fast rule. Yes .. they do send a lot of material I don't care for. But if you are a student, it is definitely cheap and worthwhile to join. As a professional, you have to make your own call .. I pay for it because I feel the money goes to conferences, student subsidies, etc. (not really charity but I feel like I am paying it forward). You get discounts at conferences but my employer pays for those anyways.
- Jtsummers 9y agoFor what it's worth, I didn't have any issues when canceling my membership. I did get some emails for a while, but those tapered off or were easy enough to unsubscribe from (link in the emails). Regarding auto-charging the CC, just don't let them. There's an option to store your CC credentials and automatically renew (I believe the default was to not store and to not auto-renew), you can either not store them, or not automatically renew, or both. I received a notice in September of every year to renew my membership, with a deadline of October or November. That was a bit nagging, but not terrible. I did find it difficult to unregister from ACM SIGs (Special Interest Groups), had to press on through several screens to get to one that let me unselect them. That was obnoxious, but only resulted in my being a member SIGGRAPH one year longer than I desired and being out $20 or so, interesting reads but wasn't an active pursuit or career-wise applicable topic anymore.
- slavik81 9y agoI found it rather appalling that the IEEE sent me junkmail disguised as a bill—using an IEEE envelope no less. "Payment required" it says on the outside. Open it up, and it turns out they're just trying to sell you insurance.
- shepardrtc 9y agoI've been a member of the ACM for many years and they have consistently impressed me by the professional quality of their publications. They take computer science, and especially computer science education, very seriously. I recommend them to all my professional friends.
- dominotw 9y agoI take ACM queue magazines and chill out in coffee shops during days I don't feel like working. Always fills me with hope and confidence.
- deleted 9y ago[deleted]
- scott_s 9y agoI am a member, and have been since I was a graduate student. Some of the best computer science academic publications are in ACM conferences.
- apeace 9y ago> There are many reasons why an organization would need to build a distributed system, but here are two examples: > - The demands of a consumer Web site/API or multitenant enterprise application simply exceed the computing capacity of any one machine. > - An enterprise moves an existing application, such as a three-tier system, onto a cloud service provider in order to save on hardware/data-center costs. When you've exhausted the capacity of a single machine, typically you don't jump straight to a distributed system. You can scale out horizontally with a stateless application layer, as long as the data storage on the backend can handle all the load. You can also scale database reads horizontally, using read replicas. This horizontal scale-out is not a distributed system, since consensus ("source of truth") still lives in one machine. So I think a better phrasing of #1 would be "When your write patterns exceed the computing capacity of any one machine".
- saryant 9y agoThat's... still a distributed system with all the joys of eventual consistency.
- jdc 9y agoHowever, I do think the general consensus is that stateless/shared-nothing app servers and following something like the 12 Factor App[1] pattern makes things much easier. 1. https://12factor.net https://12factor.net
- saryant 9y agoYes, it does. But just because your storage layer is abstracted behind an API doesn't mean eventual consistency isn't your concern. Take S3 for example. LIST calls lag deletes but exists() doesn't, so exists() could return 404 for a document that's still included in the result of LIST. Plus, all exists() calls go through a caching load-balancer, so you could receive different answers in two subsequent exists() calls. That's just a small subset. There's a good comment here[1] on S3's consistency semantics. Point is, 12FA makes things easier but any time you have more than one computer involved (i.e, always), consistency becomes complicated. [1] https://issues.apache.org/jira/browse/FLINK-5706 https://issues.apache.org/jira/browse/FLINK-5706
- marknadal 9y agoRegarding testing distributed systems. Chaos Monkey, like they mention, is awesome, and I also highly recommend getting Kyle to run Jepsen tests. But we still need more tools on this front, so we built https://github.com/gundb/panic-server https://github.com/gundb/panic-server which integrates with Mocha (and other unit test frameworks) to make it easy to run failure scenarios across real and virtual machines. It has been a life saver for me.
- saryant 9y agoI've been keen to investigate Peter Alvaro's work around fault injection. He's been working on that with Netflix[1]. The tl;dr is that you analyze successful system outcomes and inject failures along those paths to see if they subsequently fail. If they do, you've found a bug. It's the next generation of Chaos Monkey. [1] http://techblog.netflix.com/2016/01/automated-failure-testing.html http://techblog.netflix.com/2016/01/automated-failure-testin...
- itsmemattchung 9y ago> Geographies. Will this system be global, or will it run in "silos" per region? Although I've only worked at Amazon for about a year, I've learned that you should always consider building siloed/regionalized applications—if not, expect major headaches when the service needs to be deployed in multiple environments.
- peterwwillis 9y agoThis is a verbose paper written by a tech bro that over-generalizes "How To Build A Scaling High Availability Web App", but fails to explain how such systems are designed in general. If you're a tech startup and have never worked in this industry before, the very last paragraph is useful. My personal ideal system design is one that you can pick up and drop into a single machine, a LAN, a cloud network, geographically dispersed colocated datacenters, etc without relying on 3rd party service providers. If you go from a start-up to a billion dollar company, you will eventually have offices with their own labs, dev, qa, middleware and ops teams, datacenters and production facilities, and your hardware and software service providers will run the gamut. If you can abstract the individual components of your system so that dependencies can be replaced live without any changes to any other part of the system, you have the start of a decent design. However, nobody I've ever worked for designed their system this way initially, and they made millions to billions of dollars, so there certainly is no requirement that you have a perfect distributed system design for your emoji app start-up.
- d3ad1ysp0rk 9y ago"Mark Cavage is a software engineer at Joyent, where he works primarily on distributed-systems software and maintains several open source toolkits, such as ldapjs and restify. He was previously a senior software engineer with Amazon Web Services, where he led the Identity and Access Management team." What makes him a tech "bro", exactly?
- mmmpop 9y agoYou mean the Oracle VP of Engineering Mark Cavage, formerly of Joyent? Yeah, what a hack, what has he accomplished? Better yet, what have you accomplished? I eagerly await your response.
- programminggeek 9y agoAny time you have something talking to a database, cache, or pretty much anything else you have a distributed system, you just don't know it yet.