Re/ latency.at: This was probably /newest not the front page. My blog articles didn't work well on HN. But at least when launched I got on the front page. Still really hard to acquire users.
875 karma · joined January 22, 2014
Re/ latency.at: This was probably /newest not the front page. My blog articles didn't work well on HN. But at least when launched I got on the front page. Still really hard to acquire users.
BTW, I've just launched my first little SaaS. Seems like you have some more experience doing this. Maybe you have some feedback? https://latency.at/
Spun up this few hours ago, will be gone soon but if anyone wants to check it out without waiting for the metrics to trickel in:
http://pwd10-0-33-3-3000.host3.labs.play-with-docker.com/das...
It's also hosted on S3 but still up and running. (The main service is independent of S3 anyway after setup)
I'd expected it to score lower than 66 points on the uniqueness. But guess there aren't many this simple logos.
Latency at. You know, as latency at this location. And of course latency wasn't available on more prominent domains.
I just realize there is an open issue on Prometheus which, would it get implemented, would allow for very nice integration of the blackbox exporter as well as this service into kubernetes and tectonic: https://github.com/prometheus/prometheus/issues/3071
The 2.0 release of prometheus will help with stale data but not support bulk import yet. For that you can track https://github.com/prometheus/prometheus/issues/535
But to be clear: My service isn't about running Prometheus off-premises. It only provides the metrics which you can gather with your own Prometheus servers.
I've added the necessary account functionality and also extended the http probe to split response times by 'phase' (dns resolution, tls handshake etc).
The later part will be upstreamed soon though. Already discussed the required changes with the blackbox-exporter maintainer.
From what I can tell the patent grant is only beneficial to users of the software, not facebook. And it exists to address the concerns people might have that, if they use any facebook tech, they might risk getting sued. If you decide to sue, you're as good off as before. But if you don't sue, you can be sure facebook will never sue you either for violation of the patents they granted.
tl;dr: Planned to open in 2011, it's still in construction with some say it won't open before 2020.
Believe! I think this is just one of the many cases where after the fact everyone is like "oh wow, how didn't they think about it". But that doesn't say you would have thought about this before reading this.
The reason those people aim for jobs in the UK or US is because there aren't good tech jobs in Germany. Arguing for mandatory German classes to 'lock in' talent somehow is simiarly uninspired as tech companies here. What about creating jobs that good people are willing to work at?
That might be true for enterprise (I simply don't know) but in the startup world these are these are actually the most common workloads: Stateless apps that scale vertically.
I agree that startup time doesn't matter much if you need to do lot of initializations. But in my experience in most infrastructures these are a few databases of which there are orders of magnitude less than other workloads.
If you spin up the VM once and it runs for days/weeks that is true. In a cluster scheduler environment you usually have immutable images where every change requires replacement of the workload. In such scenario your VM or container might get replaced a few time a day, during every deploy. That's where VM startup time becomes an issue.
And it's surprising flexible! You don't need any overlay networking, you can just define a IP range and it will 'just work' as long as your nodes are in the same ethernet segment. If you grow to more than, let say, 500-1000 pods, you need some routing but still can do without overlay networks.
I'm currently working on a project where I use the kubelet standalone. I can give it a pod manifest and it will make sure the specified containers are running. This doesn't need any cluster components or data stores and is already useful for tiny use cases. Also using this now for my tests instead of docker-compose.
You mean given the rather slow cores? I can't think of any provider offering x86 bare metal at this price.