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.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
Read more

WSO2 ESB usage of get-property function

What are Properties? WSO2 has a huge set of mediators but property mediator is mostly used mediator for writing any proxy service or API. Property mediator is used to store any value or xml fragment temporarily during life cycle of a thread for any service or API. We can compare “Property” mediator with “Variable” in any other traditional programming languages (Like: C, C++, Java, .Net etc). There are few properties those are used/maintained by ESB itself and on the other hand few properties can be defined by users (programmers). In other words, we can say that properties can be define in below 2 categories: ESB Defined Properties User Defined Properties. These properties can be stored/defined in different scopes, like: Transport Synapse or Default Axis2 Registry System Operation Generally, these properties are read by get-properties() function. This function can be invoked with below 2 variations. get-property(String propertyName) get-property(String scop...
Post a Comment
Read more