Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
agallego
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
17 ms
·
151.
▲
by
agallego
9y ago
Oh I just got a linked to this. Thanks. Can u share a screenshot so I can look into this. It's SSL only site with a Jekyll render, and I host it on app engine.. so should be alright. Thank you
152.
▲
by
agallego
9y ago
i'm the author, feel free to ask any questions.
153.
▲
Akamai aquires Concord Systems
(akamai.com)
4 points
by
agallego
10y ago
|
0 comments
154.
▲
by
agallego
10y ago
Interesting, will keep an eye out as you mature it, looks like an awesome DSL for us to fill the runtime. Advantages are: 1. mesos integration, with that comes containerization support, multi tenancy, QoS, proper pipeline supervision, etc 2
155.
▲
by
agallego
10y ago
err. missing link: https://github.com/jjmalina/concord-python-dsl
156.
▲
by
agallego
10y ago
eng at concord here. Really cool API, you should port this to concord! =) i'd say major diff is dynamic topology. So during the pipeline execution you can add/remove workers for any stage. Also each stage/operator can be writ
157.
▲
by
agallego
10y ago
Author here. Happy to answer any q's
158.
▲
by
agallego
10y ago
Zipkin/Dapper is more for RPC tracing, not for low overhead function level tracing. We actually output zipkin traces to a kafka topic of your choice for network level tracing as well. This is more for debugging the c++ core.
159.
▲
by
agallego
10y ago
To expand on this. We use mesos. Mesos is mostly deployed with zookeeper. 'Technically' we can by swapping the library, but unlikely.
160.
▲
by
agallego
12y ago
> I don't get it. Is that yet another CORBA clone? Happy to explain what you don't get. Definitely not a CORBA clone.
161.
▲
by
agallego
12y ago
Good thoughts. I didn't talk about our operational complexity, but we are definitely working on both ends. The gist behind it is that we use Mesos/Yarn to handle the complexity of deploying and running things in a cluster. We - th
162.
▲
by
agallego
12y ago
Not sure why it sounds like CORBA. The point would be for an external system to handle communication. I agree with what Joe says in that article.
163.
▲
by
agallego
12y ago
I would agree that on the surface the problem does seem to be solved by an actor framework. The issue and main point is that I want that cross language, cross platform with isolation, tracing and debugging hooks.
164.
▲
by
agallego
12y ago
Very similar :) We do use a proxy/router. The main difference is that instead of using etcd for service discovery we are deeply integrated with Mesos. Our framework scheduler does the registration/deregistration, resource allocati
165.
▲
by
agallego
14y ago
fancy
166.
▲
by
agallego
14y ago
I wish I could go back to using it but I currently have to do some GWT dev and they only officially support linux. I tried running a vm and dual boot but that was too much hustle... as soon as I'm done with this project I'll go back to this