ACMQ offers a  exploration of message queuing systems, asynchronous communication patterns, and event-driven architectures. Through insightful articles and practical guides, readers gain a deep understanding of message queuing technologies such as RabbitMQ, Kafka, and NATS. With ACMQ, readers unlock the power of decoupled, scalable messaging architectures to build resilient, responsive distributed systems.

ACM Queue

Microservices offer an alternative to traditional monolith software development with benefits such as ease of requirements changes and testing, scalability, and support for different programming languages and platforms. However, adopting and sustaining microservices can be challenging due to the novelty of the approach and the lack of understanding in technical and organizational parameters. The decision to adopt microservices should be based on the profile of the organization's application suite, and the value proposition should be made to upper management. The strangler fig pattern is a common approach used to gradually transition from a monolith to microservices. It is important to maintain discipline and adhere to the core principles of microservices during the transformation process.

Challenges in Adopting and Sustaining Microservice-based Software Development

The Initial Decision to Adopt MS Architecture

Converting Existing Monoliths to Microservices

Building New Microservices and Modifying Existing Ones for New Requirements

Operating Microservices and the Architecture

Sustaining a MicroserviceS Approach in the Long Haul