Skip to main content

Open sourcing the Solutions Architecture Patterns

Solutions Architects (SAs) are the people who convert deep technical knowledge into a format that can be understood by both technical and non-technical people. They are the bridge between product engineers and salespeople. It is so strange that there is no common knowledge base (KB) that has been shared in the open-source community related to solutions architecture.
That was the motivation for me to build such a KB which can be reused by SAs regardless of which technology stack they are working with or promoting. I have started small an initiated a GitHub repository and started contributing solutions architecture patterns which I learn from other people and learn while I’m working as a SA. Today, I have released the 0.3 version of this repository with a set of new solutions architecture patterns. Here is the GitHub repository link for this repository.

chanakaudaya/solutions-architecture-patterns

This repository contains solutions architecture patterns which can be reused to build enterprise software systems. Some…

github.com

The architecture patterns which are discussed here are not my own inventions. Rather, they are common patterns we found day in day out working as Solution Architects. The below mentioned diagram is a sample architecture pattern that is described in the repository.


Figure: Microgateway Multi Data Center Deployment Pattern

This repository is mainly divided into 2 categories. Those are,
  1. Vendor Neutral
  2. Vendor Specific
Vendor Neutral pattern category contains solutions architecture patterns which 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. There are some patterns that utilize specific technologies. But those are very rare.
Vendor Specific pattern category contains solutions architecture patterns that are specific to a given vendor or technology. These architecture are bound to respective vendors and their products. This is an area in which we are expecting some contributions from people working with these vendors since we have not worked with all the vendors mentioned in the repository.
We 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 is still early stages and we have 65+ GH stars and 15+ GH forks as of this writing.
We would like to share an open invitation to Solutions Architects/ Engineers who works with enterprise software products and solutions to come and join with us to build a wider community around the technologies we build. You can send your contributions to the below GitHub repository link.

chanakaudaya/solutions-architecture-patterns

This repository contains solutions architecture patterns which can be reused to build enterprise software systems. Some…

github.com

Labels:

Comments

  1. Bhanu SreeDecember 14, 2019 at 1:06 AM

    Thanks for the Valuable information.Really useful information. Thank you so much for sharing. It will help everyone. Keep Post.
    Microservices Online Training
    Microservices Training in Hyderabad

    ReplyDelete

Post a Comment

Popular posts from this blog

Understanding Threads created in WSO2 ESB

WSO2 ESB is an asynchronous high performing messaging engine which uses Java NIO technology for its internal implementations. You can find more information about the implementation details about the WSO2 ESB’s high performing http transport known as Pass-Through Transport (PTT) from the links given below. [1] http://soatutorials.blogspot.com/2015/05/understanding-wso2-esb-pass-through.html [2] http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-through-transport-part-i/ From this tutorial, I am going to discuss about various threads created when you start the ESB and start processing requests with that. This would help you to troubleshoot critical ESB server issues with the usage of a thread dump. You can monitor the threads created by using a monitoring tool like Jconsole or java mission control (java 1.7.40 upwards). Given below is a list of important threads and their stack traces from an active ESB server.  PassThroughHTTPSSender ( 1 Thread )
2 comments
Read more

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr
3 comments
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte
1 comment
Read more