High Scalability

http://highscalability.com/ is one of my favorite blogs for distributed systems.

http://highscalability.com/ http://misko.hevery.com/ Old, and Hevery no longer contributes, but lots of great stuff.

The High Scalability blog [0] complements such courses nicely with curated lists of real world distributed systems and practices. I also found this reading list [1] a great reference. [0] http://highscalability.com [1] https://www.the-paper-trail.org/post/2014-08-09-distributed-systems-th…

HN is a great resource with plenty of important news posted, along with the HighScalability blog [1] and SoftwareEngineeringDaily podcast [2]. 1. http://highscalability.com/ 2. https://softwareengineeringdaily.com/ Other than that, reading the blogs of the various vendors is how I keep up (using Feedly with RSS). The modern projects are Redshift, BigQuery, Snowflake, Azure DW, MemSQL, Clickhouse, YellowBrick with older projects being Vertica, Teradata, Greenplum. It's also useful to follow the "new" distributed SQL projects like CockroachDB, Citus, TiDB, Vitess, Yugabyte.

I used to read High Scalability [1] which has write ups of real-life architectures of lots of the largest web sites. I found it great for learning about different architectures. I'd definintely recommend it as a way to find out about thing like messaging queues, asynchronous vs synchronous processing, etc. On a similar note but more theoretical, my life changed when I learned about design patterns. Martin Fowler's books/site are a good place to start [2]. [1] http://highscalability.com [2] https://www.martinfowler.com/eaaCatalog/index.html

Posts on http://highscalability.com can get a bit hardcore, but there's a lot of great knowledge there.

I've always subscribed to the HighScalability RSS feed: http://highscalability.com

Todd Hoff's High Scalability [1] is a very nice blog to follow if you like this kind of information about real-world stacks. He's been writing it for years. (Caveat: It's a while since I followed it closely.) [1] http://highscalability.com/

Thanks for your comment! > But yeah, also design patterns. And have you read http://highscalability.com/ for architecture ideas? Lots. I would love to have clients in that league (I greatly enjoy scaling, optimization, performance tuning)

Read "Functional Programming in Scala" or any other good book on functional programming to see things differently if you've just stuck with imperative so far. There's also http://iloveponies.github.io/120-hour-epic-sax-marathon/ Read books on concurrency ("Learning Concurrent Programming in Scala" if you carry on with scala) and then you'll find different ways to write performant concurrent code - for CRUD sites or other stuff. I'm not pushing scala rather exposure to other ways of doing things you might not have come across - functional programming, futures, akka, etc. But yeah, also design patterns. And have you read http://highscalability.com/ for architecture ideas?

One good resource is http://highscalability.com. It's got a number of good stories about scaling up and the architectures decisions used therein. There are also a number of articles and papers released by Google, Linkedin and Amazon that are worth reading. One thing that I've found incredibly useful is diagramming application architectures, starting with applications you work on. That plus understanding the CAP theorem

http://highscalability.com is an excellent site to find out about how companies solve their scalability needs.

There are various flavors of cloud. For example Google cloud is mostly app or app based cloud, while AWS is bare metal cloud. I would suggest following this blog - http://highscalability.com which goes into real life architecture of various services and gives behind-the-scene look into cloud and non-cloud architecture, and why they chose to use certain tools or technologies. Core concepts in domains like virtualization, networking, authentication, scalability are the same whether you do it in your own data center or cloud. My advice is to strengthen yourself in core concepts.

http://highscalability.com/ These guys have some really great interviews and articles from time to time. They don't have "news" per se, but the "stuff the internet says on scalability" is pretty great and they interview technical leads for great tech businesses. It is definitely more of a journal format though.

One great resource is the high scalability website/blog: http://highscalability.com

http://highscalability.com/ can give examples of some of the best software architectures

http://highscalability.com/ is also a great blog for those interested in scaling backend architectures, they have great use cases

Forgive me, I'm not an MS person, but is there no opportunity to augment/customise/replace/mix-and-match/etc the ASP.net components? From what I've read on http://highscalability.com and the like, they love to tweak.

This is a great article. On a side note if you want to do this all day and get paid for it let me know :-) Crawls are the first step of a search engine. Greg Lindahl, CTO at blekko.com) has been writing up a variety of technologies used in our search engine work at High Scalability [1]. One of the most interesting things for me is that a lot of the 'frothiest' web pages (those that change every day or several times a day) have become pretty significant chunk of the web from even 5 years ago. I don't see that trend abating much. [1] http://highscalability.com/

