Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.
What happens after acquisition -
merging backend systems
Jüri Tarkpea
GVP of Engineering
jyri.tarkpea@fleetcomplete.eu
Fleet Complete is a leading global provider of
mission-critical connected technologies for fleet,
asset and mobile workfor...
About Fleet Complete
Rally for market, much like telcos
Cost synergies
Partnerships with OEMs, channel partners
Why acquire?
2000 Oskando established
2006 Ambient Sound Investments
2007 + Connecty (LT)
2007 + Median (EE)
2011 + Track24 (EE)
2012 +...
2000 Oskando established
2006 Ambient Sound Investments
2007 + Connecty (LT)
2007 + Median (EE)
2011 + Track24 (EE)
2012 +...
~ 600 000 total IoT devices in service
= 1TB IoT data per month
Key partners AT&T, Telus, Telstra, T-Mobile, Telia
Mix of ...
Significant common part
Product
Map POIs Events Reports Maintenance Driver behavior
Significant common part
Product
Map POIs Events Reports Maintenance Driver behavior
Product feature bingo
Map POIs Events Reports Maintenance Driver behavior
Feature domains
Geo/Jurisdictions
Product feature bingo
Map POIs Events Reports Maintenance Driver behavior
Hours of Service
Mileage
reimbursement
Time trac...
Break the monoliths
Go service-oriented
Keep feature domains separate
Allow teams to
use what performs the best
use the te...
Build for acquisition
There will be data migration
There will be other teams (+-8h of your timezone)
There will be other t...
Thank you
Modern problems in backend engineering, Jüri Tarkpea
Modern problems in backend engineering, Jüri Tarkpea
Modern problems in backend engineering, Jüri Tarkpea
Modern problems in backend engineering, Jüri Tarkpea
Próxima SlideShare
Cargando en…5
×

Modern problems in backend engineering, Jüri Tarkpea

Modern problems in backend engineering, Jüri Tarkpea

  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Modern problems in backend engineering, Jüri Tarkpea

  1. 1. What happens after acquisition - merging backend systems Jüri Tarkpea GVP of Engineering jyri.tarkpea@fleetcomplete.eu
  2. 2. Fleet Complete is a leading global provider of mission-critical connected technologies for fleet, asset and mobile workforce-based businesses About Fleet Complete
  3. 3. About Fleet Complete
  4. 4. Rally for market, much like telcos Cost synergies Partnerships with OEMs, channel partners Why acquire?
  5. 5. 2000 Oskando established 2006 Ambient Sound Investments 2007 + Connecty (LT) 2007 + Median (EE) 2011 + Track24 (EE) 2012 + AVL Express (EE) 2013 Oskando + Autolog (DK) = Ecofleet 2014 + Altas (LT) History of acquisitions 2002 Fleet Complete established 2016 + IT Mobile (NL) 2016 + Securatrak (AU) 2017 + BigRoad (CA) 2017 + Ecofleet …..
  6. 6. 2000 Oskando established 2006 Ambient Sound Investments 2007 + Connecty (LT) 2007 + Median (EE) 2011 + Track24 (EE) 2012 + AVL Express (EE) 2013 Oskando + Autolog (DK) = Ecofleet 2014 + Altas (LT) History of tech 2002 Fleet Complete established 2016 + IT Mobile (NL) 2016 + Securatrak (AU) 2017 + BigRoad (CA) 2017 + Ecofleet
  7. 7. ~ 600 000 total IoT devices in service = 1TB IoT data per month Key partners AT&T, Telus, Telstra, T-Mobile, Telia Mix of Linux-based and Microsoft technologies All systems started out 10+ years ago 2019
  8. 8. Significant common part Product Map POIs Events Reports Maintenance Driver behavior
  9. 9. Significant common part Product Map POIs Events Reports Maintenance Driver behavior
  10. 10. Product feature bingo Map POIs Events Reports Maintenance Driver behavior Feature domains Geo/Jurisdictions
  11. 11. Product feature bingo Map POIs Events Reports Maintenance Driver behavior Hours of Service Mileage reimbursement Time tracking Security Road maintenance Trucking Man & Van +n EE ✅ ✅ ✅ ✅ ✅ ✅ LT ✅ LV ✅ ✅ DK ✅ ✅ DE ✅ ✅ NL ✅ ✅ US ✅ ✅ CA ✅ ✅ AU +n
  12. 12. Break the monoliths Go service-oriented Keep feature domains separate Allow teams to use what performs the best use the tech they want (within reason) Set goals, don’t dictate the means Nurture team’s own responsibility of CI/CD / QA Build product management network How do you build for that?
  13. 13. Build for acquisition There will be data migration There will be other teams (+-8h of your timezone) There will be other technologies Documented procedures and code Decide on custom solutions All care is for the business, not tech I-wish-I-had-knowns
  14. 14. Thank you

×