Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
1–10 of 155 posts
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#2I've just been trying to get back into elixir recently, myself. I'd done some basic crud 'helloworld' stuff when I first tried about a year into professional development.
I've since had the Fortune to spend time learning about cloud native apps, distributed service patterns, and supporting infrastructure (spring cloud, pcf, vanilla k8s, gcp) and now returning to elixir having at least better understanding of what erlang and OTP offers.
I'm super excited to see I'm not alone in finding this sort of stack is worth fiddling with(although, I tend to pick Vue when not using angular for work).
Thanks for posting this!!
For those interested in what resources I'm leaning on: The Manning 'Elixir in Action' and the Pragmatic Programmer's graphql texts along with exercism.
Anybody else have any preferred resources for these technologies?
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#3I've just been trying to get back into elixir recently, myself. I'd done some basic crud 'helloworld' stuff when I first tried about a year into professional development. I've since had the Fortune to spend time learning about cloud native apps, distributed service patterns, and supporting infrastructure (spring cloud, pcf, vanilla k8s, gcp) and now returning to elixir having at least better understanding of what erl…
If you're interested in the Phoenix Framework you should check out "Programming Phoenix: Productive |> Reliable |> Fast".
It's written by the creator of Phoenix (Chris McCord) and the creator of Elixir (José Valim), and it's a fantastic intro to Phoenix.
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#4Ok, for backend, I’m deciding between rust with actix, jvm (kotlin + akka/quasar) or elixir.
I kinda know the theoretical differences but I’m curious what hn thinks. Has someone actually deployed things in some of these.
I do have preference towards rust but maybe there’s something better.
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#5Ok, for backend, I’m deciding between rust with actix, jvm (kotlin + akka/quasar) or elixir. I kinda know the theoretical differences but I’m curious what hn thinks. Has someone actually deployed things in some of these. I do have preference towards rust but maybe there’s something better.
That really depends on what you're building.
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#6Ok, for backend, I’m deciding between rust with actix, jvm (kotlin + akka/quasar) or elixir. I kinda know the theoretical differences but I’m curious what hn thinks. Has someone actually deployed things in some of these. I do have preference towards rust but maybe there’s something better.
That really depends on what you're building.
When would erlang,jvm be preferable over actix.
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#7I've just been trying to get back into elixir recently, myself. I'd done some basic crud 'helloworld' stuff when I first tried about a year into professional development. I've since had the Fortune to spend time learning about cloud native apps, distributed service patterns, and supporting infrastructure (spring cloud, pcf, vanilla k8s, gcp) and now returning to elixir having at least better understanding of what erl…
I liked this "Elixir For Programmers" by Dave Thomas
https://codestool.coding-gnome.com/courses/elixir-for-progra...
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#8Earlier quoted context omitted.
That really depends on what you're building.
When would erlang,jvm be preferable over actix.
rust is still figuring out async, so it's not as good a fit as say go or elixir.
If you are specifically making a graphql backend, idk why you would anything but node, since it has the most mature ecosystem.
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#9When you get to the absinthe part you lose me. It's the same gut feeling I had when I see Redux where it works but it was created at the very beginning of this entire workflow discovery and better tools/approaches have since come out.
Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo
#10Earlier quoted context omitted.
That really depends on what you're building.
When would erlang,jvm be preferable over actix.
They're all wonderful, established technologies and all very capable of making concurrency relatively painless. At this stage, you should go with whatever you would be most productive in: do you already know one of the languages? If so, go with that one (always be shipping!). If not, how much do you like the syntax of each? How much do you rely on static types? How mature are the third-party libraries you're going to be relying on?
I've been building software using the exact stack described in the linked article for the last three years. I don't think about my backend very much, it mostly just works. Most of the work is on the front end. Elixir/Phoenix/Absinthe have been almost completely frustration-free. I'm sure Rust and Kotlin are great too.