Zalando's engineering team writes about running large-scale systems at the European e-commerce company, including Kubernetes, Postgres, load balancing, and ML.
HN commenters mainly link it and share related experience, such as running a paper reading group; no strong opinions appear in the given comments.
Nice graph, have you considered making it a directed graph, and also assigning more explicit semantic meaning to the edges?
So for example, using turtle syntax [1], instead of
<https://engineering.zalando.com/posts/2022/04/functional-tests-with-testcontainers.html> <http://example.com/graph-edge> <https://www.testcontainers.org/>
have
<https://engineering.zalando.com/posts/2022/04/functional-tests-with-testcontainers.html> <http://purl.org/dc/terms/subject> <https://www.testcontainers.org/>
The semantics of http://purl.org/dc/terms/subject is given at the url itself, but in brief:
> A topic of the resource.
> Recommended practice is to refer to the subject with a URI. If this is not possible or feasible, a literal value that identifies the subject may be provided. Both should preferably refer to a subject in a controlled vocabulary.
This would be similar to how wikidata expresses knowledge [2]:
<http://www.wikidata.org/entity/Q28315661> <http://www.wikidata.org/prop/direct/P921> <http://www.wikidata.org/entity/Q750997>
Or in English:
"Go To Statement Considered Harmful"(Q28315661)'s "main subject"(P921) is "goto"(Q750997)
This also makes it easier to query [4], for example, you could get all articles covering a "goto" with the following SPARQL[5] query:
SELECT ?item WHERE
{ ?item <http://www.wikidata.org/prop/direct/P921> <http://www.wikidata.org/entity/Q750997> }
May help to read the RDF primer [3] also.
[1]: https://www.w3.org/TR/turtle/
[2]:…
Congratulations on the five year mark! I co-run a similar paper reading group at Zalando (European e-commerce) and recently shared our learnings/experience[1] of running such a group for over a year and I'm happy to see so many similarities.
We focus our papers around distributed systems, software engineering and languages and try to cover more ground on the applications of the concepts discussed in the papers. The blog post also contains a "blueprint" for someone who is looking to start a similar group.
What has driven the meetups throughout the year is we being two organisers, driving the topic ourselves by preparing a presentation (not everyone would have the time to pre-read) and making the format conversational/open - very similar to what Armaan (op) shared.
One of our recent experiments was doing a collab with the Berlin Systems Group[2] where we organised an external-facing event in Berlin with attendees from outside our organisation. I was so happy to see a nice small group turn up for the event and thoroughly enjoy it!
[1] https://engineering.zalando.com/posts/2026/01/running-an-engineering-papers-reading-guild-at-zalando.html
[2] https://luma.com/y9edbih7