DevAssistant

14/05/2026

When should you migrate from Ruby to Go, and when is it better to stick with your familiar stack? Our colleagues have published a piece that breaks down all the arguments for and against. No extremes, just to the point. The link is in the post.

Migrating from Ruby to Go: when it makes sense and when it's a mistake

A Ruby project worked steadily for years, but then the load grew, response time increased, new features became a struggle, and everyone around started saying: "Switch to Go."

Is it worth abandoning your familiar stack? Let's explore this together with Alexander Kirillov, a DevOps expert and mentor in the Evrone DevOps internship program.

Go is faster under load because it compiles to machine code. Built-in goroutines simplify parallel computing. Static typing catches errors at compile time. The final binary is easy to deploy.

But there are trade-offs. The Ruby ecosystem is richer – many things in Go would have to be written from scratch. The language has strict rules: even an unused variable will prevent compilation. There are no classes or inheritance – only structs and interfaces.
Migrating a large project takes months, plus retraining the team.

To make the right decision, assess your actual problems. If current performance is no longer satisfactory – Go might help. If everything runs fine, the switch may not be worth the effort. Start by rewriting one microservice in Go, not the entire project.

And if you want to try Go but find it daunting, we can help with migration – from a test prototype to a full project rewrite.

All the details – which approach to choose, how to test, and whether to start at all – are in the article.
https://evrone.com/blog/from-ruby-to-go

07/05/2026

A non-standard approach always delivers great results. Here is a case study we contributed to.

23/04/2026

When standard solutions just don't fit your needs anymore, sometimes the only way is to build your own. We helped make that happen. Check out the results.

09/04/2026

Today we are talking about the Kinderlime platform, which we worked on.

Need help scaling your EdTech platform? Here's how we tackled this challenge. You can reach out to Evrone with a similar challenge: [email protected]

We at Evrone are used to complex projects, but Kinderlime is a different story.

It’s an app for private daycare centers and preschools in the US. It handles all the administrative work: contactless check-in and check-out, payment collection, staff management, and enrichment programs. In short, everything that helps educators focus on the children instead of paperwork. The service is popular – more than 30,000 centers use it.

The client came to us with an existing Rails application. But the business was growing, the feature set was expanding, and the monolith was starting to slow things down. The goal was to separate the frontend and backend via a REST API and build a new frontend based on ready‑made mockups.

Here’s what we did. We wrote a library on top of Redux and Axios that generates API requests, reducers, and response handling. Without it, we would have had to write the same code hundreds of times. We also built a custom form builder from scratch: support for custom questions, multi‑step forms, and custom fields. We added a CRM with dashboards that collect all conversion analytics. We built an email builder as well – custom campaigns, mailing list management, automated notifications to parents of enrolled children – all while ensuring correct rendering in Outlook, Apple Mail, Gmail, and other clients.

On the technical side: React, Redux, Webpack, Stripe integration, CircleCI for continuous integration, AWS for storage, and Cypress for testing – we achieved 90% test coverage.

In the end, Kinderlime didn’t just get a modernized product; they gained transparent communication and an effective engineering team that integrated smoothly with their product team. The new features and interface helped attract even more customers.

EdTech is never easy, especially at the scale of thousands of educational institutions. If you have a similar challenge – reach out, we’re ready to help.
https://evrone.com/cases/kinderlime

26/03/2026

We are always happy to take part in working on a cool project.

19/03/2026

A cool work tool made by colleagues, we also enjoy using it.

Not putting up with inconvenience, but customizing an existing product to fit our own needs – that's something we know how to do.

At Evrone, we use Yandex.Tracker for time tracking. It's a perfectly good system, but there were a few nuances that, let's say, bothered us. Small things, but in everyday work, they can become critical.

Instead of waiting for the system to be updated, we built our own time tracking tool that integrates with Tracker. No server-side dependencies – just a client-side app that works through Yandex authorization.

Timesheet is a lightweight add-on that pulls data from Tracker and presents it the way we find convenient. No servers, no infrastructure – just a client and Yandex login.

What's inside:

✅Time entries can now be edited
✅ Reports by tasks and projects broken down by day, week, month
✅ Active tasks are pulled automatically
✅ Filters by queue, status, and project
✅ Support for two languages and time zones
✅ Input in minutes by default – which is simply convenient

But here's the thing: we're well aware that Tracker pain isn't just our pain. That's why Timesheet is open source. Any team can take it, tweak it for their own needs, and use it.

All the details are here: https://evrone.com/blog/timesheet

12/03/2026

An interesting project has been posted on Behance — we also had a hand in it. Sharing it with you.

05/03/2026

We enjoy sharing interesting cases that we are involved in.

