bsilva
Hello!
I want to improve my understanding of what’s possible to do into a clustered application and if I can send message around it in a natural way. And also which are the rules/good practices to consider when you move from standalone to a cluster environment.
For example purposes, let’s say that I have two different services:
Service A - Product service (Product’s attributes e.g: name, sku, manufacturer)
Service B - Pricing service (Stores product id + current price)
Those services were either written on Elixir or Erlang.
1 - Would be ok to add both of them into the same cluster? Is there any known problem or implication? What’s the ‘recommended way’ here?
2 - Could I replace completely the communication between then that happened via http with Erlang messages?
2.1 - If yes, how would it be possible? Is rpc suitable for this?
2.2 - How would load balancing work on that scenario? Should I write it or is it transparent?
Thanks 
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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
- #blog-post
- #ai
- #phoenix_html
- #iex
- #graphql
- #elixirconf-us
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hauleth
rpc. Instead I would advise using regular message passing.lpil
Hello! Welcome to the forum
It’s perfectly valid to create a cluster containing nodes with different code loaded on it if you wish.
Yes, this is definitely an option. If you are happy to always use Erlang based languages then a message based API can work well.
At very high throughput you may want to move from the default single TCP connection for inter-node messages to multiple connections. Depending on the skill-set and knowledge of your team is may be harder to implement than more mainstream HTTP APIs (but you’ll have had to implement much less API boilerplate up until this point).
I would advise against using the rpc module much, it uses a single gen server per node and this creates a big bottleneck. Your API should be regular messages sent to named processes.
You will need to implement load balancing for your message based API. There may be libraries that provide this sort of functionality, depending on what you want to do.