Menu
I'm developing an application with a web interface backed by Phoenix and I'm exploring alternate methods of storage to the current SQLite (and its Ecto driver) (yes I've heard of PGSQL, no I'm not willing to use it.)
I'd like to use LevelDB and H2LevelDB, which has an Erlang driver available on Github
However, at compile time I realise that Phoenix seems to rely a lot on Ecto, even in modules charged of rendering the eex templates. Which I find a bit scary, a bit strange and a bit annoying at the same time. So, would it be safe to blindly purge all references to Ecto from the pre-generated files or should I switch to something else for my web UI?
205
Awesome Phoenix web framework Phoenix framework is where Elixir shines. It's built-in a very elegant manner and gives you everything you need to build robust web applications as well as advanced APIs.
create We have a working application! Run your Phoenix application: $ mix phoenix. server You can also run your app inside IEx (Interactive Elixir) as: $ iex -S mix phoenix. server Load `http://localhost:4000` into your browser and you will see the default landing page of your application.
For any company that currently uses Ruby on Rails, Phoenix Framework should be on your radar, because it adds considerable performance gains. To top that off, Phoenix makes it incredibly fast to build web applications.
Phoenix does not rely on ecto in any way. One can be successfully used without the other. The integration is done through couple protocols, which are implemented in the phoenix_ecto package.
The default phoenix generator will create an application with ecto - the reason is to give the user something "with batteries included". You can easily remove this by passing the --no-ecto flag to the mix phoenix.new generator.
114
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