When a request comes in to develop a complex financial instrument, we always look beyond just writing code – and the txn.pro project is a perfect example. This B2B service helps businesses accept and send crypto payments with optional fiat conversion to avoid volatility. The client returned to us because they knew we could build reliable processes from scratch.

We handled the full MVP cycle: backend, frontend, interfaces, and DevOps. We chose Ruby on Rails but moved blockchain integration into a separate module to avoid overloading the core and allow independent scaling of high-load components. The frontend, built with React and TypeScript, uses the DDD approach – dividing the application into clear layers of responsibility so that new features can be added later without rewriting everything.

The interface deserves a special mention. We presented two concepts: one following industry standards for dense analytics, and a more alternative version. The client chose the first – giving txn.pro its confident, professional look. But our main pride is the logic. We broke down complex scenarios (like setting up 2FA) into clear steps so beginners aren't lost and experts aren't slowed down. We also strengthened data verification before transactions – because in crypto, the cost of an error is too high.

The project is live and running, with our ongoing support. Importantly, the tech stack is classic and transparent – no exotic solutions that could create headaches for the client down the road.
We're proud when people come to us not just with a task, but with trust in a long-term partnership. Evrone is ready to join at any stage – from idea to scaling a finished product.

More on this project: https://evrone.com/cases/txnpro

12/02/2026

More than 7,000 stars and 600+ forks on GitHub confirm that this template has clearly struck a chord with teams building scalable Go services.

Our Go open-source template has surpassed more than 7,000 stars and 600 forks on GitHub – and those numbers are still climbing!

We built go-clean-template to solve a persistent pain: how to start a new service so that a year later, its code hasn’t turned into a tangled labyrinth of interdependencies. Our goal is to provide a foundation that establishes a clear Clean Architecture structure from day one – isolating business logic and keeping the project scalable.

That’s exactly why the developer community has embraced it. Behind every fork is a real project that relies on this template to maintain architectural clarity and development velocity. And our steady stream of updates (over 40 releases and counting!) shows the project is actively maintained and evolving right alongside the Go ecosystem.

This is our contribution to the community – and a tangible example of our expertise in building clean, resilient systems.

→ Explore the template and start your next project with solid architecture: github.com/evrone/go-clean-template

05/02/2026

Cool experience, great case. Thanks to colleagues for the interesting project.

We know how to build a modern media platform. Do you? This case is an example of how the right team can solve multiple global challenges at once.

The publication VentureBeat – a leading technology media outlet with an audience of over 6 million readers – came to us. Their platform, which had been in operation for 20 years, had become outdated and no longer met modern requirements. The task was complex: to expand the capabilities of the editors, reduce operational costs, and ensure seamless work with a massive archive of over 130,000 articles. And all of this – within a tight deadline.

Our audit revealed that the optimal solution would be the headless CMS Contentful as the foundation for future growth. Why Contentful specifically?

✅Headless architecture enables rapid frontend development and a modern user interface.

✅Its flexibility allows editors to easily create and manage content.

✅Compared to the previous CMS, the system offers better scalability and performance.

✅It is a cost-effective solution, especially when combined with a hybrid storage model.

The biggest challenge was migrating the entire article archive. A full import into Contentful would have been prohibitively expensive. We implemented a hybrid model: fresh content was placed in Contentful for speed and flexibility, while the archive was moved to a cost-effective cloud storage, preserving all link equity. This immediately reduced the client's CMS operational costs by over 20%.

The work progressed swiftly: while the new design was being created, custom Python scripts for data validation and automated migration were developed in parallel. As a result, VentureBeat achieved a seamless transition with no data loss or downtime, and gained a fault-tolerant, scalable platform. Now, the publication has not just an updated website, but a ready foundation for future growth.

If you also want a powerful, modern media platform, contact us – we will definitely help.

https://evrone.com/cases/contentful

30/01/2026

As usual, we're sharing an interesting project that we became a part of.

When your expensive GPUs are idling and teams are stuck waiting in line...

Does this sound familiar? A European research lab came to us with the same problem. Their powerful AI video cards were only 10-20% utilized, while multiple teams were manually coordinating access through managers. It was slow and opaque.

Our solution:

✔️ We didn't try to sell them a ready-made product. First, we tested different approaches on their actual hardware and workloads.

✔️ In just 2 months, we built and deployed a unified platform based on Kubernetes and open-source software (creating no vendor lock-in).

✔️ Now their GPUs are a shared, secure, and transparent resource. AI tasks run in parallel instead of waiting in line. Engineers focus on their work instead of manual resource management.

The result: the lab finally got a return on their hardware investment. And all of this runs on their own infrastructure, under their complete control.

Are you looking at your server utilization charts and wondering what to do next? Let's discuss.

https://evrone.com/cases/relab