Serdar Doğruyol's official blog. About Ruby, Crystal, Kemal, Open Source Software, Programming languages and other software development related topics.
When you spend years building and optimizing high-performance backend infrastructure like the Kemal web framework, load testing becomes second nature. You want to know exactly how your service behaves under pressure.
In late 2015, I sat down to write a blog post, Why Crystal?, about Crystal. At the time, the Ruby community was in a state of flux. Developers were increasingly looking at “Language X” (Go, Rust, or Elixir) to solve performance bottlenecks. As a die-hard Rubyist, I made a claim that felt bold yet inevitable: the “X” should be Crystal.
In the world of high-performance web services, knowing your limits is everything. Whether you are building a microservice in Go, a web app with Kemal (Crystal’s most popular web framework), or a high-throughput API in Rust, you eventually face the same question: How much load can this actually handle?
There’s something we don’t like to admit in this industry: code isn’t an asset. It’s a liability.
I am the author of Kemal. Fast, Effective and Simple Web Framework written in amazing Crystal programming language.
As we all know that the web is getting bigger and the information is being consumed really fast. Most of the web applications are in need of realtime updates to supply this demand. To achieve this WebSocket technology is a great fit.
Spoiler: This is an opinionated post about programming languages.
I’ve been itching to write this blog post for a while. Now that Rust is 1.0.0-beta the time has come.
Nowadays building an API is a really common task. If you’re a Ruby developer chances are really high that you’re already using Rails for an API.
As you may already know when you a generate a new resource, model or controller there are bunch of other files that are also being generated for you. Rails has a great way to customize the default generators as you wish. For example let’s assume that we are creating an API for a mobile app. Let call this app sample_api Let’s create a controller for our sample_api