Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tylerflint
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
tylerflint
11y ago
repmgr and other projects listed here were considered and heavily tested initially. While each of them are great projects, we needed a solution that was fully automated in both cluster configuration/initialization as well as cluster re
32.
▲
by
tylerflint
11y ago
Much of the architecture of yoke was inspired by manatee. In fact, we've spent the last 2 years working with Joyent on smartos and illumos, so we were heavily inspired by the great engineering behind manatee. Manatee didn't work f
33.
▲
by
tylerflint
11y ago
Hey everyone, I work for nanobox and on the yoke project. I just woke up and noticed the thread. The interest is appreciated. There are a lot of great questions here, and I'll try to do my best to answer them individually. Please keep
34.
▲
by
tylerflint
11y ago
Yeah we hear ya. The nanopack cloud-initiative was just announced last friday ( https://blog.nanobox.io/nanopack-a-new-vision-for-automated-... ). We're getting there slowly but surely!
35.
▲
by
tylerflint
11y ago
Oh I see. Sorry for the confusion. The initial need was for a rails app to send data model updates to dashboard clients. Later, as our infrastructure became more micro-service-oriented, mist has been used as a place for the dashboard javasc
36.
▲
by
tylerflint
11y ago
This is referring to messaging being sent through mist. Mist doesn't care what the data looks like, and won't transform it. Currently the public-facing websocket client is not allowed to publish messages until this is mitigated, a
37.
▲
by
tylerflint
11y ago
So to the first question, there's not a transactional layer to guarantee the client handled the message. Once a message is sent to the client, it is assumed the client has a mechanism for queuing messages if it can't keep up. As t
38.
▲
by
tylerflint
11y ago
Also, if your network can't natively support multicast, you might want to check out red ( https://github.com/nanopack/red ) "A fast, in-kernel, ad-hoc point-to-point vxlan network."
39.
▲
by
tylerflint
11y ago
When a node is brought online, it uses multicast discovery to learn about other nodes. You can see the gist here: https://github.com/nanopack/mist/blob/master/main.go#L68-L76 Propagating events is really
40.
▲
by
tylerflint
11y ago
Also to clarify (and yes I also work at Pagoda Box on the Nanobox project), this service was initially intended to provide push capabilities for rails and other web frameworks that can't natively provide a push socket layer. It has suc
41.
▲
by
tylerflint
11y ago
How do you keep containers isolated? Do you just run multiple docker containers from different apps on the same host? Do you provide any sort of network isolation between apps?
42.
▲
by
tylerflint
11y ago
> We are human. We make mistakes, and we correct them. We get frustrated with someone, we over-react, and then we apologize and try to work together towards a solution. Wisdom.