Pheonix with NodeJS

[Steven Livingstone-Perez]

Hello all. I am just starting with Phoenix and my initial interest is in the real time aspects for a web application I am writing.

I am interested in whether anyone has resources/thoughts/examples that show how to use the scale of Phoenix to provide real time capabilities via web sockets but using NodeJS for other parts of the application - registration, managing profiles and so on. The main reason is that I can pull together a Node app relatively quickly and have people skilled in that area that would take time to move it all to Phoenix.

Many thanks - the framework looks great :-)

regards,

steven  

[pratik khadloya]

Here are the list of open source apps that you can peek into

https://github.com/smpallen99/elixir_survey_tutorial

Real time chat app

App https://growing-beach-6143.herokuapp.com/

Code github/ma2gedev/phoenix_sample

Elixir Stream

https://github.com/janjiss/elixir-stream-phoenix

Sprint Poker

https://github.com/elpassion/sprint-poker

https://github.com/ericmj/gaze

https://github.com/phoenix-examples/

http://elixirstatus.com/

Colorjam Channel App ( https://colorjam.herokuapp.com )

https://github.com/reverie/phoenix-colorjam

~Pratik

--
You received this message because you are subscribed to the Google Groups "phoenix-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phoenix-talk...@googlegroups.com.
To post to this group, send email to phoeni...@googlegroups.com.
Visit this group at http://groups.google.com/group/phoenix-talk.
To view this discussion on the web visit https://groups.google.com/d/msgid/phoenix-talk/b01c9bee-2c9c-4964-959b-84a20c93b82c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jerel Unruh]

Hey Steven, one of the exciting things about Phoenix to me is that you can have your websockets and API/HTML code in the same codebase. I've (previously) went the route of separate realtime and API apps and it got unwieldy. Soon you want to access the same database from both apps, you have models (and migrations) duplicated between the two apps, etc. Or you end up using something like redis to pass messages between apps every time you need something.

You might find that switching your team to Phoenix is faster than the time you spend on architecture to make the two apps work well together.

To view this discussion on the web visit https://groups.google.com/d/msgid/phoenix-talk/CAOADwJFpTOqm7kR9CEpFsJbnVx2PMhTKYoX3dLoOdGe2av3uJQ%40mail.gmail.com.

[benwil...@gmail.com]

If you're set on doing both then your best option is to go the micro service route and just have two apps that handle separate parts of your domain.

[Steven Livingstone-Perez]

Hi - thanks everyone, Ben, Jerel & Pratik for responding!

I have actually been firing through the Phoenix docs today and into this evening and it is coming together quite faster in my head than i thought it would. I may stick with one codebase - at the API level anyway.

One thought i had was the huge number of packages i get via npm which is why node is great ... however, there *is* such a randomness in quality and complexity, as well as established patterns in scaling all the different pieces which is where my doubts had set in and I came back to see how Elixir was doing (i learned a bit of Erlang a couple of years ago).

So, although I am yet to see how easy and how many Plugs there are, the overall architecture of this and related projects feels very clean and, dare i say it, enjoyable :-)

Back to the docs!

regards,

steven