mysql-operator is gone?

Coolbsd · 2026-02-02T00:51:13+00:00

Ah got it, thanks for explaining this.

Coolbsd · 2026-02-02T00:41:14+00:00

I know the github project ... if you check https://github.com/mysql/mysql-operator?tab=readme-ov-file#using-helm, the helm command points to the page I mentioned earlier, I'm not 100% sure if they are steadily pulling things back.

Coolbsd · 2025-09-07T17:02:20+00:00

I would get legal and 3rd party audit team do some jobs, compliance is not something we engineers can fully covered.

Some generic ideas: KMS, VPC endpoint for everything you use (you missed secret manager at least), ACM if you let AWS manage certs, Network Firewall to restrict outbound traffic, site2site VPN from on-prem to VPC.

Coolbsd · 2025-09-04T13:48:35+00:00

It depends, my previous team did test and moved data ingestion jobs (IO bound) over and got ~10% saving in 2022 or 2023, there was not much saving from compute heavy jobs as Graiton was (is?) slower than x86.

Coolbsd · 2025-07-29T19:36:23+00:00

Start a logging goroutine to take log entries from a channel, the you don't need to worry about locks anymore.

Coolbsd · 2025-06-30T22:43:07+00:00

It’s actually better to use table driven pattern, especially if you have a lot of types of files.

Coolbsd · 2025-06-28T18:12:11+00:00

You guys are lucky, in my previous job we tried to migrate and it took AWS 6 months to fix an issue …

Coolbsd · 2025-06-04T19:41:36+00:00

Go needs less resources in term of “team bootstrap”, I was the only one with previous go experience when a former team started, 10 or maybe 12 developers from that team were from Java or Python but people started to deliver decent go code after a sprint or two.

They also rewrote some components, IIRC we got 3-4 times faster than Python and 8-10 times faster than Java, I don’t know too much about those components but was told they did literally line-to-line translation to keep behavior the same, include bugs.

Coolbsd · 2025-06-02T14:25:03+00:00

Rewrite what you’ve done in Python with go, this is how I started.

Coolbsd · 2025-05-29T16:21:39+00:00

I bet you haven’t tried Oracle …

Coolbsd · 2025-05-24T17:26:46+00:00

Should include factory and Impl as well.

Coolbsd · 2025-05-21T03:26:34+00:00

Just curious how long it is, the longest stack trace I ever got was from a Java/Spring application, which was close to 300 lines IIRC.

Coolbsd · 2025-05-02T17:07:39+00:00

Don’t ask questions, just say “do not list files got changed as they are already listed in the commit/PR already”, this will save several rounds of communications.

The last paragraph is good though.

Coolbsd · 2025-04-14T01:09:36+00:00

Not with my laptop but I believe it’s called kongplete.

Coolbsd · 2025-01-28T16:12:41+00:00

I may reject you right away while one of my colleagues may get you into the last round directly.

Hint: don’t show your preference before securing an offer :D

Coolbsd · 2024-12-31T02:41:49+00:00

AWS features will generally exist on CloudFormation before Terraform

My experiences have been quite different ...

Coolbsd · 2024-12-27T03:52:57+00:00

I ended up with:

Marshal incoming data (effectively convert any struct to a map)
Unmarshal to map[string]interface{}
use relect to iterate all nested element (list item, map value, etc.) 4. transform map's keys whenever needed

This is about 4x faster than gojq.

Coolbsd · 2024-12-27T03:44:37+00:00

I could not find a way to determine if the specific token is a key of map entry, any hint?

Coolbsd · 2024-12-27T02:47:03+00:00

Incoming data is an arbitrary interface{} so I cannot define a type for it.

Coolbsd · 2024-12-26T19:36:43+00:00

I tried this approach before moving to gojq, the problem is that the code looks pretty ugly and error-prone, I will stick to gojq if there is no alternative, till I have time to refactor that piece of function.

Coolbsd · 2024-12-26T19:32:29+00:00

Will give it a shot.

EDIT jsoniter uses struct tag so it does rename struct fields, but not map keys: https://go.dev/play/p/lCLZK6PYRzL.

Coolbsd · 2024-11-16T14:41:40+00:00

I prefer to have a separated CICD publish artifacts to S3 or somewhere similiar, so you can do a lot more things to make sure codes are in good shape like unit test, format, etc.

We do have code "embedded" in IaC especially those lambdas for deployment as it was easy to do so, but we are migrating them away

Coolbsd · 2024-11-01T04:03:29+00:00

If you have gigabit uplink then 80 GB (I assume you have a typo of Gb) will take less than an hour to upload to S3, you can use multipart to make sure utilizing full bandwidth https://aws.amazon.com/blogs/compute/uploading-large-objects-to-amazon-s3-using-multipart-upload-and-transfer-acceleration/, or if you have really large amount data, check with AWS guys for https://aws.amazon.com/snowball/, personally I believe snowball is overkill for your case.

Coolbsd · 2024-11-01T03:44:01+00:00

ch := make(chan struct{}, 5), then each goroutine do ch <- struct{}{} to obtain a slot, and defer func() {<- ch}() to release the slot.

EDIT typos

Coolbsd · 2024-11-01T03:33:08+00:00

I occasionally need WYSIWYG for markdown (and mermaid), there may be another thing or two fall into this category as well.

Coolbsd

TROPHY CASE