How can you choose and apply the right system architecture patterns and frameworks?

Modern software development always tries to avoid a big design upfront approach. Most of the architects are following the KISS approach. But it would not be a good fit if the product is 80% developed and you are trying to add ad-hoc features for the sake of simplicity. I would suggest an approach; Start Simple, Improve Continuously Focus on the Core Problem: Begin with a basic solution that tackles the main issue. Learn from Users: Put it out there, gather feedback, and adapt. Evolve Gradually: Add more features based on what users need. Repeat: Keep improving in small steps, ensuring your software gets better with each iteration.

To my knowledge, we mostly need to design software either there come new requirements or some problems/issues with existing software are raised. First, we're more likely to realize what problem could be solved and understand possible obstacles on the way to good design. Analyze the requirements and restrictions by sketching some architectural UML standard diagrams such as sequence-diagram, activity-diagram, and data model diagram to clarify more in detail in the form of HLD and LLD documentation would be highly recommended.

Certainly, when you have a clear insight in connection with the issues or requirements you're one step closer to the ultimate solution, now it's time to sort out what options could be suitable for your challenge to be solved. if you're hands-on with the subject then you may hand-pick from the experience including some short investigation over relevant technical articles. Depending on the requirements and best-fit solutions, In my experience, I had to opt for a Reactive non-blocking even-driven, cloud-native framework to create an efficient micro-service in which utilizing streaming platforms such as Amazon Kinesis and Kafka (Confluent) takes place highly smoothly declarative. it's been Quarkus supersonic java framework.

Briefly, In my use case creating a bunch of micro-services with less memory consumption, fast startup timing, and less hardware resource consumption even under a massive workload took me right to the Quarkus as a supersonic Java framework which is stunning specifically on cloud-native. Moreover, one of the best breeds of implementation of the Reactive library named Mutiny framework is found which facilitates me in development and deployment with the best practices in both areas.

To make sure the principles are followed, its best to use static code analysis tools as part of your CI pipeline. At the same time if certain architectural rules must be preserved there are tools similar to static code analysers to validate modular/component design to make sure they align with high level design in architecture documentation. Using tooling for this will give good values compared to manual review.

On the way to implementing the micro-service, my team and I were stunned by the beauty of the excellent features of Quarkus in both imperative and reactive development therefore we kept developing more applications being built by Quarkus.