Using a framework for thousands of real-time connections for weekly reports?
Seems like over engineering to the max. :D
On the other hand they call it the hipster stack, so well done, I guess?
Seems like over engineering to the max. :D
On the other hand they call it the hipster stack, so well done, I guess?
It's a simple monolithic application with a relational database. Does this sound like over engineering? I don't think so.
It's actually the opposite. Which one seems like an overkill, Server A or Server B (https://pbs.twimg.com/media/CngB1sfWIAAbOFi.jpg)? ;)
Background: Just today I read that DHH considered Phoenix pretty cool, but Rails is enough if you don't need the real-time features.
Anyway, of course you can build your services how you like and it's probably a lot fun to use Phoenix :D
- Nowadays I have several reasons not to use Rails for new projects (https://blog.jaredfriedman.com/2015/09/15/why-i-wouldnt-use-...). But I actually I have more reasons to use Elixir instead (https://medium.com/@kenmazaika/why-im-betting-on-elixir-7c8f...) (http://blog.carbonfive.com/2016/04/19/elixir-and-phoenix-the...). And yes, it's fun, incredibly robust and scalable. :D