Last week the good old Gunnar Morling launched an interesting challenge about ordering 1 billion rows in Java. Like my ex colleague and friend Robin Moffat, I’m not at all a Java expert, and while Robin used DuckDB to solve the challenge, I did the same with PostgreSQL and ClickHouse.

When sinking unix timestamps from Apache Kafka to OpenSearch/ElasticSearch using the dedicated connector, they are not recognized by default as timestamp in the target tech.

You have an Apache Kafka topic that you want to consume via REST APIs (think curl or just a web browser), how to do it? The reply is Karapace an Open Source (Apache 2.0) tool providing Schema Registry and REST proxy functionality. Let’s check out how to quickly run it on Docker. Step 1: the Apache Kafka® Cluster You need an Apache Kafka cluster up & running, if you have one already you can skip to the next section.

In the modern world, it’s rare to have the data in the same shape and platform from the beginning till the end of its journey. Yes, some technologies can achieve quite a good range of functionalities but sometimes at the expense of precision, developer experience or performance. Therefore, to achieve better or faster results, people might select a new tool for a precise task and start an implementation and integration process to move the data around.

So… what does a Staff Developer Advocate do, and how is it different from the Senior Developer Advocate role you were doing before?

I got this question three times in the last two weeks after my promotion from Senior to Staff (🎉🎉🎉🎉), from various people in my network.

Technical scalability is one of the main drivers of a data platform, as mentioned in the SOFT methodology. But what are the options? In this blog we’ll evaluate the direction of scalability and the tradeoffs you might encounter in the decision process.

Companies are in a continuous motion: new requirements, new data streams, new technologies are popping up every day. When designing new data platforms supporting the needs of your company, failing to perform a complete assessment of the options available can have disastrous effects on a company’s capability to innovate, and making sure their data assets usable and reusable in the long term.

I started following the #PGSQLPhriday initiative a couple months back but never had the time to properly sit down and write due to conference traveling. Therefore I was super happy to be at home this week and find out that PGSQL Phriday #003 theme is about the PostgreSQL community!

If you’re reading this, there are good chances you’re thinking, writing or iterating over an abstract for a conference. The post is about little tips I learnt in more than 8 years of prepping for conferences and in 1 year or reviewing internal abstracts at Aiven before they are submitted for a conference.

Sometimes you want to query a remote InfluxDB server to understand the data in it. This can be done via cURL as explained in the InfluxDB docs