home icon

Ducati Desmosound and Containerized Microservices

Comments ,(0)

Some of us know that the distinctive sound that the Ducati motorbikes produce is patented. And it is named as 'Desmosound'. It is interesting to see how Ducati originally figured out the optimal tuning of the bike's components - the engine, exhaust and set-up of other parts - to get that sound. What if we apply the same concept to Containerized Microservices?

There is much in common between a Ducati bike and a well-orchestrated system of containers with microservices in them. The objective of optimal performance is common, and so is the complexity of individual components (services) that determine the performance. The need for component compatibility and intricate tuning is so evident that without these the system doesn't even qualify to exist! This comparison and exchange can enable microservices to be measured in a much coherent way.

For containerized microservices, first thing to consider is what would be the single unit to measure - i.e. - equivalent of sound wavelength in Ducati scenario. Second, what would be the characteristics of well-orchestrated and well-oiled containers and microservices that they host, so that we measure them up against the unit? This is an interesting concept.

Lots of content are available online in terms of deploying and orchestrating containers using Docker and deploying microservices on them. Some of the articles even discuss measuring containers' performance, but not in a coherent way. Most of the thoughts rely on infrastructure measurements (Memory, Latency, etc.), while others rely on business function parameters with custom monitoring (Invariables). We must attempt to collate older (infrastructure, performance) and newer (innovative) parameters and dovetail them so that the performance and 'sound' thus derived, is exactly 'Desmosound'. Again, it is not about measuring one Container/Microservice. It is about measuring a system in which many types of containers and associated microservices run seemingly as one entity - that is the 'Bike'.

In such a process, the pre-requisite is to define the 'Bike' itself - i.e. ability to carve out a specific architecture of containers, orchestrations and microservices and their layers. It is a no-brainer that we would see many architectures and combinations.

Silence plays a big part in the patented sound. Amongst the parameters that contribute to the unit will be individual service throughput, time spent by services on being silent, fault occurrence and managed faults, heap memory metrics, elastic scaling performance, message queue length at service endpoints, deploy-consumption ratio and infrastructure resource consumption levels.

In a bike, it doesn't make sense to measure parts one by one. It is futile if you measure the exhaust output, without correlating with the engine sparks or with the transmission system in the context of Desmosound. Similarly, in the microservices world, measuring each such parameter independently will not do, rather we need to arrive at a more cohesive formula. And of course, post deriving the formula, we need to name this 'unit' in line with 'Desmosound'. Any suggestions on name?

{'Ducati' and 'Desmosound' may be registered trademarks of Ducati Motor Holding S.p.A}

About Author

Praveen Kodikkambrath- Head Presales - BAS Microsoft Application Services

Praveen is a Practice Head and Principal Architect with Microsoft Practice, Business Application Services, Wipro Limited. He brings with him 18+ years of experience in development, consulting, delivery, sales and pre-sales, go-to-market activities, CxO and analyst interactions, and innovation and marketing.

His area of expertise has been Application Estate Transformation. He has built transformation services to scale, including management of services and strategy, customer accounts, solutions development, delivery and management of associated people structures.

At Wipro, Praveen handles two practices - Modern Microsoft Applications and Application Remediation and GTM for .NET and BizTalk business. In his current role, he has pioneered a productized solution that addresses all transformation requirements across Microsoft technologies (SharePoint, BizTalk, Dynamics, and Azure).

Read all blogs

Comments (0)

Post Comments