I figured while I'm doing so much prep and learning with all of this and aim to be continuously growing and evolving my skillset, why not translate this repository itself into some form of interactive website built on a microservices architecture.
The frontend could be a basic react app with routes to different UIs for different services.
For example:
One page (http://website.com/leetcode) would be a dynamically-created list of all of the Leetcode problems I've solved so far. Click on one, and it'll run a Spring Boot microservice that compiles and runs the actual Java code, and then the output is displayed on the screen.
If I end up having a bunch of different, say, NATS-based example apps, I could have a universal NATS proxy/gateway service that would take in all of these endpoints and then route them to the correct endpoints, instead of a separate proxy/gateway for each example app.
While it might be a little bit overkill to use microservices, I think it would be a good way to put all of my learnings into practice, and would be a pretty interesting and unique project.
I figured while I'm doing so much prep and learning with all of this and aim to be continuously growing and evolving my skillset, why not translate this repository itself into some form of interactive website built on a microservices architecture.
The frontend could be a basic react app with routes to different UIs for different services.
For example:
While it might be a little bit overkill to use microservices, I think it would be a good way to put all of my learnings into practice, and would be a pretty interesting and unique project.