tbarbugli

Stream | https://getstream.io | Amsterdam, The Netherlands | Senior Software Engineers | Full-time | EUR 60-70k + equity | ON-SITE (NL)

We're looking for three developers to expand our core team in Amsterdam. Our tech stack: Golang / Python 3 / AWS. We built and operate our own in-house distributed database (Go + Raft + RacksDB + gRPC).

You can find more information about the positions on Angel List.

- Senior JS Engineer -> https://angel.co/stream/jobs/421542-senior-javascript-develo...

- Senior iOS Engineer -> https://angel.co/stream/jobs/434049-ios-mobile-developer

- Senior Python / Machine Learning Engineer -> https://angel.co/stream/jobs/268098-senior-python-developer-...

Experience running high traffic services and maintaining open-source libraries is a big plus.

You can also email me with any questions: tommaso@gestream.io

Do I really have to explain this?

Great idea, I hope they also put money to help get orgs out of PHP, Drupal and other dead/terrible software. If not this is a bit depressing and short sighted.

Only problem is that dutch vegetables have no taste and are still insane expensive compared to meat (which is also tasteless). So yeah, awesome thinkering and efficiency here, but quality is not there.

Perhaps you are from NL, Denmark, Germany or Sweden. Traffic management in Italy, Belgium, France, Spain, Portugal, Romania, Greece is insane (and you can't even take a right when it's red!)

Stop eating beef instead of focusing on these BS ideas.

This icould be great news, it is not clear from the article but I hope they solved the annoying problem of first repo sync hitting Github rate limits. We had this issue several times when we migrated from Trello to Jira.

Stream | Senior Backend Developer | Amsterdam, The Netherlands | ONSITE | https://getstream.io Stream is an API service to build scalable newsfeeds and activity streams.

We're looking for a senior backend dev to work on our core APIs. Our tech stack: Golang / Python 3 / AWS. We built and operate our own in-house distributed database (Go + Raft + RacksDB + gRPC).

Experience running high traffic, highly available services is a big plus. We also have an office in Boulder, CO which you are welcome to visit.

Apply: https://angel.co/stream/jobs/241159-backend-software-enginee...

Been reading about pill based diagnosis for digestive organs for more than 10 year. Current alternative to this is incredibly invasive and painful and scary as hell!. Is any hospital using similar non invasice technology to run stomach/intestine checks?

> "Why Did We Build It?"

Marketing

Am I the only one thinking this is a terrible Buy versus Build decision?

You can get HTTP load balancing, Postgresql with automatic fail-over and queuing up and running in a matter of minutes from AWS or GCE.

There are more factors to take into account than plain API / feed update traffic when looking at server count:

- High Availability requires 2x or 3x more servers

- We run our own monitoring, log collection and tracing infrastructure

- ML/Analytics features

- Distribution of traffic

- Disaster Recovery

Edit: fix list formatting

We currently use the Raft Go implementation from Hashicorp (the article links to the Github project). We found Hashicorp implementation mature enough and easier to work with than the one from etcd.

Using Rocksdb with Go has indeed its own challenges because CGO calls are far from cheap and have an important consequences on Go applications. For performance reasons, we ended up moving some logic from Go to C in a few hot-spots (eg. moving the retrieval of large amount of keys from Go to C).

Disclaimer: I work for Stream and I am one the two co-founders

Just PhDs, the undergraduate bit was added by accident. Fixed my comment.

Yet the primary source of energy for Germany is coal.

Years ago after spending uncountable beers listening to the frustration of several PhDs friends, I had the idea of a journal for research failures/dead-ends.

The idea was to look at unfruitful research as something useful for the community and give some credit to time and resources spent doing something that did not work (and should not repeated by others). I still wonder if that would create the wrong incentive though and if that could be feasible at all (who likes to talk about money and time wasted?)

EDIT: fixed wrong sentence

So far the best mitigation I could find out is to enable the root account and set a strong password for it. Hopefully we'll get a security update quickly so that I disable root access again. While checking on this I also realized I was running 10.13 instead of 10.13.1 which fixes another major security flaw (key chain saves in plain text)

author here: About your second point. We spend quite some money on AWS every month. As long as we keep paying our bills, I don't see why they would want to cut us loose.

author here: this indeed incorrect, I will change that into "centralized and distributed" thank you for pointing that out

> Using .io is unfair to the Chagossian People

> The reason closest to our hearts is the geopolitical background of .io domains which we only learned about recently.

Later in the article:

> Of course, we will make sure to redirect all traffic from *.plan.io appropriately so no existing links will break in the future.

Which to me sounds like they will keep paying for the .io domain for the foreseeable future.

That's interesting. Can you share the source of that information? I was trying to understand that but somehow I did not manage to find anything online.

Author here: the post is based on my direct experience with .io. It is not very clear to me how Afilias is involved in the operational side of things, AFAIK they might have just acquired the existing .io infrastructure and kept it as it is (and same goes for the way more reliable .org TLD)

nic.io contact page links to https://www.icb.co.uk/ which is not reachable

This https://bridge.joinmastodon.org/ let's you find your friends from Twitter on Mastodon

Did you try using Imgix for images? We did that this week and so far we like it a lot

Same exact experience for me (in NL). I have to say that compared to all other co-working spaces I used (6 so far), WeWork is the only one that really nailed it in terms of operations. (WiFi/Internet, delivery, key-cards, ...)

coin toss?

I suggest adding an explanation what what the game is about (or fix the "How it works" link)

how can that be related to Route53? Nameservers are managed by .io TLD and that's where the issue is coming from. If you use Route53, the nameserver should return Route53 nameservers

Seems to be fixed now