EatFreshRupesh

Sort by

How does a @OneToOne relationship work in Spring Data JPA?

  • EatFreshRupesh
  • 0
  • 5

great read. simple explanations. funny though how the first one is the only one worth exploring if you ask me!

EatFreshRupesh

CascadeType is an option that specifies how related entities should be treated...

EatFreshRupesh

System.gc();

EatFreshRupesh

Great 5 minutes explanation. Implementing your own version of the Observable is a MUTS DO exercise for new developers...

EatFreshRupesh

when I read through the "Push vs Pull" section I couldn't help but think about the similarities to a "pull" based system like Kafka. In Kafka, consumers pull messages from topics. The advantage is Kafka just sits there so an infinite number of applications can read from Kafka in parallel.

EatFreshRupesh

The difference between Java SE and Java EE are negligible into todays programming world. I'm sure some will disagree but we use SE in production and have no issues operating at scale.

EatFreshRupesh

When people talk about a "Kafka consumer" they can mean different things...and it leads to some confusion.

EatFreshRupesh

Yes super annoying. I have to continuously manually reset offset to latest to get it to skip past the bad record and keep consuming. Not sustainable for sure. Any help is greatly appreciated on this.

EatFreshRupesh

You use the <span class='code-bite'>poll()</span> method to read messages from a given topic. This method takes a single argument of type <span class='code-bite'>Duration</span> specifying how long to listen for messages before returning an empty list of records.

EatFreshRupesh

Yes blazing..this is a common problem with using the <span class='code-bite'>JsonDeserializer</span> class provided by Kafka.

EatFreshRupesh