majidazimi
Joined 13 years ago
Joined 13 years ago
- if you save 60% of your income, your lifestyle will be severely damaged and you won't become a spender all of a sudden the day after retirement.
- If you save 5% of your income, then you won't be able to lower your lifestyle once you retire.
Saving 15/20% of income isn't a magic number. But it's something that doesn't damage your lifestyle + it accumulates to a meaningful amount that saves your ass in old times.
Going aggressive in either direction (spending or saving) is not the right mindset, because you won't be able to CHANGE once you adopt a specific lifestyle.
Yes it is. Developing any short term job -- that runs multiple seconds and goes away -- like lambda or k8s jobs with Java is meaningless for exactly this reason. The startup time is longer than the run time.
The same is not true for JS. The most mature libraries depend on absurdly vague libraries that no one has ever reviewed.
1. A single partition is stored in one node (replicas on another nodes). With this, introducing new nodes takes very long time to replicate large partitions, because it can replicate one partition from only one node (leader of the partition). On Pulsar each segment of partition is stored in a different bookkeeper node.
2. Because of 1, if two consumers read different parts of a partition that are far from each other, they will compete over disk bandwidth. In Kafka consumer can not read from replica node. If a topic is really popular and many consumers try to read from it (from different parts of the file which makes OS page cache useless), total consumption rate is limited to disk bandwidth of a single node. But in Pulsar each consumer can read from different brokers. Catch up consumers won't trash streaming consumers in Pulsar.
These are not problems that can be fixed easily. Additionally, in the realm of streaming the difference between Flink and Spark is day and night. The low watermark feature that Flink offers makes them behave fundamentally different.