Suggestions
Sabarish Sasidharan
Senior Director @ HARMAN International (IC Software Products) | Chief Architect | Engineering Leader
Sabarish Sasidharan is a senior technology executive at HARMAN International, a subsidiary of Samsung Electronics focused on connected technologies for automotive, consumer, and enterprise markets. Here are the key details about his current role and background:
Current Position
Sabarish Sasidharan currently serves as:
- Senior Director (Chief Architect), Ignite Automotive IoT Platform at HARMAN International1
- Based in Bengaluru, Karnataka, India12
Areas of Expertise
His work focuses on:
- Automotive IoT platforms
- Connected car services
- Software engineering for automotive applications
Career History
Prior to his current role, Sabarish has held other positions at HARMAN, including:
- Chief Engineer for Connected Car Services
Professional Background
Sabarish appears to be an experienced technology leader in the automotive and IoT space, with expertise in:
- Software architecture
- Connected vehicle technologies
- IoT platforms for automotive applications
His progression to a senior director and chief architect role suggests he has significant experience and technical depth in automotive software systems and IoT technologies.
While specific details about his educational background or earlier career are not provided in the available information, his current high-level position indicates he likely has extensive experience in the automotive technology sector.
Highlights
Microsoft Azure's recent crowdstrike fiasco has come at an inopportune time for Microsoft. Unfortunately for them, because I am seeing this shift happening, companies across industries moving enmasse into Azure. But then that's the nature of software, it's inherently unstable when at scale, unless we have the right checks and balances. So what can we learn from this fiasco? Of course, the learning is to build highly available systems. But then how?
There are many patterns for high availability and disaster recovery. But there is one less known pattern. And it doesn't address these concerns directly. It is called the stamp pattern. And the first I heard this pattern was from Microsoft Azure architects, yes, the same Microsoft. What an irony. Anyways, the stamp pattern is basically a deployment pattern where your system is deployed as stamps. Each stamp is a full fledged system catering to a segment of your user population. So when catastrophe strikes, as it did with crowdstrike, probably only a segment of your user population suffers, depending on the stamp that got affected. For ex, airline A may have been affected but airline B may have still been operational because they are hosted in different stamps.
Note that this is different from disaster recovery or data center based high availability. It's addressing slightly different concerns.
How would you get started with unifying enterprise applications, to have a consistent language and be a coherent suite? How would you go about prioritizing which applications to attack first?
A big bang approach is not ideal, certainly its too much to chew in one bite. A top-down approach, would be to pick applications based on architecture factors of coupling, complexity, overlap etc. This would be my instinct if I were a purist, I think.
Another approach can be to go bottom up, based on data. This could be data from production operations and development process, with more bias to operations. Basically saying, attend to those babies first that cry the most in production.
Theoretically speaking, a meet-in-the-middle approach that uses both facets from above, can also be a method to prioritize. But they may or may not converge. What do you think?
