This is also Tech in NYC. The average salary ($190k) is low for that market, so they're asking for an easier work-life balance.
Why they have 600 people is a question for management, no?
Kafka's not exactly hard to set up, especially for simple configs for low event rates. The justification from the link you posted:
> On the other side we have a wide range of services and applications that need
> access to this published content — there are search engines, personalization
> services, feed generators, as well as all the different front-end applications,
> like the website and the native apps. Whenever an asset is published, it should
> be made available to all these systems with very low latency — this is news,
> after all — and without data loss.
Why they have 600 people is a question for management, no?
Kafka's not exactly hard to set up, especially for simple configs for low event rates. The justification from the link you posted: