System Design 101
github.com
System Design 101
1–10 of 45 posts
Re: System Design 101
#2Great sharing
Re: System Design 101
#3Keep up the good work! I feel that your content is bringing a lot of educational value to the tech community. I would even say that the visualisations extend the understanding of tech averse people and leads to more people understanding our rather complex ecosystems.
Thank you
Re: System Design 101
#4ByteByteGo is one of the best YouTube channels I've come across. Really well done content, all explained very clearly.
Re: System Design 101
#5Draw.io is used everywhere. I see it all over in different enterprises...
Re: System Design 101
#6What a little treasure trove of information.
I can see a recent cs grad who’s never built anything benefit immensely from this.
The bigger thing here is that it teaches you the vocabulary for you to then go on and research and form your own opinions etc.
All you need is a sound starting point and this is definitely it.
Kudos to you man.
Re: System Design 101
#7Good Stuff,
About GraphQL, I read that GraphQL is versionless, is it really versionless? If so, how? The link below says you will still need to version but we have some Graphql fans at work and they insist that it does not need to be versioned.
[0] https://medium.com/swlh/no-graphql-doesnt-magically-fix-api-...
Re: System Design 101
#8bytebytego is insanely high quality compared to the geeksforgeeks like website that came before.
Re: System Design 101
#9> Stack Overflow serves all the traffic with only 9 on-premise web servers, and it’s on monolith! It has its own servers and does not run on the cloud. This is contrary to all our popular beliefs these days.
Love this part. I wonder how much of the complexity of microservices and various cloud services are actually adding value on a net basis vs. resume-driven development of some bored backend engineer.
Re: System Design 101
#10Good Stuff, About GraphQL, I read that GraphQL is versionless, is it really versionless? If so, how? The link below says you will still need to version but we have some Graphql fans at work and they insist that it does not need to be versioned. [0] https://medium.com/swlh/no-graphql-doesnt-magically-fix-api-...
It's not versionless per se, but given you ask for the specific fields you want (e.g. user { name }), you don't have to be anal about bumping the version every time a new prop is added to a response, such as in REST, e.g. GET /users/1234
However, if you change the data schema around, like `user` is now `person` or something, or a mutation call changes the required params, there's no magic, you either update the clients, or add versioning.