Skip to main content

New book on Solution Architecture

After years of effort, I am thrilled to announce the release of my second book “Solution Architecture Patterns for Enterprise”.

How did it start?

It all started a few years ago when I decided to share my experiences through a GitHub repository on Solution Architecture. Eventually, it became a popular resource within GitHub and then I decided to write a book with greater details. Here I am today, releasing the book that contains a set of solution architecture patterns that can be used to build enterprise software systems.

Who this book is for?

Solution Architecture is a domain in that people from different backgrounds (majors) come and work. This book can be used as a getting-started guide for novel Solution Architects and a pattern guide for experienced folks. For University Students, this can be used as reference material to learn about Solution Architecture which is hardly taught at universities yet a considerable area of expertise in the software industry.

What is in the book?

This book contains 9 chapters covering the following topics.

  1. Introduction to Enterprise Software Systems
  2. Introduction to Solution Architecture
  3. Building Enterprise Software Systems with Microservice Architecture
  4. Building Enterprise Software Systems with Hybrid Integration Platforms
  5. Designing Enterprise Platforms with Event-Driven Architecture Patterns
  6. Securing Enterprise Software Systems
  7. Implementing Observability for Enterprise Software Systems
  8. Designing Next-Gen Enterprise Software Systems with Cloud-Native Architecture
  9. Industry Specific Architecture Patterns

Prerequisites before reading the book

None. This book can be read and understood by a novice as well as experienced engineers who are interested to learn about solution architecture. People from different majors work in the area of Solution Architecture and it is hard to find organized content to learn about it. This book tries to fill that gap by providing introductions to the basic concepts and then moving into technical details as quickly as possible so that all types of readers are interested in the book.

Where to buy/read?

The book is available through the following platforms.

Front cover of the book Solution Architecture Patterns for Enterprise

Feedback

This is an attempt to share my experiences with the world so that someone in the other corner of the world can learn from them. I’m happy to learn from you as well so that I can improve my understanding and produce better content in the future. I welcome your feedback.

Comments

Popular posts from this blog

How to setup an WSO2 API manager distributed setup with a clustered gateway with WSO2 ELB

In this blog post I am going to describe about how to configure a WSO2 API Manager in a distributed setup with a clustered gateway with WSO2 ELB and the WSO2 G-REG for a distributed deployment in your production environment. Before continuing with this post, you need to download the above mentioned products from the WSO2 website. WSO2 APIM - http://wso2.com/products/api-manager/ WSO2 ELB - http://wso2.com/products/elastic-load-balancer/ Understanding the API Manager architecture API Manager uses the following four main components: Publisher Creates and publishes APIs Store Provides a user interface to search, select, and subscribe to APIs Key Manager Used for authentication, security, and key-related operations Gateway Responsible for securing, protecting, managing, and scaling API calls Here is the deployment diagram that we are going to configure. In this setup, you have 5 APIM nodes with 2 gateway...

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...

How puppet works in your IT infrstructure

What is Puppet? Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to orchestration and reporting. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud. How the puppet works? It works like this..Puppet agent is a daemon that runs on all the client servers(the servers where you require some configuration, or the servers which are going to be managed using puppet.) All the clients which are to be managed will have puppet agent installed on them, and are called nodes in puppet. Puppet Master: This machine contains all the configuration for different hosts. Puppet master will run as a daemon on this master server. Puppet Agent: This is the daemon that will run on all the servers, which are to be managed using p...