Solution Architecture Patterns 0.8 released
It is almost 1 year since I started this project on GitHub to share the knowledge around various solution architecture patterns evolving in the world of enterprise software. I didn’t have any idea of how effective this would be and how this will be accepted by the community a year ago. Reaching 100 stars on GitHub was a dream at that time which I never thought about.
Here we are today. With
- 231 GitHub stars (as of this writing)
- 46 forks
- 4 releases
- 36 solution architecture patterns
It is too early to call these numbers a success or failure since the project is still at the early stages. But these numbers encouraged me to keep on going with this project. The good thing about these numbers is that all these are organic growth. I didn’t spend money on advertising, I didn’t give talks about this on conferences, at least I didn’t write about it like this except one article which I wrote 6 months back.
Today, I’m releasing the 0.8 version of the repository to mark a significant improvement from where we were with the previous release which was 0.3 released 6 months ago. Now we have 3 main categories of solution architecture patterns including
- Vendor Neutral Patterns — These are common architecture patterns that can be used to build solutions for real-world problems in the IT domain. It contains solution architecture patterns that are not restricted to a specific vendor or technology stack. The architectures discussed here can be implemented with multiple vendors as well as with one vendor. But there are no special remarks on a specific vendor in most cases
- Vendor Specific Patterns — These are specific architecture patterns that can be used with the respective vendor technologies to solve problems in the IT domain. These patterns cannot be replicated with a different vendor and these might become invalid with the time because of the changes in the technical directions of those vendors and new releases.
- Industry Specific Patterns — These are specific architecture patterns that can be used to solve problems in specific industries like healthcare, financial, etc. These patterns also do not tie into a specific vendor.
Given below is an architecture pattern mentioned in the “Digital Health Platform Pattern” which proves more relevant at a time like now.
As I mentioned at the beginning of this post, I have started this project with the goal of building an open-source community around solutions architecture discipline and a common ground where people can share their knowledge, ideas, and suggestions. This project is proving the fact that there is a need for such an alliance and it can benefit a whole lot of engineers around the globe who build solutions using the technology.
I would like to share an open invitation to Solutions Architects/ Engineers who works with enterprise software products and solutions to come and join with me to build a wider community around the technologies we build. You can send your contributions to the below GitHub repository link.
https://github.com/chanakaudaya/solutions-architecture-patterns
