We share our thoughts

Building a backend, extending a team and reviewing architecture call for different Elixir partners. This comparison looks at eight companies, their specializations, client projects and ways of working.

How do you change a message schema when producers and consumers are deployed independently? We present how backward and forward compatibility, consumer-first rollouts, and compatibility layers help keep distributed systems working.

Phoenix LiveView is usually associated with real-time web applications and SaaS dashboards. But what happens when the browser becomes an operational interface for a fleet of physical machines?

Here's what changed in Permit 0.4.0, Permit.Ecto 0.3.0, Permit.Phoenix 0.5.0 and Permit.Absinthe 0.3.0.

Reusable Phoenix widgets without the usual pain. See how a pattern for building stateful, interactive, real-time components that stay fully self-contained and don’t leak complexity into the parent LiveView.

This article shows how Nerves on Raspberry Pi can turn sensor-based installations and DIY synthesisers into more reliable, flexible, and fault-tolerant systems.

Phoenix scopes are a new concept in Phoenix 1.8, and they can be easy to misunderstand at first. What they are, how they fit into Phoenix, and where they relate to authorization - Find out below.

You need speed and efficiency, but most importantly, you need a mobile product that performs like a native application without the financial burden of maintaining two separate codebases. That is the business case for React Native.

When we announced Permit.Absinthe last June alongside the Permit 0.3 and Permit.Phoenix 0.3 releases, we described it as a working proof-of-concept - something you could pull from GitHub and play around with for simple APIs. We also shared a pretty honest TODO list of things that were still missing before the library could be considered a real tool for real applications.