Hey fellow elixir developers,


I seek your guidance. In my very few freetime? I'm working on a basic 
microservice in elixir: Magellan Microservice. (see 
https://github.com/fr3dch3n/magellan-microservice). 


Spending more and more time with elixir, I started wondering if my approach 
is actually any good. In Magellan I use a basic cowboy server and attach 
some routes to it. 

Here lies kinda the heart of this microservice. The concept enables you to 
write your own app, start the magellan from within your project and then 
simply register your own router to the magellan router. All requests that 
aren't handled by the configurable application-status-endpoints are 
forwarded to your own router. This way you don't have to worry about server 
or basic app-status things. (You can simply register a status function at 
the app-status that gets invoked by a request for the status-page. (The 
app-status is still in a very early stage, so there is no strategy to 
provide an useful status.)


Before continuing on this project I wanted to get some feedback to see if 
my concept is any good.

To provide a more specific question: 

Should I prefer phoenix even for such possibly small applications? For me 
it seems overpowered for this usecase.

I use some Agents for the rare cases where there is a state to safe (e.g. 
the registered router or registered functions for the app-status). Is this 
good practice?

What do you think about the whole concept?


We already use the magellan as basis for some monitoring applications, so I 
want to improve it wherever I can.


I'm greatful for any advice!

fr3dch3n

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-talk+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-talk/72daa6c6-68c2-402a-8648-d3b00a22601a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to