Bearer | Why Hotwire in 2021

Find out why engineering team at Bearer made the decision last year to swap from a React on Rails SPA to a Hotwire application.A bit of Bearer history. We started as a Ruby on Rails heavy team, but as our original product grew, so did the needs of our architecture. Pretty soon, it was incredibly reliant on microservices. For good reasons, too. We were handling over a billion requests a month, we required resiliency as we sat in between our users requests and the outside world. The stack was very diverse to put it lightly. We ran a Rails API, GraphQL, ReactJS on the front-end, and a handful of other services running Elixir, NodeJS, and Rust to name a few. This was compounded by the in-app agents that our customers installed in their applications—which at the time we transitioned away from the product covered PHP, Go, Ruby, NodeJS, and Python. It was quite the engineering burden for a small team. We’ve spoken in the past about how we processed all that data effectively.
Bearer | Why Hotwire in 2021 #ruby #rubydeveloper #rubyonrails #hotwire https://rubyonrails.ba/single/bearer-why-hotwire-in-2021

Nezir Zahirovic

Contractor Ruby On Rails (8+ years) / MCPD .Net / C# / Asp.Net / CSS / SQL / (11 years)

related articles