react-redux-realworld-example-app VS system-design-primer

You have a working backend, but it is not very interesting without a frontend. Let's go ahead and install a React + Redux frontend that will serve as a UI:

This is the React + Redux frontend project, and for Spring Boot I'm not sure what your prospective company uses to interfact with the Database, but it's normally JPA, therefore this Spring Boot + JPA project is a good start.

Since you mentioned you want Redux: I found this sometime back: https://github.com/gothinkster/react-redux-realworld-example-app

Did you use create react app to build your app? It take a lot of the pain away from learning as there are a lot of sane defaults configured in. If you specify Typescript (an option for create react app) it’s a lot closer to Java than vanilla JS, also helps you write clearer, more typesafe code. Perhaps look at some existing smaller projects using React, there are some good real world examples for a heap of languages on gothinkster including react, but that might be overwhelming with redux as well which is a whole other part of a UI app.

However although their React+Redux example is perhaps the most popular one, it's not currently maintained. Instead, this maintained fork is recommended on their list. It's not in TypeScript, which today's projects should normally use, but I guess it's OK for beginner to study

✅ 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