Driving cost efficiency while ensuring zero downtime and a performant microservices architecture (MSA) for an automotive OEM.
The problem.
A leading Korean automotive OEM needed to support its Connected Vehicle program with a highly available and performant microservices architecture (MSA). The primary goals were to achieve zero latency or downtime, minimize operational overhead costs, and meet the organizational mandate for using commercially supported software in production environments. The existing commercially supported Apache Kafka® solution proved too costly and complex, requiring extensive training and leading to low levels of engineer engagement and slow feature development.
Overview.
Background.
- Leading Korean automotive OEM
- Connected Vehicle program required a highly available and performant microservices architecture (MSA)
- Software Engineers leveraged to complete the task
Requirements.
- Zero latency or downtime
- Minimal Operational overhead costs.
- Organizational mandate requires commercially supported software in production environments
Initial actions and results.
A commercially supported Apache Kafka® version was initially selected & several challenges persisted
- Apache Kafka® complexity required extensive training for the Software Engineers to utilize the commercially supported Apache Kafka® version, resulting in an unacceptable time to develop new features & a low level of engineer interest due to Apache Kafka® complexity
- Operational Overhead was too high due to the costs of commercial support, combined with resource provisioning inaccuracies
New capabilities.
- Apache Kafka® self-management & engagement capabilities
- Partition distribution monitoring among brokers
- Standardized Apache Kafka® architecture tailored to connected vehicle needs
- Change Data Capture (CDC) database & live migration support
Final outcomes.
- Lower Total Cost of Ownership
- Fully Engaged, More Efficient & Happier Software Engineers
- Zero Downtime During & After Migration