A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."
Here are all of the resources mentioned by Deconstruct 2017 speakers, along with who recommended what. Please post a comment if I missed something or have an error!
It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.
This is a list inspired by some of our current or potential lines of work at the World Bank Innovation Labs. The “Innovations in Big Data Analytics” program helps to strengthen the World Bank capabilities to effectively use big data in its operational and strategic work.
We are always looking for great Data Scientists. If you can solve any of these [using open software], you'll be heads down helping us from day one. Email us to brunosanchez@worldbank.org
(This list is updated frequently).
We are building an open stack to process nightly data from satellite and query light output from all known villages. Currently we are doing 20 years of nightly data for 600,000 villages in India.
(A book that I might eventually write!)
Gary Bernhardt
I imagine each of these chapters being about 2,000 words, making the whole book about the size of a small novel. For comparison, articles in large papers like the New York Times average about 1,200 words. Each topic gets whatever level of detail I can fit into that space. For simple topics, that's a lot of space: I can probably walk through a very basic, but working, implementation of the IP protocol.
Questions about Distributed systems by @tsantero.
| Turning The Design Clock Back | |
| Object-oriented design principles haven't had the effect we hoped for. The | |
| SOLID principles are excellent design guidelines, but experience shows that | |
| programmers find them difficult to follow. What do we do about this? | |
| Surprisingly, the Structured Design literature of forty years ago contains | |
| compelling solutions to many current design problems. They're simple and easy | |
| to understand, but were lost in the noise as OO rose to popularity. We'll | |
| reinterpret these simple design ideas in a modern context, finding that many of | |
| our most promising new design ideas resemble them. Rapid web application |