Introduction As an Architect, when we start working on a new application or solution architecture; we study the requirements and see if the solution requires maintaining a specific set of states to support a business use case that requires maintaining a workflow or a state-machine (Event-Driven). Now, this is the tricky part; many would consider … More The Curious case of Stateful Architecture!
During our latest joint webinar with our partner Lightbend, we discussed building future-proof system architecture. This is the link to the webinar recording. We highlighted the importance of architecture flexibility and the role of Reactive Architecture and Cloud-Native architecture in supporting adaptability while achieving resilience and elasticity. We also highlighted the importance of loose coupling … More Why Akka if you have Kubernetes?
Microservices Anti-patterns Microservices architecture has been a dominant architecture style for the last few years, it fits well into the Cloud-native architecture and the agile methodology. The business units are constantly looking for creative ways to support the faster time to market demand; and the Microservices evolution is a big part of that. Lately, many … More MicroSystems Vs. MicroServices
Software Architect, Application Architect, Solution Architect or all of the above? Introduction In the past few years, the information technology and the software development landscape dramatically changed. Advances in computer processors, networking and storage technologies, along with Cloud and mobile; led to the digital transformation evolution and the introduction of plethora of new business use … More The Modern Era Solution Architect
Building Responsive, resilient, elastic, maintainable and extensible systems leads to gaining competitive advantage through faster time to market, improve modern user experience and lower the total cost of building and operating applications. Methods Event driven and message driven architecture Using Asynchronous messaging for inter-service communication and request processing Isolate Everything (Decoupling) Isolate time (eliminate blocking … More Reactive Architecture Quick Reference
Prerequisites For more info on Reactive design patterns such as CQRS, event sourcing, command sourcing and Saga please refer to the references section. Introduction Reactive architecture is an architecture approach aims to use asynchronous messaging or event driven architecture to build Responsive, Resilient and Elastic systems. Reactive Microservices is capitalizing on the Reactive approach while … More Why is Kafka a good fit for Reactive Microservices?
Introduction While I was at API World giving a talk on Reactive Microservices Architecture, it was obvious that, Reactive is gaining a lot of momentum within our technical audience, described by many as a very powerful and game changer set of architecture concepts, design patterns and technologies. However, many business stakeholders still wondering, how this … More The business case for Reactive Architecture
See how a reactive microservices architecture provides the highest levels of responsiveness, resiliency, and elasticity for reactive systems. Full article here.
The Reactive summit is usually focusing on Reactive Architecture and Programming and Fast Data architecture and technologies. This is the conference for someone looking into creating distributed and scalable systems. Lightbend is the host and the leader behind the event and they did an awesome job with the organization and the content. The following is … More The Reactive Summit 2017 Summary Report
Image is Copyright of Lightbend Introduction One of the things we have learned through working with some of our customers that they were at the early stage of the Microservices journey; they started experiencing performance issues and reporting that their Apps are not very responsive anymore. This article will explore inter-service communications as one possible … More Reactive Vs. Synchronous Rest. Interaction patterns in Microservices Architecture