Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

schneider.dev

Post reply on HN
Print view View original

111–120 of 155 posts

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#111

Post by scns »

jypepin wrote: post #90
dafrie wrote: post #86

Earlier quoted context omitted.

Just a quick one: why would you need redux for forms? This is in my opinion a total overkill. I have forms either having their own state or (preferred) just use Formik for all of this. In my stack, this then allows to just add a field in the GraphQL schema (backend), add it in the query, add the formik field + yup validation and done.

Some people would argue that if using Redux, also having local state logic is an anti pattern. That would mean that if you use Redux, a form also requires actions for form update/submit/success/error and the form data should be stored in the redux store. That is one of the main issues I have with Redux, which I feel adds automatic complexity for simple things, but at the same time I'm not sure if it's very good to ha…

Abramov advises against using redux for forms

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#112

Post by Xixi »

out_of_protocol wrote: post #84
bitcrusher wrote: post #37

Earlier quoted context omitted.

Yep! Just use Plug. There’s no need to drag the entire Phoenix stack in. https://hexdocs.pm/plug/readme.html

Then you'll need to create own version of migrations, routing, configure asset building pipeline etc etc etc. Phoenix have everything in place, without need to re-implement lots and lots of basics

A bit pedantic, but migrations are provided by Ecto [1], not by Phoenix. You don't need Phoenix to use Ecto.

https://hexdocs.pm/ecto/Ecto.html

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#114

Post by nathan_long »

rossenberg79 wrote: post #30

Why is Elixir always being paired with Phoenix? Can’t I just have a backend API running on Elixir and a javascript front end to interact with it? I’d prefer a simple React, Postgres, Elixir stack (REP).

You can use Plug instead of Phoenix if you like, but why do you object to Phoenix? It's quite customizable.

Generate a new Phoenix app. Open up the endpoint file. Don't want routing? Comment it out. Don't want logging? Comment it out. Keep what you want, discard the rest.

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#115

Post by nathan_long »

hestefisk wrote: post #19

Good read. Curious about Elixir. Why would one use this over ‘plain old’ Erlang / OTP apart from the Rubyesque syntax, which might appeal to RoR devs?

Friendlier tooling and documentation are a couple of reasons.

Elixir's whole reason for existence is to make the Erlang programming model easier to use. Try it and see if it does.

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#116

Post by mwcampbell »

Draiken wrote: post #106
xlii wrote: post #98

Earlier quoted context omitted.

That was one of the reasons I choose this stack. The plan was hiring team just after stack was set. Unfortunately financial plans toppled and we (2 full stacks + front end UX) were stuck with very complex architecture designed for ~10. If I would be to working on only 1 part it would be great, but instead of parallelizing effort it was sequenced which kind of sucked.

It's early optimization at the architecture level. I've seen it happen so many times. On top of all you said, the GraphQL stack is horrible for caching. You will not have this problem until you reach really high traffic, but once you do, it will eat you alive. Unlike a rest endpoint, you can't cache a URL. You can't use HTTP headers. You don't know beforehand what GQL query will come and even with batch queries for d…

> it's super hard to optimize. It's very easy to have an N+1 query hell.

Both Postgraphile and Hasura deal with this. I have no idea about Absinthe.

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#117

Post by em_jones »

Intermernet wrote: post #28
bdibs wrote: post #3

Earlier quoted context omitted.

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.

Link: https://pragprog.com/book/phoenix14/programming-phoenix-1-4

This has been on my radar. I'll have to add it to my queue on Safari. Thanks for the rec!!

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#118

Post by em_jones »

nickjj wrote: post #14
em_jones wrote: post #2

I'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 almost exclusively learned the basics of Elixir / Phoenix by looking at the source code of https://changelog.com which is at https://github.com/thechangelog/changelog.com . Major kudos to them for open sourcing their platform. It covers like 50+ common web dev features. I pretty much skimmed the docs to get the ultra basics, looked at that source while I was building my own app and then asked questions when I got r…

This is a sweet shout-out. Thanks!

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#119

Post by rainygold »

SaltyBackendGuy wrote: post #17
adamnemecek wrote: post #4

Ok, 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.

Dotnet Core is actually really nice as well, I think v3 is right around the corner. Something worth checking out if you're looking into beckend technologies. I've been using it lately, coming from Node.js for the last few years, and it's been a really nice change.

Anything .Net can be replaced by Java.

Re: Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo

#120

Post by bobwaycott »

rossenberg79 wrote: post #30

Why is Elixir always being paired with Phoenix? Can’t I just have a backend API running on Elixir and a javascript front end to interact with it? I’d prefer a simple React, Postgres, Elixir stack (REP).

If you want something simpler and more building-block, micro-framework style in Elixir, you'll want to take a look at Raxx[0]. You could also just build atop Plug itself, though Phoenix really is just a whole lot of Plug.

[0]: https://github.com/crowdhailer/raxx

Post reply on HN