Design Patterns VS system-design-primer

After that, more practice, and then Design Patterns (as in the famous book of the "Gang of Four": "Design Patterns: Elements of Reusable Object Oriented Software"). Here I'd recommend "Head First: Design Patterns" and Java Design Patterns as well as Refactoring Guru (the sites are more reference than course).

For Design Patterns - any resource recommendation that misses Java Design Patterns and Refactoring Guru (also for Refactoring) as well as *Head First: Design Patterns, has failed.

A massive list of design patterns and how they could be implemented (in Java) can be found here.

https://java-design-patterns.com/ has example code for things like object pools that can help with memory management.

Sidenote: I would not really use the GoF Design Patterns book anymore. Too dry. I would use "Head First: Design Patterns" - much more modern, much easier to read, or Refactoring Guru or Java Design Patterns (uses Java, but again, only for illustrations).

Also: https://java-design-patterns.com and https://refactoring.guru/design-patterns

Use either Java Design Patterns or Refactoring Guru. Both resources are far higher quality than yours.

Java Design Patterns

Java Design Patterns - IMO one of the most accessible sites with very easy explanations

A hint: go to Java Design Patterns and go through the patterns to figure what could fit.

✅ donnemartin/system-design-primer: https://github.com/donnemartin/system-design-primer

View on GitHub

I've been giving interviews for past couple of months and this github repo has helped me so much for system design perspective and I can see myself excelling at interviews. - https://github.com/donnemartin/system-design-primer

You'll be on opiod's probably the first 1-2 days, so sleeping should be fine. Everything will be allright, don't worry too much. Just use the time now to prepare for the time after, make sure you go through post-surgery-essentials thread. Once you are out of the OR you won't have the energy to think about those details, so make sure you take that prep serious.

Tooling isn’t architecture. Figure out what you need to handle both personas and volume/throughput and then lay out the capabilities you’ll need. As you lay out points of ingress, egress, consumption you can start to lay out sequences(think in persona and sequence diagrams to express interactions between services). Lastly, evaluate tools that offer some of these capabilities and weigh the trade-offs (there are always trade-offs: https://github.com/donnemartin/system-design-primer).

[1] https://github.com/donnemartin/system-design-primer [2] https://www.teamblind.com/post/My-Approach-to-System-Design-V4SJARdx