Posted on

Event-Driven Architectures: 5 Myths

Event-Driven Architecture: Bust or Fact?

Alright, let's face it—there is a lot of content talking about how REST vs messaging APIs and how one is more fir than the other for a microservices architecture design. I wrote a blog post about My journey to learning EDA that highlights what event-driven architecture is. Whether you are new to event-driven architecture (EDA) or have some background with it via dabbling with gRPC, kafka, rabbitMQ, Solace, or whatever messaging API, I am here to share with you 5 claims about EDA that I will be busting or confirming. 

I Will Have to Re-Design My Rest-Heavy Architecture From Scratch To Adopt EDA

MYTH

Advanced event brokers allow for protocol translation within the broker. What does this mean you might ask? Well, it is very common in any software architecture design approach to have a polyglot of protocols and APIs in an application. Whether you are using REST, or different messaging protocols (MQTT, AMQP, Solace, Kafka...etc) you would want your different microservices to communicate with each other. 

Posted on

Why Your DevOps Is Not Effective: Common Conflicts in the Team

The main problem that DevOps solves is how to give businesses the ability to respond to market changes as quickly as possible.

Many companies mistakenly believe, that by trying to get in developers and administrators and implementing a couple of useful tools, they get DevOps. When we consult companies, some of them believe that they are already actively using DevOps.

Posted on

How To Implement Continuous Testing In DevOps Like A Pro

In a decade, the need for software development has evolved drastically. The software has become a key differentiator for companies to gain a competitive edge, especially if your company falls under the SaaS umbrella. From the implementation of traditional processes such as a waterfall in their SDLC, organizations are now transitioning towards Agile in order to deliver software at a faster pace in the market. To cope up with RAD (Rapid Application Development), we have witnessed numerous new approaches such as CI/CD, DevOps, and Shift Left testing to build, develop and optimize software delivery. Even so, trying to maintain both quality and speed is a real challenge, and testing methodologies can either aid or downshift this whole acceleration process. Today, we are going to look into the importance of Continous Testing in DevOps. In this article, I will be talking about what continuous testing is all about. I will also help clear the fog around the myths associated with continuous testing. We will also be touching the challenges involved in continuous testing in DevOps, and best practices to help you execute the continuous testing process as a professional. 

What Is Continuous Testing?

Continuous testing is an end-to-end quality maintenance process in which teams carry out a broad range of automated tests on an ongoing basis. Simultaneously, analyzing various business risks associated with the latest software development and providing the developers with quick feedback. This feedback helps to identify defects and errors at a very early stage and encourages developers to optimize their code during successive stages of the SDLC (Software Development Life Cycle).