python-fake-data-producer-for-apache-kafka VS Stream-Framework

I had good experience with Aiven in the past, we needed something located in the EU: https://aiven.io/

Access to Aiven

One of the hardest questions we answer for our large enterprise customers is why they should choose Aiven instead of managing their own database and streaming services. It can seem counterintuitive that paying extra for a managed service can save you money. However, when we factor in economies of scale - particularly in regards to access to specialized knowledge and tooling - the case for managed services becomes clear. This was certainly the case for some of our MySQL clients earlier this year, where their investments in Aiven paid off in the form of a quietly managed bug fix.

And Kafka + Kafka Connect has https://www.confluent.io/ https://aiven.io/ https://upstash.com/ (and not quite Kafka, but protocol-compatible, https://redpanda.com/)

Fake data utility - https://github.com/aiven/python-fake-data-producer-for-apache-kafka

For PostgreSQL, similar offerings are: * Google Cloud SQL * AWS RDS * Digital Ocean Postgres * Azure Database for Postgres * Aiven, Instaclustr etc

Aiven - https://aiven.io/

Majority of companies layer DevRel on top of marketing as a sort of afterthought, and that’s usually a recipe for failure. All four co-founders at Aiven (the company where I work at) have been long-time open-source maintainers/contributors and highly value the work of DevRel. Similar examples can be seen at HashiCorp, where co-founder Armon Dadgar has been doing DevRel on the whiteboard since the early days of the company. Technical founders know the value of DevRel and know when to form a DevRel team. This is very different from bringing your first DevRel hire onboard and making them convince the leadership why the company needs DevRel in the first place. If your developer advocate needs to explain to the technical leadership the need for DevRel, that's a red flag for that individual and the company.

I wonder when Aiven https://aiven.io/ (or something similar) will start supporting hetzner.

I have looked into a getstream.io integration, however it seems that the Ruby SDK is really treated as a second class citizen. There's bugs with the documented API (I'm having issues even creating users and querying users), the usage of the gem is low and there is an open issue since May that no one has even looked at, which doesn't give me hope for long term support.

An ultralight social media app with no dependencies that can run on shared web hosting. It's an API like Getstream, so F/E is up to you. I've had a fork of it in production for 2.5 years on a subscription site that generates a small income.

Now, I'm seeking your advice and opinions. If you have experience using Stream or MirrorFly for chat implementation, I'd greatly appreciate any insights you can provide. Here are some questions I have:

Think about the edge that you can have over thousands other people looking for a job like you. One of the ways to do it – tailor your (even small) experience to the company you are applying to. E.g. Let's take a company like Stream that have an open-source Swift SDK, try to contribute to their SDK, maybe close some `good-first-issue`s here and there, do some documentation improvements, enrich their example app. So that when you feel like you are ready to knock their door – you already have an edge over others – you don't need onboarding (because you already know most of their codebase, you even completed your first few tasks while yet not being employed!)

This is absolutely absurd. I mean I 100% believe it happens, it's just absurd that the Tier 1 admin bot is this bad.

I too firmly believe the tier 1 admins are just this program - https://getstream.io/ And reddit doesn't want to admit that humans are not actually reviewing things

Really depends on so many variables, and comes down to knowing the audience. I built a lightweight social network api platform to do a lot of what getstream.io and OSSN does, but the way users engaged with it was nothing like what I expected. One use case, for example, would have been mostly satisfied with WordPress and Mailchimp. Forums are very familiar to people and still used by a lot of "I don't do social media" types. At the risk of making a sweeping generalization, if you have an older target audience they will be happy with a forum. If you have a younger target audience they will prefer the sequential post / react style of interacting, like Discord or Instagram.