This is an introductory post to Phoenix, Elixir’s web framework. It is not intended to be a complete guide, but rather a quick primer if you’re interested in Phoenix and have a background in Rails and Ruby. I’ll explore the differences and similarities using a classic blog setup example, although
This article is about StimulusReflex, a new tool to help you bring Rails to the era of the backend-side-managed frontends. I was surprised to see that Phoenix LiveView and following with things like Motion and Sockpuppet use WebSockets to push updates from the server to the client and update the DOM accordingly. Luckily the team at StimulusReflex’s
I think we are quite underpowered when it comes to doing queries on Rails, having this in mind I proposed my opinion on how we could improve this and made a PR. I also wanted to share it here to know what others think and maybe get some traction. The
We usually try to solve performance problems by using #includes to get rid of N + 1 queries but this doesn’t always fix the issue; in fact, it can even create more queries under some circumstances. This post shows a few examples of when that happens and how to deal with it.
Introduction In the first part of this blog post we talked about how Rails and Phoenix compare on the web layer, if you haven’t read it go and check it out. Following on from that, we’ll see how data and the business layer are implemented on both frameworks. Migrations Let’s start
This is an introductory post to Phoenix, Elixir’s web framework. It is not intended to be a complete guide since it’s a big framework with lots of things to dive into, but rather to show a side by side comparison of how things are done in both frameworks using the
