chuhnk

24 ms·

181.
Show HN: Slack-srv: slack bot API as a go-micro RPC microservice(github.com)
2 points by chuhnk 11y ago|0 comments
182.
by chuhnk 11y ago
I was part of the BeatThatQuote.com acquisition back in 2011. We built Google Compare UK and then the team eventually moved onto to building the US comparison products also. Great to see this progressing forward.
183.
On Leadership(medium.com)
1 points by chuhnk 11y ago|0 comments
184.
Show HN: Micro – a microservice toolkit(myodc.github.io)
3 points by chuhnk 11y ago|0 comments
185.
by chuhnk 11y ago
Agree with the sentiment. Docker needs to build a product around the runtime, [build, deploy, manage], and then monetize that. It's the only long term play that makes sense. I also interestingly see them as the only company after redha
186.
by chuhnk 11y ago
Find a company doing it at scale, join them and learn about how its done. If you can go to a Google or a Facebook then it's a great way to learn from a decade or more of their experience. Jet.com is a .Net shop looking for engineers. M
187.
by chuhnk 11y ago
Interesting. Was working on something similar but more focused on streams with no identity. http://malten.me/
188.
by chuhnk 11y ago
Personally I think we need a foundation of reusable microservices that anyone can then build on top of.
189.
by chuhnk 11y ago
I'm working on something that falls into that category at the moment. Micro is a microservices toolkit written in Go that starts with a focus on development. It provides a library for discovery, client/server, routing, etc and als
190.
by chuhnk 11y ago
You'll see the extreme similarities to writing a microservice here https://github.com/asim/go-micro
191.
by chuhnk 11y ago
Hmm. So not to be critical but isn't this just rpc? It feels very much just like rpc development. If you look at the net/rpc package you basically do the identical thing.
192.
by chuhnk 11y ago
Very early on we had a lot of critical updates in core libraries which meant rebuilding everything and releasing but at the time the number of services were quite low and we were still in the R&D phase. Overtime that maturity meant chan
193.
by chuhnk 11y ago
We use protobuf rpc which allows us to maintain some form of backwards compatibility. New fields are ignored by old version of a service. We can also run multiple versions of a service in parallel and send a percentage of traffic to each. A
194.
by chuhnk 11y ago
From Hailo. Running 200 microservices in production. 199 of which are Go. We run on AWS with our own system that orchestrates Go binaries but are also moving to containers.
195.
by chuhnk 12y ago
Was always in awe of Borg and Omega while at Google. Really nice to see them finally publish a paper on this. Guess they've more far enough along now that it makes sense to do so. Omega will be a far superior beast to Borg and the open
196.
by chuhnk 12y ago
Genuine question. What makes this a blueprint for microservices infrastructure? What are the requirements for something that can support a microservice based design?
197.
by chuhnk 12y ago
Always resign with professionalism. Never burn bridges.
198.
The Handshake Deal Protocol(ycombinator.com)
2 points by chuhnk 12y ago|0 comments
199.
by chuhnk 12y ago
I think everyone is clear on the fact that after 9 months Kubernetes is not yet as mature as the 4-5 year old Mesos. But people love the project and the direction that it's headed in, to such a degree that there are partnerships formin
200.
by chuhnk 12y ago
Kubernetes will become a dominant container orchestration platform and API. It's what Mesos should be, but with the backing of Google, kubernetes is more likely to push into that space a lot quicker and with a lot more momentum. Notice
201.
by chuhnk 12y ago
Had similar pain points 6 months ago. Went through vagrant, docker, ec2, gce, gke and found issues almost everywhere. That's just the way it goes in the early days. 6-12 months down the line this will all be really easy and seamless wi
202.
by chuhnk 12y ago
How about asking them what they want to do? Ask them what motivates them? What they want to work on? Making assumptions based on what you think or what other people want is a mistake.
203.
by chuhnk 12y ago
Legitimate question. Do you think GitHub would accept a lucrative offer from Google? On the order of billions of dollars. How would that look? Where would we all be then? How much would it change things? Is it even realistic?
204.
by chuhnk 12y ago
Remember what they said about AirBnb in the early days? This is going to be pretty huge, mark my words.
205.
by chuhnk 12y ago
He said he was fired, but not how.
206.
by chuhnk 12y ago
No. It's a great way to separate one's involvement from the issue. Things like this happen all the time and you don't hear about it because it's treated exactly like this. CEOs are displaced at the top level in a way tha
207.
Y Combinator could be making a big change to its funding strategy(uk.businessinsider.com)
4 points by chuhnk 12y ago|0 comments
208.
by chuhnk 12y ago
Hailo - London - https://www.hailoapp.com/ Get a ride in two taps. Using e-hail to get you from point A to B might sound simple but there's a lot that goes on behind the scenes. From the iOS, android or web app all the
209.
by chuhnk 12y ago
The tech industry for the majority attracts like minded people. We tend to have an all on our nothing mentality. We don't do it on purpose, it's just how we're wired. We work endlessly, hours upon hours, and at some point it
210.
GRPC – cross-platform open source RPC over HTTP/2(corner.squareup.com)
2 points by chuhnk 12y ago|0 comments

More ›