code
I want to transfer an API that was built using fastapi in python to elixir. Should I use phoenix or plug? Phoenix is excellent for web development, but is it overkill for an API that serves another frontend built in js? plug on the other hand seems suitable from what I’ve read but I also read that it needs more boilerplate. The API is fairly complex and plug seems suitable to me. I just wanted to know if there is anything that I should be warned about regarding plug and if there are some tweaks to phoenix to make it similar to fastapi (ie: remove the fullstack web development packages).
Thank you.
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Other Trending Topics
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
RudManusachi
Take a look at the API-only applications section of Phoenix docs.
code
Thank you
dimitarvp
Phoenix, while making your app have a little more files, is much more future-proof than any almost barebones Plug app you might do.
Go for Phoenix. It might be slightly annoying to begin with but will very quickly pay dividends.
lud
I’d go with Phoenix too. We build our APIs with it and it has been great so far.
The Phoenix tutorial will have you install the
phx.newcommand. Once done, callmix help phx.newin your terminal and you will see options to disable HTML, LiveView, Tailwind and ESBuild when creating a new Phoenix project.victorbjorklund
I would say go with Phoenix unless it is a very simple API that won’t grow in the future (which does not seem to be the case). The overhead of phoenix is negligible but makes many things easier.
Just exclude everything you don’t need:
mix phx.new my_api --no-assets --no-gettext --no-html --no-mailer