brasetvik

I'm sure a certain Joseph Fourier was asked that question too, quite some time ago. :)

Cognite | Oslo, Norway and Austin, US | On-site (we help relocate) or remote | https://www.cognite.com/en/careers

Cognite provides contextualised data as a service, such as digital twins, focusing on asset heavy industries to start with.

We're hiring for several positions. Most are on-site, but we're looking for a principal database reliability engineer (DBRE) with Postgres and Kubernetes chops, and a senior/principal DBRE with Elasticsearch, Kafka, and Kubernetes experience.

The DBRE positions are offered remote in EU + US time zones, the rest are mostly in on-site Oslo, Norway. We help with relocation.

https://www.cognite.com/en/careers

Big fan of graphviz.

Lots of interesting tools that use it being posted here, so here's a toy of mine: https://github.com/alexbrasetvik/graphspec

I've used it mostly to mix edge+node definitions in comments in asciidoc or code, and the non-nested nature makes it easy to compose different sources of edges and nodes.

(It's just a POC. If you know of something similar that's more actively developed, I'd be very interested)

Hey. I wrote that a long time ago. Funny to see it re-surface and glad it's helpful. :)

There is a presentation version of it here: https://www.youtube.com/watch?v=PpX7J-G2PEo&feature=youtu.be (I made the presentation first and then wrote the blog posts)

I wrote a follow-up at called Elasticsearch from the Top Down here: https://www.elastic.co/blog/found-elasticsearch-top-down

The page doesn't do a great job at explaining the mechanism (which from a quick glance seems to involve WebRTC).

This is a better resource on this topic, which involves DNS rebinding: https://medium.com/@brannondorsey/attacking-private-networks...

DNS-rebinding also gets around the cross origin request issue, which some comments here mention.

XSS coupled with a vulnerable JSONP endpoint can also be chained to a persistent client-side XSS via service workers. https://c0nradsc0rner.com/2016/06/17/xss-persistence-using-j...

Elastic, the company behind Elasticsearch (and more), is hiring for a lot of roles: https://www.elastic.co/about/careers#engineering

Location: Earth

Another feature that should probably be on that list is Common Table Expressions: https://momjian.us/main/writings/pgsql/cte.pdf

(I still frequently run into people who work a lot with SQL that don't use CTEs, though less than before :)

And that's why server side request forgery (SSRF) is so dangerous.

Note that Postgres supports functional indexes, and the case in the post (a `lower(column)=`-clause not being able to utilise the column's index) is the example used in the documentation: https://www.postgresql.org/docs/current/static/indexes-expre...

This is (understandably!) a common request, and both are on our roadmap.

Per availability zone, Elastic Cloud currently scales vertically (in power-of-two increments) until a cluster hits 64GiB memory, at which point multiple 64GiB-nodes are added. While you can run Elasticsearch with e.g. two 8GiB nodes per zone, we prefer a single 16GiB node as there's fewer things that can go wrong. (If you want the second 8GiB node for redundancy, then that's exactly what our multi-zone HA configurations are for, and we encourage HA setups by making them less than twice (or thrice) the price, throwing in additional master-only nodes for free)

(A bit of history: When Found (the company Elastic acquired and which is now Elastic Cloud) was in private beta in early 2012, we actually did allow custom cluster topologies. We ultimately disabled that as it was overwhelmingly used to make sub-optimal cluster configurations, such as 5 x 1GiB memory nodes)

(Disclaimer: I work on Elastic's Cloud team)

While AWS ES can be cheaper in some configurations, Elastic Cloud is actually quite competitive in pricing for larger clusters when compared to AWS' ES-service. This post compares the two services, and there's an example price comparison at the end of the post: https://www.elastic.co/blog/hosted-elasticsearch-services-ro...

We support most official plugins, and if you get a gold or platinum subscription you can upload your own plugins. Elastic's X-Pack is included in every cluster, which includes security features like role based access control.

It's not possible for external service providers to integrate with IAM at this point.

Have you considered a more permissive license, like Apache/MIT/BSD?

Elastic, the company behind Elasticsearch, is hiring for a lot of positions: https://www.elastic.co/about/careers

I'm on the team behind Found, which is the official hosted Elasticsearch service. We're hiring engineers with backgrounds in design and operations of distributed systems: https://www.elastic.co/about/careers

We're (very) distributed/remote :)

http://www.glassdoor.com/Overview/Working-at-Elastic-EI_IE75...

Elastic, the company behind Elasticsearch, is hiring for a lot of positions: https://www.elastic.co/about/careers

I'm on the team behind Found.no, which is a hosted Elasticsearch service. We're hiring engineers with backgrounds in design and operations of distributed systems: https://www.found.no/jobs/

We're distributed/remote.

Elastic, the company behind Elasticsearch, is hiring for a lot of positions: https://www.elastic.co/about/careers

I'm on the team behind Found.no, which is a hosted Elasticsearch service. We're hiring engineers with backgrounds in design and operations of distributed systems: https://www.found.no/jobs/

We're distributed/remote.

Elastic, the company behind Elasticsearch, is hiring for a lot of positions: https://www.elastic.co/about/careers

I'm on the team behind Found.no, which is a hosted Elasticsearch service. We're hiring engineers with backgrounds in design and operations of distributed systems: https://www.found.no/jobs/

We're distributed/remote.

Elastic, the company behind Elasticsearch, is hiring for a lot of positions: https://www.elastic.co/about/careers

I'm on the team behind Found.no, which is a hosted Elasticsearch service. We're hiring engineers with backgrounds in design and operations of distributed systems: https://www.found.no/jobs/

We're distributed/remote.

Elastic, the company behind Elasticsearch, is hiring for a lot of positions: https://www.elastic.co/about/careers

I'm on the team behind Found.no, which is a hosted Elasticsearch service. We're hiring engineers with backgrounds in design and operations of distributed systems: https://www.found.no/jobs/

We're distributed/remote.

Elastic (formerly Elasticsearch) – https://elastic.co – Remote

Remote senior software engineer with experience developing and/or operating large scale distributed systems, and more.

See also: https://www.elastic.co/about/careers

If you reach out to support, we can get you settled right away. :)

Hi,

Found-founder here. You can pick HA in eu-west-1 as well, and we've been battle testing a solution for other regions for some time now, and it'll soon be generally available.

The issue is that a lot of regions only have two availability zones, and having a third is important to prevent split brain scenarios. (Our solution to that involves using ZooKeeper.)

Nice post!

We also have some articles on analyzers here: https://www.found.no/tag/analyzers/

Our tool Play is also helpful when playing with analyzers, as it can show how text is processed step-by-step: https://found.no/play (Click on "Analysis". Try changing the configuration and press Ctrl+Enter to execute with the new config)

(Disclaimer: I work for Found and made Play)

An important limitation to note is that while you can "just buy a second 2xlarge", you have to do it within the same hour:

"When combining Reserved Instances, the end dates of the Reserved Instances must have the same hour digits in 24-hour format"

Source: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ri-modify...

Great initiative.

This one is a classic as well: What Goes Around Comes Around (Michael Stonebraker, Joseph M. Hellerstein) – http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.113....

"This paper provides a summary of 35 years of data model proposals, grouped into 9 different eras. We discuss the proposals of each era, and show that there are only a few basic data modeling ideas, and most have been around a long time."

https://twitter.com/alexbrasetvik - mostly tidbits related to Elasticsearch and distributed systems, with a hint of skydiving.

For local testing on Postgres where you don't care about database reliability, you can also speed things up a lot by setting `fsync = off` and `synchronous_commit = off`.

(Never do that on a production database, of course!)

Happy to help!

I posted it since NoSQL was a hot topic in the 1.0 thread.

If you're uncovering unknown unknowns, these can also be of interest:

- https://www.found.no/foundation/elasticsearch-in-production/

- https://www.found.no/foundation/elasticsearch-from-the-botto...

Thanks for the feedback!

The point of that section is exactly that "NoSQL" (or to make things even more confusing "NOSQL" (Not only) doesn't have a very specific meaning. Some think it rules out ACID, other's don't. Thus, you'll need to know what you need.

And database marketing tend to not be very good at pointing out what they're not good at, or actually deliver what they promise. See also: http://aphyr.com/tags/jepsen