meenachinmay
Planning a micro-service arch project with NestJS and elixir!
Hey everyone. This is going be the first post ever here by me. Coming to the point that i am planning to build a very simple but powerful architecture based application which is going to be a real time chat application.
I am going to use Micro-service arch for this. For creation / update / deletion of users / rooms i am planning to use NestJS service and for handling real time messaging i am going to use elixir backend as a service.
I am planning to use Kafka as a message broker which will help me to perform inter service communication between nestjs service and elixir service.
when i will add authentication to this app which will be a tricky part of course because there are two separate choices one is to add centralized auth system after an API gateway or add a separate auth service in both the services. So that i will be thinking later.
for now i just want to welcome suggestions / hints / notes / help for this project. I am going to broadcast this whole project on my youtube channel and My biggest supporter in this project will be a AI bot called chatgpt. Because he helps me a lot.
One thing i want to tell everyone that i decided to build this project being a fresher to elixir. i have experience with nestjs as i use it at my work every day. But for elixir it is going to be my first time and today itself i wrote “Hello world” in this language.
I love real time system so i chose elixir to learn now onwards.
I would be more than happy if you can help me in this journey.
Thank you everyone in advance.
Most Liked
tfwright
Since your interest is mainly to learn I recommend just jumping into writing code without worrying too much if you are making all the right decisions for designing the elixir piece. You will learn a lot from making wrong decisions and if you get stuck on something specific along the way you should find it easy to get answers here. In general the more specific the question the quicker and better the answer ![]()
krasenyp
Don’t know, sounds like overengineering to me. Just go with Elixir, you won’t regret it and it’s a superior technology, especially for the use case. But most probably it doesn’t matter because you probably won’t get to a scale where it would. No offence.
If you go with your proposed architecture, just deploy the two services to the same server and use UNIX sockets for communication.
D4no0
Totally agree, the best practice to truly understand something is to make it the wrong way, then slowly improve while understanding the tradeoffs.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #hex









