Sai Ganesh

Senior Messaging / Site Reliability / DevOps Engineer with 6+ years of experience supporting enterprise distributed systems, cloud platforms, production reliability, CI/CD, Kubernetes, and event-driven application environments. Recent experience focuses on Solace PubSub+ messaging enablement, broker/platform operations, event-mesh connectivity, Dynamic Message Routing (DMR), Event Portal, application onboarding, messaging observability, and OpenTelemetry-based telemetry export. Strong SRE background across AWS, EKS/ECS, Infrastructure as Code, monitoring, incident response, automation, service reliability, and production operations.

Experienced in collaborating with application teams to enable publishers/consumers, troubleshoot messaging flows, standardize platform onboarding, improve monitoring, and operate highly available enterprise services.

Senior Messaging / DevOps / SRE Engineer - United Airlines

(2024-09)

• Enable and support Solace PubSub+ messaging brokers for enterprise application teams, providing a standardized messaging platform for event-driven communication across distributed airline applications and services.
• Perform Solace application enablement by working with development teams to define and configure messaging requirements including Message VPNs, queues, topics, subscriptions, publisher/consumer connectivity, client access, and environment-specific integration needs.
• Support enterprise Event Mesh architecture connecting distributed applications and messaging domains, helping applications exchange events reliably while reducing point-to-point integration dependencies.
• Participate in modernization and migration initiatives moving enterprise messaging workloads from TIBCO EMS, IBM MQ, and Apache Kafka toward Solace PubSub+, helping establish a common event-driven messaging platform and standardized application-integration model.
• Assess existing TIBCO EMS messaging patterns, queues/topics, publishers, consumers, delivery requirements, connectivity, and operational dependencies, and map them to appropriate Solace PubSub+ constructs for migration planning and application enablement.
• Support IBM MQ-to-Solace migration activities by analyzing queue-based point-to-point integrations, message-flow dependencies, client connectivity, reliability requirements, and target Solace queue/topic/subscription configurations.
• Support Kafka-to-Solace migration and coexistence patterns by reviewing producer/consumer flows, topics, event distribution requirements, application dependencies, and target event-mesh designs for workloads transitioning to Solace.
• Work with application teams to identify migration dependencies, document current-state and target-state messaging flows, define onboarding requirements, coordinate lower-environment validation, and support controlled production cutovers.
• Develop migration approaches that preserve application messaging semantics while transitioning publishers and consumers to Solace, including queue/topic mapping, subscription design, connectivity configuration, security requirements, and failure-handling considerations.
• Support phased migration and coexistence between legacy messaging platforms and Solace, helping reduce cutover risk while application teams progressively move producers, consumers, and event flows to the target platform.
• Validate migrated messaging flows through connectivity checks, message publishing/consumption tests, queue and subscription verification, application health monitoring, and end-to-end transaction validation before and after production cutover.
• Use Dynatrace, OpenTelemetry, logs, metrics, and messaging-platform telemetry to compare application and message-flow behavior during migrations and quickly identify latency, connectivity, routing, or consumer-processing regressions.
• Create migration runbooks, onboarding documentation, rollback procedures, validation checklists, and operational handoff material for TIBCO EMS, IBM MQ, and Kafka workloads transitioning to Solace.
• Collaborate with application, middleware, architecture, networking, security, and SRE teams to resolve protocol, connectivity, authentication, routing, deployment, and operational issues encountered during messaging-platform migrations.
• Configure and support Dynamic Message Routing (DMR) connectivity between Solace brokers so events can be dynamically routed across messaging nodes and environments based on subscriptions and application demand.
• Troubleshoot DMR and event-mesh issues involving broker connectivity, routing behavior, subscriptions, application reachability, message flow, and infrastructure/network dependencies.
• Use Solace Event Portal to support event-driven architecture governance and visibility by documenting/discovering events, applications, schemas, and relationships across the messaging ecosystem.
• Collaborate with application and architecture teams to improve event discoverability and reuse through Event Portal, reducing duplicate event definitions and improving understanding of publisher/consumer dependencies.
• Support the lifecycle of event-driven integrations from application onboarding and non-production validation through production enablement, monitoring, troubleshooting, and operational support.
• Implement messaging observability using OpenTelemetry, collecting and exporting Solace/messaging-related metrics into centralized monitoring platforms for health, performance, capacity, and operational visibility.
• Support OTel Collector pipelines for messaging telemetry, configuring receivers/processors/exporters as appropriate to forward metrics and related telemetry to enterprise observability platforms.
• Build dashboards and alerting around broker availability, connectivity, resource utilization, message-processing indicators, application dependencies, and messaging-platform health using enterprise monitoring tools.
• Correlate messaging metrics with application logs, distributed traces, Kubernetes/AWS infrastructure telemetry, and deployment events to determine whether incidents originate in publishers, consumers, brokers, networks, or downstream services.
• Support distributed tracing and trace-context correlation across REST/API services and asynchronous messaging paths, improving visibility into transactions that cross publisher, broker, and consumer boundaries.
• Monitor and troubleshoot publisher/consumer connectivity, queue/topic subscriptions, message-delivery behavior, client configuration, authentication, network connectivity, and downstream processing failures.
• Support secure messaging-platform operations by applying controlled client access, authentication/authorization practices, environment isolation, certificate/TLS-related operational requirements, and change controls.
• Develop and maintain operational runbooks for broker enablement, application onboarding, DMR/event-mesh troubleshooting, messaging monitoring, common failure scenarios, escalation, and recovery procedures.
• Automate repetitive messaging and platform operations using DevOps practices, scripting, CI/CD, and Infrastructure as Code where applicable, improving consistency and reducing manual configuration.
• Partner with developers, middleware engineers, networking, security, cloud, and SRE teams during production incidents involving complex dependencies between applications and the messaging platform.
• Participate in production on-call and incident response, perform root-cause analysis, restore messaging/application services, and implement monitoring, automation, or process improvements to prevent recurrence.
• Support release and change activities by validating broker/application dependencies, connectivity, monitoring coverage, deployment readiness, rollback procedures, and post-change platform health.
• Apply SRE principles to messaging operations by reducing repetitive operational work, improving observability, standardizing enablement processes, documenting failure modes, and strengthening platform reliability.

Systems Engineer - DevOps / SRE - Amazon Web Services

(2022-08 - 2024-09)

• Supported highly available AWS services and distributed systems with responsibility for production reliability, operational readiness, monitoring, automation, deployment safety, and incident response.
• Served in production on-call rotations, triaging service-impacting incidents, restoring availability, coordinating troubleshooting, performing root-cause analysis, and driving corrective actions.
• Built CloudWatch dashboards, metrics, alarms, and logs for three services spanning more than 50 AWS resources, improving detection and diagnosis of production issues.
• Developed operational automation and internal engineering tooling using Python, Shell, Ruby, JavaScript, AWS CDK, and CloudFormation to r