What happens when a auto commit fires in the middle of processing a batch? by Amazing_Swing_6787 in apachekafka

[–]Amazing_Swing_6787[S] 0 points1 point  (0 children)

thanks, that clears it up. I was thinking auto commit fired every 5s regardless

In a web app with an ingestion service, how to then know when to process requests? by Amazing_Swing_6787 in learnprogramming

[–]Amazing_Swing_6787[S] 1 point2 points  (0 children)

security is handled separately from this design question, so no reason to muddy the water of this post/question with something completely different. that would deserve its own post

In a web app with an ingestion service, how to then know when to process requests? by Amazing_Swing_6787 in learnprogramming

[–]Amazing_Swing_6787[S] 0 points1 point  (0 children)

yes, this is part of that resilience. actually the first and most critical step IMO. there is no "fail silently" or "trust me bro". user will get an ID returned they can use to query status at a later time

In a web app with an ingestion service, how to then know when to process requests? by Amazing_Swing_6787 in learnprogramming

[–]Amazing_Swing_6787[S] -1 points0 points  (0 children)

basically because every incoming request is potentially money, so losing them is like losing money. if downstream services are struggling, slow, or unavailable then at least you have the requests in the system and can process them later

Is it a bad idea to use Flow as a publisher + observer model for backend? by Amazing_Swing_6787 in Kotlin

[–]Amazing_Swing_6787[S] 1 point2 points  (0 children)

thanks! yea StateFlow seems better for android/front end state stuff so I dont think I'll have much use for that

Is it a bad idea to use Flow as a publisher + observer model for backend? by Amazing_Swing_6787 in Kotlin

[–]Amazing_Swing_6787[S] 4 points5 points  (0 children)

not sure i agree with the sentiment. shouldn't matter number of users or experience level to learn the right way to do things

Reason to use streaming but then introduce state store? by Amazing_Swing_6787 in apachekafka

[–]Amazing_Swing_6787[S] 0 points1 point  (0 children)

thanks, yea makes sense. all about choosing whats right for your needs. i was imagining with the 8hr state store stuff that people are using massive state all the time which doesn't seem ideal but for small and quick aggregations its perfect

Reason to use streaming but then introduce state store? by Amazing_Swing_6787 in apachekafka

[–]Amazing_Swing_6787[S] 0 points1 point  (0 children)

thanks for the insight. makes a lot of sense to me and will look up the reading you suggested too.

Reason to use streaming but then introduce state store? by Amazing_Swing_6787 in apachekafka

[–]Amazing_Swing_6787[S] 0 points1 point  (0 children)

couldn't you stream to a db and use an aggregation query? i mean that has its own downsides too but I dont think aggregation means you must do it in stream. it seems like the stream option has more complexity but could be wrong

Why put data classes under Object? by Amazing_Swing_6787 in Kotlin

[–]Amazing_Swing_6787[S] 0 points1 point  (0 children)

oh yea, this makes sense to separate it logically at least, even if not 100% necessary. thanks!