Oleh

@elonmusk WTF Elon, did you watch the video?

🤨

"Data Intensive Applications" Daily - MySQL is not detecting Lost Updates in term of separate snapshots transactions

"Data Intensive Applications" Daily - snapshots read as an alternative

"Data Intensive Applications" Daily - no "dirty read" and no "dirty write" is called READ COMMITTED

"Data Intensive Applications" Daily - "dirty write" can be prevented by delaying concurrent writes

"Data Intensive Applications" Daily - "dirty write" is about parallel writes to rows that was earlier written by CONCURRENT TRANSACTION THAT IS STILL IN PROGRESS

"Data Intensive Applications" Daily - transactions read dirty - is about reading uncommitted writes of parallel transaction

"Data Intensive Applications" Daily - C in ACID transaction shouldn't be there: #serverside #transactions #techshock

Data Intensive Applications daily (on Transactions):

Data-intensive applications [Partitioning]: "Zookeeper for registering and load balancing partitioned databases"

Similar is user post comments

From Designing Data Intensive application book: "CassandraDB use case: social media site, one user may post many updates. Make compound index by userID and postTime. That's how you would be able to effectively retrieve post by user with ordering applied."

#java #springboot stackoverflow.com/questions/7105… Run in this issue in my project. That was quite unexpected behaviour.

#effectivejava Overloading in general bad, Overriding - good

#effectivejava Would be great if Java floating point literals were BigDecimal by default.

#EffectiveJavaToday 2 in 1: most local scope variable + 1 time computations

#coding Great example of cleaning varargs arguments passing with at least 1 arg required (Effective Java, Joshua Bloch)

Щастя девелопера в простих речах: IDE, version control, автозаміна

Часом мотивує та незламність, а часом зайобує