NodeUp: A distributed systems show #53

Activity

1. rvagg commented on Jul 12, 2015

   

   rvagg

   on Jul 12, 2015

   More actions

   • @mafintosh
   • @substack
   • @dominictarr
   • @ralphtheninja
   • @juliangruber
   • @feross

   Can y'all help with coming up with an ideal panel for a distributed systems NodeUp? Ideal would be 3 people, can stretch to 4. Would be good to have a diversity of views and/or approaches on distrubuted & p2p, particularly if we can get people working in different parts of this area.

   I'd love to do this and can make it happen pretty soon.
2. objectiveSee commented on Sep 8, 2015

   

   objectiveSee

   on Sep 8, 2015

   More actions

   Adding a few more ideas from working in Node:

   • Load Balancers (server discovery)
   • Auto-scaling: Amazon Web Services, Elastic Beanstalk, Elastic Load Balancer
   • Pub/Sub, inter-node communication, distributed memory systems (Redis)
   • Database access (document level locking in a distributed environment)
   • sharing preferences and secrets
   • Web Sockets (balancing, session affinity, headaches)
   • Deployment of multiple apps, rolling deploys, rolling back
   • Logging and realtime monitoring (Kibana, Logstash, munin, Google Analytics)
   • What does your environment look like? (How many different app servers?)
   • At what point do we become sys admins?
   • Do you dare use the cluster module?
   • pm2
   • unique debugging problems (log access, performance, sshing into a dynamic sized set of servers)
   • docker
   • Amazon Lambda
3. JamesKyburz commented on Jan 5, 2017

   

   JamesKyburz

   on Jan 5, 2017

   More actions

   Would love this
4. dominictarr commented on Jan 5, 2017

   

   dominictarr

   on Jan 5, 2017 via email

   More actions

   i suggest having two sessions, one distributed and one p2p. Although there is some overlap in concepts, they are very different in spirit.

   …

   On Jan 5, 2017 22:59, "James Kyburz" ***@***.***> wrote: Would love this — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#53 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAP1Lj_dJfXoMe1xNRaB5GZFukRXUp29ks5rPL8AgaJpZM4FW43h> .

   👍React with 👍2Reacted by Asbjorn Enge and James Kyburz
5. ralphtheninja commented on Jan 6, 2017

   

   ralphtheninja

   on Jan 6, 2017

   Last edited by ralphtheninja

   More actions

   @rvagg Sorry, I completely missed your message over 1.5 years ago :) I'm currently not working on any project related to p2p (although I would love to take it in that direction). I currently work on stuff related to a mixture of

   • mqtt (for pulling in data and also internal pub/sub)
   • websockets
   • z-wave
   • openwrt
   • docker (deployment based on docker-remote-api + tls)
   • docker container orchestration using docker swarm (the new 1.12+ built in swarm feature)
   • traefik reverse proxy (running in docker)
   • node (well duh)
   • azure (virtual machines + azure load balancer)

   Not sure if this is of any interest or relevance :)
6. JamesKyburz commented on Jan 6, 2017

   

   JamesKyburz

   on Jan 6, 2017

   More actions

   @dominictarr Sounds great!

   I enjoyed the show on Docker, maybe this time a show more about the core concepts of going distributed using node?
7. JamesKyburz commented on Jan 6, 2017

   

   JamesKyburz

   on Jan 6, 2017

   More actions

   @ralphtheninja

   Interesting mix!

   Been also using docker + node but with nginx. Will have a look at traefik ;)
8. ralphtheninja commented on Jan 6, 2017

   

   ralphtheninja

   on Jan 6, 2017

   More actions

   Been also using docker + node but with nginx. Will have a look at traefik ;)

   traefik is awesome :)