<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Liron Schliesser on Medium]]></title>
        <description><![CDATA[Stories by Liron Schliesser on Medium]]></description>
        <link>https://medium.com/@schliesser.liron?source=rss-dc15bb52cb4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xUwl5lHhftGmVA6vXzwbsw.jpeg</url>
            <title>Stories by Liron Schliesser on Medium</title>
            <link>https://medium.com/@schliesser.liron?source=rss-dc15bb52cb4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:13:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@schliesser.liron/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Navigating the Driver Portal Migration: A Technical Odyssey]]></title>
            <link>https://medium.com/gett-engineering/navigating-the-driver-portal-migration-a-technical-odyssey-f2b06f9883e1?source=rss-dc15bb52cb4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2b06f9883e1</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[gett]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Liron Schliesser]]></dc:creator>
            <pubDate>Mon, 24 Jun 2024 09:37:13 GMT</pubDate>
            <atom:updated>2024-06-24T09:37:13.053Z</atom:updated>
            <content:encoded><![CDATA[<p>In September 2023, news broke that Gett had secured the Israel Airport Authority (IAA) tender, an achievement that generated considerable excitement both within the company and in the media. However, the initial celebration quickly gave way to the practical realities of meeting the tender’s stringent requirements. Product managers and operations personnel immediately began outlining the new capabilities the system would need to support, with the Driver Portal playing a pivotal role in many critical workflows. It was clear that the portal would need to meet Gett’s highest technological standards for reliability, availability, scalability, and monitoring.</p><p>As highlighted in <a href="https://medium.com/gett-engineering/driving-transformation-getts-driver-portal-migration-journey-6ea9a55d99dc">the first part of this series</a>, the Driver Portal ecosystem required improvements to fully meet the standards we have for Gett’s platform. Recognizing this, in October 2023, the R&amp;D management set a clear goal: deprecate the existing system and transition to Gett’s state-of-the-art infrastructure just in time for the project’s rollout. Only through a complete migration could we attain the desired technological standards.</p><p>As we began planning the roadmap for this ambitious project, we anticipated numerous unforeseen challenges in the coming months. To mitigate potential delays, we prepared for the possibility that the migration might extend beyond our planned timeline. Thus from the outset, we actively implemented the necessary features in the legacy system as a backup solution, ensuring we could meet the IAA tender requirements regardless of migration progress.</p><p>Despite the challenges, the team executed the migration within an impressive five-month timeframe, concluding ahead of schedule. This rapid turnaround was achieved while simultaneously delivering the functional requirements for the IAA tender, ensuring that both the migration and the new capabilities were ready for the early 2024 launch.</p><p>Let’s now dive into the details of the endeavor !</p><h4><strong>Code base migration</strong></h4><p>The migration process started with a comprehensive identification of all services utilized by Gett Drivers and Gett Israel Operations personnel. Each service’s code base was meticulously analyzed to identify its dependencies, including other services within the Driver Portal ecosystem, services from the different Gett R&amp;D teams — located in a different AWS account, external third-party applications (such as SAP and Salesforce), storage solutions (like databases and S3 buckets), and AWS-specific services (such as Lambda functions and SNS/SQS).</p><p>Below you can find schematics for a service-centered diagram and for an illustration of a complete system architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FajdA-zsXa9Nm12S" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/0*EhWop873x88rtWO2" /></figure><p>Once the system architecture diagram was clear and understood, namely each and every application belonging to the Driver Portal ecosystem, we forked the relevant GitHub repositories into our main R&amp;D account, adapting the code to run as any other R&amp;D service at Gett. For that purpose, numerous key modifications had to be implemented, to name a few:</p><ul><li>all secrets were moved into the <strong>secure storage</strong> used by Gett platform</li><li><strong>environment variables</strong> were transferred to a dedicated repository to enable seamless deployment to testing and production environments</li><li><strong>golang version</strong> of the micro-services was updated to a common standard</li><li>API requests relying on Gett’s public API were replaced with <strong>direct calls</strong> eliminating the need for authentication/authorization mechanisms which were previously required for inter-VPC communication</li><li>new <strong>docker files</strong> were created for efficient deployment via dedicated CI/CD pipelines.</li><li>we switched over to <strong>Kubernetes for container orchestration</strong> ensuring automatic scaling and efficient pod management; pre-migration, each service was deployed at all times on 2 different EC2 instances for redundancy purposes</li></ul><p>This collaborative effort between the infra and driver portal teams spanned several months. Once the services and their dependencies were ready, we began the testing phase.</p><h4><strong>Testing strategy</strong></h4><p>At this stage, our focus was on validating the application code along with the recent changes done in the code migration step, so we maintained the same storage and AWS related components to ensure consistency — facilitated by a VPC peering connection between the two AWS accounts. Needless to say that since the data being manipulated was the same, the services were expected to display and behave exactly as in their legacy version.</p><p>The URL domains of the migrated services were initially shared with a restricted group, including IL Ops personnel, QA engineers, and product managers. From here on we entered an iterative process of debugging every possible feature/scenario to validate the new applications until all issues were resolved.</p><p>Below you can find some of the main technical problems we encountered :</p><ul><li><strong>missed external dependencies</strong>: such as Google Sheets documents and static files hosted on S3 which weren’t initially identified</li><li><strong>missed request headers</strong>: when we stopped using Gett’s API interface, certain built-in headers in the existing process were overlooked, breaking specific flows, which we then had to include into our direct API calls to restore functionality</li><li><strong>shortage of logs</strong>: as some functionalities broke, we had to add extensive logging to trace and identify the sources of problems</li><li><strong>resource constraints</strong>: necessary logic re-implementation to meet pod’s CPU and memory constraints in Kubernetes to ensure services operated efficiently within the new environment</li></ul><p>For services requiring real user traffic, such as the call center management service, we employed canary deployment, redirecting a small percentage of traffic (typically 10%) to the new application for a predetermined period of time (typically 1 hour). By integrating appropriate monitoring and logging tools, we quickly identified and resolved any issues.</p><p>Once the Driver Portal and its dependencies were validated, we opened it to beta users (a select group of Gett drivers) to gather feedback and increase real-world exposure.</p><h4><strong>Monitoring and alerts</strong></h4><p>Legacy services lacked any type of monitoring and alerting, instead they relied on a data analytics dashboard that exposed the raw tables information, allowing IL Ops personnel to debug the application behavior to some extent. Additionally, certain actions and errors emitted events that could be queried through the data analytics interface.</p><p>To align with Gett’s best practices, we made databases available only to the selected personnel outside the R&amp;D department that is required to operate the system, deprecating the existing data analytics interface. Additionally, we implemented high-quality monitoring and alerting mechanisms, improving internal logging and creating alerts based on metrics such as error rate, Apdex, web response time, and throughput, as demonstrated in the example below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sPvnSjlFc9GOPQTG" /></figure><p>The events being emitted by old services were migrated into Gett’s event pipeline, which can be consumed by visualization tools like Grafana and Mixpanel. This allowed us to deprecate the SNS/SQS implementation previously in place, streamlining data handling.</p><h4><strong>Storage migration, optimizations and rollout</strong></h4><p>Confident that the application layer was functioning correctly, we proceeded to the final step of the migration: transitioning the data storages (RDS and S3).</p><p>The databases were migrated into our AWS production cluster with minimal downtime for users during a pre-scheduled nightly maintenance window. Post-migration, we established robust monitoring and alerting for the newly migrated databases, tracking CPU utilization, free storage, database connections, and long queries through performance insights.</p><p>Analyzing a month’s worth of data on pod memory usage and database metrics allowed us to scale down instances to optimal sizes, not wasting unnecessary resources. Moreover, by identifying the most expensive queries, we were able to optimize the data structure through indexing, for greater performance and reduced cost. Later on, we were able to estimate our actual cost reduction, decreasing AWS expenses by 80%, from $100k to $20k annually.</p><p>With the migrated services already supporting back-office operations, we gradually rolled out the Driver Portal to a larger driver base, moving from beta users to full scale in under a week! Careful traffic analysis on legacy EC2 instances and databases allowed us to safely shut down all old infrastructure, and so completing the transition.</p><h4><strong>Project Outcome and Future Directions</strong></h4><p>The migration project not only met its immediate objectives but also brought about significant improvements across the board. By integrating the Driver Portal ecosystem into Gett’s unified R&amp;D infrastructure, we enhanced reliability, availability, scalability, and monitoring. The project enabled streamlined code management, automated deployment processes, and optimized resource utilization, which collectively reduced overhead costs and improved operational efficiency. Additionally, the migration facilitated better monitoring and data integration capabilities, empowering data-driven decision-making and enhancing the customer experience.</p><p>As part of the R&amp;D infrastructure, we also enjoy easy access to various other resources, including well-maintained and highly available testing environments, built-in Continuous Integration (CI) pipelines for unit and integration tests, as well as Role-based access control (RBAC) for effective user access management.</p><p>One of the critical improvements was the optimization of our global firewall. Initially, the firewall was handling a significant number of inter-VPC sessions across different accounts, which strained its resources. This strain often resulted in database requests taking up to five times longer, potentially slowing down the applications. By eliminating inter-VPC connections, we reduced the overall session load by approximately 85% (from an average of 20k to 3k, as illustrated in the image below). This change significantly improved performance and reliability across our systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/0*Dvfov08OEcXG1Mjg" /></figure><p>The successful rollout of the Driver Portal also demonstrated its potential as a platform for innovation and swift implementation, as it was initially intended to be. A couple of months after the completion of the project, during Gett Hackathon 2024, it already served as a stage for exciting new features conceptualized by visionary Getters, showcasing the portal’s potential for rapid yet meaningful development.</p><p>As other Gett business units outside of Israel learn about the potential of this renewed product, projects such as the revival of the UK Driver Portal suddenly make sense, and are starting to take shape. This ongoing drive for improvement and consolidation underscores Gett’s commitment to technological excellence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2b06f9883e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gett-engineering/navigating-the-driver-portal-migration-a-technical-odyssey-f2b06f9883e1">Navigating the Driver Portal Migration: A Technical Odyssey</a> was originally published in <a href="https://medium.com/gett-engineering">Gett Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Driving Transformation: Gett’s Driver Portal Migration Journey]]></title>
            <link>https://medium.com/gett-engineering/driving-transformation-getts-driver-portal-migration-journey-6ea9a55d99dc?source=rss-dc15bb52cb4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ea9a55d99dc</guid>
            <category><![CDATA[gett]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Liron Schliesser]]></dc:creator>
            <pubDate>Mon, 08 Apr 2024 08:05:35 GMT</pubDate>
            <atom:updated>2024-04-08T08:05:35.674Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Setting the Stage</strong></p><p>In the dynamic landscape of transportation technology, adaptability is paramount. So when faced with the challenge of aligning Gett’s Driver Portal ecosystem with the company’s broader R&amp;D infrastructure, a migration project was not just an option — it was a necessity. As an integral part of Gett’s R&amp;D Engineering, the Driver Portal team embarked on a transformative journey to enhance reliability, scalability and efficiency. This article marks the beginning of a multi-part series, shedding light on the context, challenges and outcomes of this amazing teamwork effort.</p><p><strong>Background and Context</strong></p><p>Arriving at Gett in February 2023, my role initially involved leading the R&amp;D Billing Backend Team. However, in September of that same year, I assumed leadership of the Driver Portal Fullstack Team. This transition coincided with significant organizational hurdles, including the departure of a key developer in the team, and a lack of comprehensive documentation for the Driver Portal ecosystem — a network of ten microservices responsible for various functionalities, including: driver account management, commission plans, car branding updates, generation of monthly driver summary statements and a call-center management service. Below you can find a schema demonstrating how a driver accesses the portal from within Gett Drivers App.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LZH_pVti8KWh73zX" /></figure><p>In a broader organizational context, the Driver Portal team was historically aligned with Gett’s Israel operations, reflecting the traditional development focus on operational needs. This alignment resulted in the team’s being a part of the Operations department, rather than the Systems department where R&amp;D personnel primarily operated. As a matter of fact, it led to the existence of another system in maintenance mode for the UK, and previously, one for Russia, which was shut down along with our Russian line of business. This division resulted in disparate tools, infrastructure, and processes, hindering seamless integration with Gett’s overarching R&amp;D structure, characterized by its continuous learning, growth and improvement over time.</p><p>The technical disparities were obvious from the very start: the Driver Portal code resided in a separate GitHub account, and its AWS cloud infrastructure operated in a different cluster from that of Gett’s Production R&amp;D AWS account, lacking the support enjoyed by the broader R&amp;D domain, with dedicated DevOps/Infra and DBA engineers responsible for its smooth operation. And the disparities extended beyond the technical aspects, encompassing procedural misalignments as well, as the Driver Portal product management function wasn’t integrated properly either.</p><p>Finally, and to complete the bigger picture, Gett had just secured a significant victory by winning the Israel Airport Authority (IAA) tender, set to launch in early 2024. As part of the agreement, Gett would provide exclusive taxi services from Ben Gurion Airport to destinations across Israel while aligning with standard practices observed at international airports worldwide. At its core, the tender aimed to address longstanding challenges in the taxi industry, particularly concerning passenger safety and fare transparency.</p><p>As product management worked through the requirements of the IAA tender, the pivotal role of the Driver Portal in facilitating crucial flows was immediately recognized, including:</p><ul><li>Driver registration for IAA plans: all drivers, Gett and non-Gett drivers, would need to enroll in the ride plan of their choice via the Driver Portal</li><li>Handling IAA fee payments for non-Gett drivers during checkout step by facilitating the upfront payment for their airport pickup rides</li><li>Future order registrations, mandating all upcoming rides to be pre-registered in the system to ensure smooth access for drivers to the airport premises</li></ul><p><strong>Challenges and Drawbacks</strong></p><p>The existing setup posed multifaceted challenges. Code management complexities were compounded by over a hundred GitHub repositories, many of which were deprecated or lacked clarity regarding their relevance. Instances of deploying development branches to production highlighted the absence of robust deployment procedures.</p><p>Furthermore, the microservices operated on individual EC2 instances without auto-scaling capabilities or disaster recovery protocols, leading to manual intervention for service restarts and heightened operational risks. Shared RDS databases exacerbated performance issues and inflated infrastructure costs, while inadequate monitoring and alerting mechanisms impeded timely error resolution.</p><p>Integration hurdles with other R&amp;D services necessitated post-production testing, limiting agility and increasing development cycles. In the illustrated schematic provided below, an instance of the Driver Portal is accessing driver information from the Driver Service — this interaction entails additional authorization headers, along with interfacing through Gett Public API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4RuSXvKs1QltvtLm" /></figure><p>From a business/tech support perspective, all event data were collected but stored separately, hindering their accessibility for generating the required dashboards for daily operations and data-driven decision-making processes.</p><p>And so it became evident that the system in question could not exhibit the same level of reliability, availability, scalability and monitoring as other components within Gett’s system, and served as a great justification for the underlying investment, as well as its urgency: the only dependable course of action involved a complete migration of the entire Driver Portal ecosystem, ensuring its alignment with the modern technological framework of Gett’s R&amp;D department.</p><p><strong>Project Impact</strong></p><p>Despite numerous challenges, the migration project yielded transformative outcomes. Five months of collaborative efforts, involving diverse stakeholders ranging from developers to project managers, culminated in the successful completion of the migration ahead of schedule. While the immediate benefits for the IAA tender were evident, the project’s impact transcended its immediate objectives.</p><p>By integrating the Driver Portal ecosystem into Gett’s unified R&amp;D infrastructure, the project elevated reliability, scalability and efficiency across the organization. Streamlined code management, automated deployment processes, and optimized resource utilization not only enhanced operational efficiency but also reduced overhead costs. Moreover, improved monitoring and data integration capabilities empowered data-driven decision-making and enhanced customer experience.</p><p>In the forthcoming continuation part of this series, we will delve into the technical intricacies and challenges encountered during the migration journey, offering insights into our methodology and lessons learned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ea9a55d99dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gett-engineering/driving-transformation-getts-driver-portal-migration-journey-6ea9a55d99dc">Driving Transformation: Gett’s Driver Portal Migration Journey</a> was originally published in <a href="https://medium.com/gett-engineering">Gett Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>