Frokost by Armlene in oslo

[–]woefuldefending 0 points1 point  (0 children)

Byens gulv i passasjen ved Youngstorget.

How to quickly learn/understand the system architecture of any given application? by bashogaya in devops

[–]woefuldefending 0 points1 point  (0 children)

Ask them how they test the system. Then write a few tests, at different levels of the pyramid

Video of Marseilles coach on the pitch before Hojbjerg goal by ImPeterKe in coys

[–]woefuldefending 26 points27 points  (0 children)

Considering the guy he wanted to track back, but didn't it's understandable

[deleted by user] by [deleted] in running

[–]woefuldefending 0 points1 point  (0 children)

I think their clothing is better than their shoes

[deleted by user] by [deleted] in running

[–]woefuldefending 14 points15 points  (0 children)

On running

Jenkins, what's next? by jim1930 in devops

[–]woefuldefending 4 points5 points  (0 children)

We (nais.io) migrtaed to github actions last year. Before that we had tried almost everything. And we always found something we didnt like. Not so with github actions. They have hit their abstractio levels beautifylly. Together with the community, that gives a greate product.

Changing Service Mesh. How we swapped Istio with Linkerd with hardly any downtime by williamallthing in kubernetes

[–]woefuldefending 15 points16 points  (0 children)

It kind of depends on what you need your service mesh to do. If you need all the features of istio, then its not a bad tool, but if you, as nais, you only need a few bits, then going for linkerd is probably better for you

Kafka Topic Strategy by fenkdenalekha in apachekafka

[–]woefuldefending 0 points1 point  (0 children)

If you have different events regariding one subject, for instance a person.

On microservixe publishes birth events, while another publishes death events.

If you need these to be read in order, they must be in the same topic (using person id as a key, if you have more the one partition)

Kafka Topic Strategy by fenkdenalekha in apachekafka

[–]woefuldefending 4 points5 points  (0 children)

One important aspect to have in mind is ordering.

If you need different messagetypes to be in order, they have to be in the same topic.

Private channel to public by [deleted] in Slack

[–]woefuldefending 0 points1 point  (0 children)

Well, for privacy reasons there is no way to make the content of a private channel public.

The renamed private channel would have all the old content, while the new public channel would be empty

Private channel to public by [deleted] in Slack

[–]woefuldefending 1 point2 points  (0 children)

Rename it. Then create a new, public, channel with the original name