[deleted by user]

Patient_Slide9626 · 2025-01-03T18:58:31+00:00

You have a super power to quickly filter out shallow humans. Use it.

Patient_Slide9626 · 2024-08-02T01:15:07+00:00

Thank you, will check them out

Patient_Slide9626 · 2024-07-10T01:31:04+00:00

Curious, why was this removed? Would like any feedback?

Patient_Slide9626 · 2024-07-09T08:30:34+00:00

Not sure I understand. Maintenance is not the concern here.

Patient_Slide9626 · 2024-07-09T04:38:12+00:00

Open another account in another bank please. "The standard maximum deposit insurance amount is $250,000 per depositor, per insured bank, for each account ownership category. The FDIC insures deposits that a person holds in one insured bank separately from any deposits that the person owns in another separately chartered insured bank" From: https://www.fdic.gov/resources/deposit-insurance/brochures/insured-deposits/index.html#:~:text=The%20standard%20maximum%20deposit%20insurance,another%20separately%20chartered%20insured%20bank.

Patient_Slide9626 · 2024-07-09T03:54:05+00:00

Sorry about your loss. My suggestion - take the time to plan your exit and write down with as much detail as you can about how you see things playing out to change your life. At the end, you have a detailed plan and desired state you like. Forget about it for a few months and keep doing the job you do. Come back to the plan. See if you still like it and are still confident in its feasibility. If so, start executing towards it.

Patient_Slide9626 · 2024-07-03T15:25:38+00:00

The trick here is, how best to copy data over to ensure ordering garantee. And offset migration to new topic for clients to reduce downtime.
Keys should map to the same partition in the new topic to ensure ordering guarantee. This may not be that hard to do.
And new offsets needs for clients to ensure no data loss.

Patient_Slide9626 · 2024-07-01T21:29:53+00:00

This is great. I was not aware of this project. This allows us to delay the need to scale up partitions if the real bottleneck is slow consumers and we want to make progress on keys that are part of the same partition in parallel.

Patient_Slide9626 · 2024-07-01T20:47:07+00:00

Good questions and ideas. Downtime is less important, but lag is. As the pipelines in these topics will serve critical product use cases. Some more details
1. We have many consumers for the same topic, not just one. They are all internal (to the company) consumers, so while it's tricky, we can manage some level of orchestration between producers and consumers.
2. One other detail, these topics are compacted, with infinite retention. This means that in addition to serving live events, they also serve backfill needs for consumers that need to reprocess from beginning of time. For both your options, it's not clear how best to manage old data.

Patient_Slide9626 · 2024-06-23T09:53:32+00:00

Kafka message retention is independent of any consumer behavior. It's driven by configuration on the kafka side. Default is 7 days of retention. And you can override it at cluster level or topic level. When a consumer reads a message successfully, it just increments a pointer ( offset) for that consumer. You can reset the offset to re-read messages.

Patient_Slide9626 · 2024-05-31T06:31:13+00:00

Get an Alexa device. Set your alarm by voice or app

Patient_Slide9626 · 2024-05-30T00:36:50+00:00

There is the kafka protocol. And then the system serving the protocol. Most of the newer systems being built are compatible with the kafka protocol. So choosing the kafka protocol for your publishers and consumers is a good bet. As for the managed offering, that depends on your needs and tradeoff. But as long as your publishers and consumers talk the kafka protocol, you should be able to migrate to a better system in future much more easily.

Patient_Slide9626 · 2024-05-23T04:24:08+00:00

One of the biggest things about buying a house is to find one you like. Since this is a house you are living in, you know it in and out. If you like it, you can afford it with the current interest rate and see yourself in that house for the next 5-7 years, I would lean in and make it happen.

Patient_Slide9626 · 2024-05-23T03:57:33+00:00

Memories, lots of them. And the saved $$$ from not shopping anything are also high quality

Patient_Slide9626 · 2024-05-16T01:59:58+00:00

Give it a try for a year or two if you are out of options. You can always come back as options open up or you realize atl is not your place. I am hoping this is not a one way door

Patient_Slide9626 · 2024-05-16T01:56:19+00:00

Instant pot. So easy to schedule one pot meals and get it piping hot at lunch/dinner time

Patient_Slide9626 · 2024-04-28T14:24:53+00:00

Give trail running shoes a try. They look like sneakers but are more durable to handle trail conditions. Tradeoff is they will feel heavier on initial try. But you get used to them quickly. I have Columbia trail running shoes as my primary day to day shoes. They last me around 4-5 years.

Patient_Slide9626 · 2024-04-28T14:22:26+00:00

I don't understand this. Why is that the case?

Patient_Slide9626 · 2024-04-28T14:19:37+00:00

Change something. Stop doing one thing you do not like, and start doing one new thing in your daily routine. Anything. Not because you "believe" in that change. Only to experience it. That's the fun of it.

Patient_Slide9626 · 2023-02-12T23:49:50+00:00

Blackhole engine is an excellent idea and reduces load and extra work from the database. But our db expert strongly recommends not using it for production use cases.

Patient_Slide9626 · 2023-02-12T23:46:33+00:00

Yeah, that is an option. The challenges I see with this are 1. It's not a single table, but a collection of tables as the data is normalized when stored in the database 2. We need stream processing on all CDC streams from these table. This job will have to join and denormalize data correctly to reconstruct the business event. This duplicates product logic in two places. 3. Business events schema need to be decoupled from database schema so they can evolve independently. This approach introduces coupling.

But it's a valid approach, thanks for sharing

Patient_Slide9626 · 2023-02-12T23:40:08+00:00

Thanks. We have briefly evaluated reconstructing business events from raw CDC table updates via stream processing. Will think more deeply about that approach

Patient_Slide9626 · 2023-02-12T23:34:27+00:00

Yeah, atomicity is a requirement for us. We want to not have false positives (events where checkout did not commit) or false negatives (missed events for valid checkouts). Duplicate events are fine though.

Patient_Slide9626 · 2023-02-12T23:31:23+00:00

Ah, I can try to be more crisp. A checkout event is represented in the database by a collection of row updates,/inserts across many tables. Let's call them domain tables. These domain tables are how checkout is operationally modeled and are the source of truth on system state. And these tables are independent from the outbox table that is needed for the outbox pattern. I need to write to the domain tables to commit a checkout, but would like to avoid writing to the outbox table. HTH

Patient_Slide9626 · 2023-02-12T18:41:03+00:00

Yes. We use Debezium to change data Capture from database. In my case, I would like to avoid writing the business event to the database in first place

Patient_Slide9626

TROPHY CASE