I recommend starting from reading the HAProxy site. http://haproxy.1wt.eu/ It has a ton of information about building a load balanced infrastructure using HAProxy. This article helped me too: http://horms.net/projects/has/html/node6.html Read some architecture articles from this site: http://highscalability.com I am also planning on doing that, so once suppliers allow multiple machines I'll write a blog post about I had to do.

this website has some GREAT content: http://highscalability.com/ Many articles focus on bigger, high-profile companies with unique challenges but there are tons of great articles and tips on scaling normal web apps. Check the archives.

This site is probably the best place to start: http://highscalability.com/ I learned most of what I know from working for http://www.gemstone.com

Designing for fault tolerance and scaling out instead of individual node durability and scaling up is, in most cases, a sounder approach. Since the vast majority of applications map well to this case, it makes sense for Amazon to focus on features that assume/assist scale-out. It's easier to design for scale-out than one might think; a great resource to get started is http://highscalability.com. Regarding EBS, I haven't seen the hangup issue you've described. Any data? As for low inter-node latencies, Amazon has an offering that specifically addresses that need: http://aws.amazon.com/ec2/hpc-applications/ Overall, I think Amazon is making a lot of inroads in areas with specific hardware demands. They just launched GPU compute options, and I expect we'll even see SSDs soon.

Check out: http://highscalability.com/ About 20-30% of stuff posted there is worth reading, which is pretty good =)

Running mysqldump on a database the size of CouchSurfing's is a real problem. It's a resource hog. To properly back up a consistent data image you need to use locking, which prevents writes to your database while the backup is running. That causes downtime on every backup, not ideal. Likewise, when backing up 100s of GiBs of data, a simple tar gz is not suitable. More sophisticated strategies need to be used when the data becomes that big. I've found http://HighScalability.com to be a great source of information on building scalable applications.

Here is one, http://highscalability.com/ I bookmarked an AskSlashdot thread on a similar topic a while ago but Slashdot has archived the original thread so here is the google cache entry, look at the O'Reilly books they should answer a lot of your questions. http://64.233.169.104/search?q=cache:eugOZQ5ltGwJ:ask.slashdot.org/art… A final word of caution though, There is no silver bullet. You are your applications best scalability expert.

I don't know about Rails (It's DB library is ActiveRecord, if I recall names correctly) but SQLAlchemy which is Python's big ORM, has support in it for sharding and similar partitioning, etc. When we built sketchcast.com sharding was on the design list and a concern - there were some fantastic articles at http://highscalability.com/ that we used as a basis for some of our design.

https://HighScalability.com is excellent

http://highscalability.com/ is one of my favorite sites.

This is something that can be difficult to learn even if you've been working in the industry (lord knows we've all seen awful practices at various companies in our career). This is probably not popular advice, but of all the places I've worked, Google seemed to have the highest standards for best practices I've seen. I recommend paying attention to Google's best practices, in their blogs, certification programs (like the google cloud developer cert), Coursera courses, product docs, codelabs, style guides, git code, etc. Obviously everything they do won't be a right fit for your company, but it's something to aim for. Enforce code style (be specific and use a linter), and write tests as you go. Try to keep bad code out of your repo before PRs can even be merged. I use Jenkins and git hooks to enforce this for the whole team. Draw up design docs and understand business needs before diving into projects and features. Understanding good architecture and operational principles will make you much more valuable as a developer than your peers. Read the Google SRE book, it's free. Also read http://highscalability.com/ articles and learn from other companies' triumphs and mistakes. Books about architecture include the micro services book by Sam Newman. You may not ultimately be responsible for making these decisions, but demonstrate your value by being able to understand and provide quality feedback to your tech leads and architects. Study and learn about project management…