Comments (8)
You can definitely do it via environment variables! Just set DISCOVERY_HOSTNAME
env var to the ip address :)
cote works with an auto-discovery mechanism. Supplying some IP addresses is great, but how will the instances discover each other? For that you would need to supply all the IP addresses of all the services, and that doesn't work with the fundamentals of cote, as it's not 0 configuration and not auto-discovery, and not scalable.
from cote.
If you are entirely sure about your machines and services, you can have a look at axon, which is the library cote makes use of underneath.
from cote.
So DISCOVERY_HOSTNAME does not work? as zero-conf, I would expect if every instance configured any ip/port pairs, then can exchange nodes info so get together as much as possible, so no need each instance configure all instances ip/ports. maybe just supply one share ip/port should also work for the worse case.
You can definitely do it via environment variables! Just setDISCOVERY_HOSTNAME
env var to the ip address :)cote works with an auto-discovery mechanism. Supplying some IP addresses is great, but how will the instances discover each other? For that you would need to supply all the IP addresses of all the services, and that doesn't work with the fundamentals of cote, as it's not 0 configuration and not auto-discovery, and not scalable.
from cote.
DISCOVERY_HOSTNAME
works if you have redis or another discovery mechanism like weave net. You can't exchange these ip/port configurations without a centralized mechanism, whether it's the broadcast/multicast mechanism or redis. How will they "get together as much as possible"?
cote doesn't try to replicate an auto discovery mechanism in software. It expects you to have either weave net, a broadcast / multicast mechanism, or redis. It's possible to add further discovery tools like etcd or zookeeper, but one would need to build these integrations.
from cote.
Well, cote do have broadcast and multicast as the basic discovery tool. what I really need is the other fallback way to specific other node ip/port to do the same work as broadcast or multicast in an env where broadcast and multicast do not work.
For my most simple case, 2 servers, but I found no simple way to connect them together with cote in such env.
from cote.
If you can't use redis or weave net, currently there are no other alternatives to replace broadcast or multicast with.
from cote.
yep, that's what this issue for. for now, I have to switch to use moleculer since it supplied the fallback way for my case: https://moleculer.services/docs/0.14/networking.html
from cote.
IP addresses should be unknown and irrelevant in cloud apps. Cloud apps follow the cattle approach, whereas specific IP addresses mean you have pets. I recommend switching to cattle, and if that's not what you are after, cote definitely isn't the right tool. (more about pets vs cattle).
Cote won't support specific IP addresses, as it's counter to the cloud native approach of building scalable infrastructure.
from cote.
Related Issues (20)
- No namespace and a strange "type" for Requester and Responder instances HOT 7
- Subscriber binding a socket instead of connecting (client vs server) ?
- Round-robin mechanism leads to lost requests HOT 4
- Client lost data when service graceful shutdown
- cote.js actively maintained? HOT 2
- Using cotejs on k3s cluster HOT 2
- K3S Kubernetes Cluster: TypeError [ERR_INVALID_ARG_TYPE]: The "options.port" property must be one of type number or string. Received null HOT 8
- Invalid 'main' field - node-discover HOT 2
- hiredis dependency preventing using node versions > 10? HOT 3
- [QUESTION] Are broadcasts mandatory? HOT 3
- Remove hiredis dependency HOT 3
- Discovery not working HOT 2
- How can I allow anyone over the Internet to run replicas of a service? HOT 1
- Cote not working with AWS Autoscalling instances. HOT 3
- Select port used
- Can't start cote due to port issue HOT 2
- View IP address of incoming request/broadcast HOT 1
- Hide "no listeners found for event" log HOT 2
- Requester can see the Responder but dont send request to it HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cote.