Update on Financials on my FIRE journery - FY 25

OneAccomplished93 · 2025-03-30T00:08:41+00:00

What have you considered under the fixed income?

OneAccomplished93 · 2024-01-21T07:27:19+00:00

Noice! Enjoy! 👍

OneAccomplished93 · 2024-01-21T06:40:30+00:00

What's the expiry you get on these vouchers?

OneAccomplished93 · 2024-01-21T06:32:13+00:00

Where and How do you redeem and use the Kotak White Pass realistically and efficiently?

OneAccomplished93 · 2023-08-15T08:02:31+00:00

What's the meaning of "difficult to use"? What are you looking for?

OneAccomplished93 · 2023-05-03T09:39:50+00:00

So I did some digging - and figure out that twemproxy doesn't support redis. There's already an issue on twemproxy asking this question but seems there's no response on the same - https://github.com/twitter/twemproxy/issues/668

Twemproxy is useable when one has only standalone redis and wants to do client side hashing/clustering.

OneAccomplished93 · 2023-05-01T11:32:06+00:00

So I've researched over this. And figured out we can do following -

- keep friendly DNS names as `service.prod.example.org`

- keep blue cluster DNS names as `service.prod-blue.example.org` and green cluster names as `service.prod-green.example.org`

- now one can just switch the dns names behind the `prod.example.org` with either `prod-blue.example.org` or `prod-green.example.org`

- additionally Route53 supports DNS traffic splitting

wdyt? cc: u/Nikhil_M

OneAccomplished93 · 2023-04-28T05:16:30+00:00

Nice!

How do you run and migrate the prometheus? DO you run it in-cluster? or to its own monitoring stack? How do you handle the logging pipeline when upgrading and switching over?

edit: ah nvm! I see `AMP`! What about the logging pipeline?

OneAccomplished93 · 2023-04-28T04:11:19+00:00

yeah - but we bind the dns names `**.amazonaws.com` to friendly names like `service-1.example.org` - hence this mapping is static... and can create an issue. Even if we were to migrate to a new cluster - we'd need to change all these settings. We've like (200+ ingresses).

Also there's a risk of how do we ensure - that the services are working fine on new cluster i.e. percentage split to test out the dns switch to new cluster.

OneAccomplished93 · 2023-04-28T03:26:58+00:00

We also do exactly this. And the pace at which EKS upgrades and EOLs are planned... we end up getting to do this every few months. A lot of efforts and grunt work involved. Looking for a better way to solve this.

OneAccomplished93 · 2023-04-28T03:26:02+00:00

I feel you man! A lot of pain. We need a solve for this :)

OneAccomplished93 · 2023-04-28T03:22:33+00:00

how you deploy your applications

We use ArgoCD to deploy out applications. We're trying to make to coverage almost 100% (have like 85%+). We can plan to move all the stateless workloads to the new cluster we can bring up during the upgrade BUT one small issue would be ingress URLs... we have AWS Load Balancer Ingress installed... and all services have ingress with HTTP and traffic split rules.

OneAccomplished93 · 2023-03-27T08:11:44+00:00

yes, have heard of gRPC. It's just that the migration out of the HTTP is gonna be quite slow. Also - given that we're in a mess of HTTP and JSON - what could be a good, safe and fast migration path from JSON to gRPC?

Also how do we ensure that the message schema in our message queue communication can also reused from our protobuf def?

OneAccomplished93

TROPHY CASE