THOUGHT LEADERS
Assembling a Connected-Car Using MicroServices When it comes to connec ng drivers and technology, the auto industry has a longer and richer track record than any other
•
•
Con nuous Integra on and deployment: Features that are added to a service must be visible at once, so that compa bility with other services can be tested automa cally Code quality: The same code is used in different projects. So the demands on so ware code quality and genericity have increased
What are MicroServices? Over the past decade, most applica ons were deployed using monolithic architecture design principles. This means in an applica on all modules, libraries, and inter-dependencies that exist in a single code base is deployed and,
Ragu Sivaraman Founder MacMetry Ragu Sivaraman was earlier instrumental in launching MacTrac, a two wheeler tracking product that augments a rider, a Dealer and/or Fleet provider to manage and monitor motorcycles in real me using tracking device, mobile app and a cloud hosted repor ng solu on.
If a Connected Vehicle could talk, it will say “AV, you complete me!!” Welcome the Connected Autonomous Vehicle world (CAV) where the Connected Vehicle is all about supplying useful informa on to a driver or to the Autonomous vehicle to help make safer or more informed decisions. CAV has high demands on the exchange of data and files between the connected car on the road, and a variety of scalable and agile services in the backend. This results in a so ware services life cycle where in which the depreca on and deployment of new services must happen on a frequent basis. To solve these upcoming challenges, a scalable and flexible architecture is required. Choosing Microservices as an architectural paradigm will enable us to achieve scalable and agile CAV backend that provides with increased opera onal efficiency and code quality.
CAV-Architecture Building Blocks PG.12 | Smart Automo ve | Mar - Apr 2018
sector. Although turning “connected car” into a significant revenue generator has remained sketchy, its role in the AV (Autonomous Vehicle) world is pivotal and will make the car safer, faster, and more efficient. Furthermore, virtually all autonomous vehicles will require connec vity to ensure that their so ware services and data sets are current. While the CAV has been the most prominent example of IoT these days, the cars as such are increasingly becoming so ware driven and the real cloud based IoT developments in the auto industry are happening behind the scenes. OEMs or the solu on provider must address the complexity of behind the scenes so ware development requirements with IoT centric use cases in mind. Some of the key points include: • Scalability: Some so ware components are more o en used and/or more resource intensive than others, resul ng efficient ways to replicate specific components necessary • Loosely Coupled: Components in major so ware solu ons can quickly become outdated. So it is important to find a way of exchanging a component easily without affec ng other components • Reuse: Many projects use similar so ware features to work within the cloud. So a set of standard services used among mul ple projects must be iden fied
importantly, scaled as a single unit. This architecture concept created a significant impediment in the emerging IoT world. For ex: If a small piece of the applica on needs a change, the whole applica on has to be compiled, tested and deployed again. This means that all parts of the applica on have to undergo the so ware development process even though most of the modules don’t experience any changes. This comes at big costs taking manpower, me and IT resources and in most cases lead to delays. In addi on, a monolith makes it difficult to ensure: • Scalability • Be Highly Available • Agile • Con nuous Service Delivery To meet these challenges the applica on architecture must change from a big blob of monolith to an architecture design where complex applica ons are composed
www.telema cswire.net I www.coe-iot.com
