From Spaghetti to Microservices Architecture

Play From Spaghetti to Microservices Architecture
Sign in to queue


Hopefully, the time when systems were built like monolith and integrated with point-to-point connection is behind us… right? More likely, though, many software applications are developed with a convoluted design that, eventually, hit the wall of maintainability and scalability. In this context, how can a microservice-based architecture help organisations focus on building features that add business value to their applications, without the overhead of designing and writing additional code to deal with issues of reliability, scalability, or latency in the underlying infrastructure? Explore the agility of architecting fine-grained microservice applications that benefit continuous integration and development practices, and accelerated delivery of new functions into production, with the help of Azure Service Fabric. It also presents the Publish-Subscribe design pattern of an enterprise-level service bus built on Azure Service Bus, which guarantees message queueing and delivery, on-premises and in the Cloud. Targeted at software architects and developers, a significant emphasis is posed on demoing the ESB capability available in Azure, how to avoid spaghetti-like intricate architecture designs, and how to design for microservices and API-based applications.




Level 400



Session Type:





Arena 1B



Download this episode

The Discussion

  • User profile image

    I hoped this would be a "Refactoring to Microservices Patterns" presentation -- it's not. Instead, this presentation is mainly on using Azure Service Bus for Pub/Sub operations.

    I haven't seen recommendations on using a service bus in microservices, as most communicate directly. I'm not sure that introducing a service bus improves anything.

  • User profile image

    Hi Tim, you are correct, the ESB is an anti-pattern in micro-service oriented architectures. This session described a path of going from convoluted and monolith applications towards micro-services, passing by the ESB experience. Not all organisations need micro-services, not all organisation can afford a migration to micro-services. The Publish-Subscribe pattern offers a scalable solution for simplifying the integration challenge, and still offer the benefit of (sort of) services, like scalability, loose coupling on endpoints, etc. In addition, an ESB provided queueing and guarantee of message delivery, monitoring and security, and if necessary, state management. All things that Azure Service Fabric offers for micro-services, but can me made available to not micro-services applications too.

    Hope this clarifies the intent of this session, thanks for your feedback.

  • User profile image

    Hi Stefano, Very nice presentation. Where can we download the source code in your demo?

Add Your 2 Cents