4 ms·

A favorite resource: https://learn.microsoft.com/en-us/azure/architecture/patterns/sharding https://learn.microsoft.com/en-us/azure/architecture/pattern... Mic

A favorite resource: https://learn.microsoft.com/en-us/azure/architecture/patterns/sharding https://learn.microsoft.com/en-us/azure/architecture/pattern... Microsofts Azure Cloud Patterns is some of the best documentation out there. It's not Azure centric. It focuses on why you may want to do something and describes the techniques that are commonly used to solve it. It's pretty great.

shortrounddev 4y ago
MSDN is like the Wikipedia of coding problems. You documentation for things that have nothing to do with MS there
beebmam 4y ago
I also couldn't recommend this higher. If you are designing a new application, read these docs. You will almost certainly learn something deeply useful that you'll carry me with you for the rest of your career.
Douger 4y ago
Just want to say thanks for pointing out this resource. Will make for some great long weekend reading!
- andirk 4y ago
  Sometimes I wonder how many other industries allow a worker to stumble upon a document that they then read outside of work, despite the details often being kind of difficult to understand at first, frustrating even, but we do it literally as a pastime, for pleasure. I love that.
revskill 4y ago
The main issue is, i can't stand C# or OOP syntax to illustrate patterns. Why class here ? For God sake, please use simple functions to prove the points.
- cpurdy 4y ago
  I think it only reasonable then for you to show us how to do it in COBOL, Lisp, or some other 1950s programming language.
- yawgmoth 4y ago
  They might supply Python examples if you ask. A lot of Microsoft documentation has Python as well as C# these days.
danjc 4y ago
Never come across this before. The collection of articles one level up from your link is an incredible resource.
sahn44 4y ago
Great resource and very well written articles. I'm always curious how these come to be when done really well. I wish we could generate high quality, useful, correct, internal documentation like this at my company, but I've never figured out how to get that done in practice. The people that know the concepts are not natural/gifted writers, or at least wouldn't be motivated or prioritize doing this. Even if they did, the style/tone/depth would vary greatly. For these msft docs, they somehow achieve consistent tone, depth, and quality/correctness across so many domains and I just don't know how that's achieved.
game_the0ry 4y ago
Super helpful, thanks!

shortrounddev 4y ago

MSDN is like the Wikipedia of coding problems. You documentation for things that have nothing to do with MS there

beebmam 4y ago

I also couldn't recommend this higher. If you are designing a new application, read these docs. You will almost certainly learn something deeply useful that you'll carry me with you for the rest of your career.

Douger 4y ago

Just want to say thanks for pointing out this resource. Will make for some great long weekend reading!

andirk 4y ago
Sometimes I wonder how many other industries allow a worker to stumble upon a document that they then read outside of work, despite the details often being kind of difficult to understand at first, frustrating even, but we do it literally as a pastime, for pleasure. I love that.

revskill 4y ago

The main issue is, i can't stand C# or OOP syntax to illustrate patterns. Why class here ? For God sake, please use simple functions to prove the points.

cpurdy 4y ago
I think it only reasonable then for you to show us how to do it in COBOL, Lisp, or some other 1950s programming language.
yawgmoth 4y ago
They might supply Python examples if you ask. A lot of Microsoft documentation has Python as well as C# these days.

danjc 4y ago

Never come across this before. The collection of articles one level up from your link is an incredible resource.

sahn44 4y ago

Great resource and very well written articles. I'm always curious how these come to be when done really well. I wish we could generate high quality, useful, correct, internal documentation like this at my company, but I've never figured out how to get that done in practice. The people that know the concepts are not natural/gifted writers, or at least wouldn't be motivated or prioritize doing this. Even if they did, the style/tone/depth would vary greatly. For these msft docs, they somehow achieve consistent tone, depth, and quality/correctness across so many domains and I just don't know how that's achieved.

game_the0ry 4y ago

Super helpful, thanks!