Tweet

@debezium

More from @gunnarmorling

Gunnar Morling 🌍

@gunnarmorling

Sep 5, 2021

@java

⏱️ Just ten more days until the release of @java 17, the next version with long-term support! To shorten the waiting time a bit, I'll do one tweet per day on a cool feature added since 11 (previous LTS), introducing just some of the changes making worth the upgrade. Let's go 🚀!

🔟 Ambigous null pointer exceptions were a true annoyance in the past. Not a problem any longer since Java 14: Helpful NPEs (JEP 358, openjdk.java.net/jeps/358) now exactly show which variable is null. A very nice improvement to #OpenJDK, previously available only in SAP's JVM.

9⃣ Varying load and new app instances must be started up quickly? Check out class-data sharing (CDS), whose dev exp has improved a lot with JEP 350 (Dynamic CDS Archives, Java 13); also way more classes are archiveable since Java 15. More details here: morling.dev/blog/smaller-f…

Read 11 tweets

Gunnar Morling 🌍

@gunnarmorling

Aug 9, 2021

https://twitter.com/gunnarmorling/status/1423311149748166657

#Postgres as an event store -- Thanks a lot for all the super-insightful answers 🙏! It looks like using a jsonb[] for modeling an event stream isn't ideal performance-wise, but several great pointers to using #Postgres for event sourcing here. Mentioned solutions include... 1/4

https://twitter.com/gunnarmorling/status/1423311149748166657

@marten_lib

- FactCast: docs.factcast.org
- Message DB: github.com/message-db/mes…
- @marten_lib: martendb.io
- @axonframework: axoniq.io
- crabzilla: github.com/crabzilla/crab… (an event sourcing exploration using @vertx_project)

2/4

@adamwarski

Two really read-worthy blog posts on the topic of using #Postgres as an event store:

- dev.to/kspeakman/even… by Kasey Speakman
- softwaremill.com/implementing-e… by @adamwarski

3/4

Read 4 tweets

Gunnar Morling 🌍

@gunnarmorling

Dec 3, 2020

@apachekafka

A short 🧵 on @apachekafka topic creation (triggered by @niko_nava, thanks!): who should create Kafka topics, how to make sure they have the right settings, how to avoid dependencies between producer and consumer(s)? Here's my take:

2⃣ Don't use broker-side topic auto-creation! You'll lack fine-grained control over different settings for different topics; Merely polling, or requesting metadata, will trigger creation based on global settings. Plus, some cloud services don't expose auto-creation to begin with.

3⃣ Instead, the producer side should be in charge of creating topics. There you have the information and knowledge about the required settings (replication factor, no. of partitions, retention policy, etc.) for each topic. Depending on your requirements, different approaches...

Read 8 tweets

Gunnar Morling 🌍

@gunnarmorling

Jul 31, 2020

⏰ What time is it? Time for a #Mythbusters thread -- #Serverless edition!

Agreed, the term is sub-par. But hear me out, the architecture is not. Let's talk about a few common misconceptions about Serverless!

1⃣ "Serverless means no servers"

There *are* servers involved, but it's not on you to run and operate them. Instead, the serverless provider is managing the platform, scaling things up (and down) as needed. Less things to take care of, billed per-use.

Myth: BUSTED!

2⃣ "Serverless is cheaper"

Pay-per-use makes low/medium-volume workloads really cheap. But pricing is complex: no. of requests, assigned RAM/CPU, API gateways, traffic etc. Depending on your workload (e.g. high, sustained), other options like VMs are better.

Myth: Kinda BUSTED!

Read 8 tweets

Gunnar Morling 🌍

@gunnarmorling

May 10, 2020

@java

Thanks for all votes and insightful answers to the poll on usage of @java's var! Not unexpectly, replies range from "using var all the time" to "don't see the point of it". Yet one third never using var at all was a surprise for me. Some repeating themes from replies in this 🧵.

https://twitter.com/gunnarmorling/status/1257743776367460353

1⃣ Readability vs. writability: some argued var optimizes for writing code (less characters to type) at the cost of reading code (less explicit type info). I don't think that's the intention behind var. In fact, more (redundant, repetitive) code may read worse.

2⃣ var only or primarily used in test code: described by several folks as a good starting point for getting their feet wet with local variable type inference, before using it more widely.

Read 7 tweets

Gunnar Morling 🌍

@gunnarmorling

Aug 28, 2019

@ApacheKafka

Message transformations (SMTs) are an invaluable feature of @ApacheKafka Connect, enabling tons of use cases with a small bit of coding, or even just configuration of existing SMTs ready to use. Here are some applications in the context of change data capture: (1/7)

* Converting data types and formats: date/time formats are the most common example here, e.g. to convert milli-seconds timestamps into strings adhering to a specific date format (2/7)

* Creating an "anti-corruption layer", shielding consumers from legacy schemas or ensuring compatibility after schema changes; e.g. could use an SMT to choose more meaningful field names, or re-add a field using its old name after a column rename, easing consumer migration (3/7)

Read 7 tweets

Share this page!

Gunnar Morling 🌍

People who liked this thread also liked...

Try unrolling a thread yourself!

More from @gunnarmorling

Gunnar Morling 🌍

Gunnar Morling 🌍

Gunnar Morling 🌍

Gunnar Morling 🌍

Gunnar Morling 🌍

Gunnar Morling 🌍

Did Thread Reader help you today?

Don't want to be a Premium member but still want to support us?

Like this author's thread?