From the team building the #1 most visited automotive shopping site in the U.S.*
We give people the power to reach their destination.
How we went from inconsistent results and infrastructure chaos to a reliable, automated performance regression pipeline for Remix apps. Why We Built This Frontend Platform owns the template layer that all Remix apps at CarGurus build on. When the template ships changes — dependency upgrades, platform improvements, new defaults — those changes ripple across every…
Keep reading
If you are a software engineer perhaps one of the situations below sounds familiar. You’ve just finished a small change to a landing page, tweaked some layout, added a new field to your article section. You run the tests… and suddenly something deep in your CMS integration is failing. Or maybe you want to reuse…
Keep reading
Do I have a favorite standard? Silly question. How could I not? There are so many great ones, each with its own weirdly fascinating story. In a previous job, I spent a lot of time getting to know ECMA-262 (the JavaScript language specification). Lately, though, I’ve been acquiring a taste for encoding standards. Encodings are…
Keep reading
Authors: Mark Gordon and Naman Rathi Problem CarGurus runs hundreds of A/B tests annually to improve every aspect of our marketplace. Because the car-buying journey is complex and touches every part of our platform, we validate product changes through qualitative insights (consumer interviews) and quantitative experimentation (A/B tests). Over the past year, our experimentation workflow…
Keep reading
Introduction: Understanding the Value of Server-Side Rendering (SSR) Server-side rendering (SSR) applications like Next.js and Remix play a pivotal role in delivering substantial value to both CarGurus customers and the company itself. These frameworks offer the ability to present web pages seamlessly on low-performance devices and in scenarios where JavaScript is disabled. Notably, SSR also…
Keep reading
When CarGurus started our Decomposition Journey of monolith to microservices, we recognized the need for clear ownership boundaries and we created an internal tool, Showroom. What we didn’t predict at the time was that Showroom would become more than just a source of truth for ownership and an internal developer portal – it is now…
Keep reading
Original written by Don Mitchell, Cargurus Technical Fellow (ret.). Computers have up to a dozen cpu cores which can all work in parallel (concurrently). It’s hard to write code to take advantage of that concurrency. Additionally, every time code makes a request of an external system, it has to wait a long time relative to…
Keep reading
Originally written by Jahvon Dockery, Principal Software Development Engineer. As you may expect, maintaining a continuously growing distributed system architecture does come with developer experience challenges. For instance, running the services in development may require additional services or you may need multiple backing data stores with realistic data. Also, building and deploying the microservices across…
Keep reading
Back in early 2019, it was clear that our monolith became, well, a little too monolithic. Significant business growth put higher demands on developing against our application. We needed to do more and faster, but we had longer build and deploy times, an uptick in broken workflows and bugs, and increasingly unclear ownership lines which…
Keep reading
From its humble beginnings as a blog for the automotive community, the last 15 years have seen CarGurus’ offerings grow to almost two-dozen independently deployable web applications, supported by roughly 180 backend services and systems. As our product offerings have expanded, our tech stack and system architecture have had to evolve to meet the needs…
Keep reading
Something went wrong. Please refresh the page and/or try again.
