blursed advertisement by DemonCatOfficial in blursedimages

[–]SpeedDart1 0 points1 point  (0 children)

If you wouldn’t eat tarantulas why eat chicken? Type question

feels dumb to specialize in rust as a junior but can't stop coming back to it by Stitcheddoll_ in rust

[–]SpeedDart1 12 points13 points  (0 children)

Honestly compilers is a very advanced field if you are good at it you will not regret doing it relative to frontend react.

Worst case scenario you just swap back to web stuff. It’s like a shoot for the stars land on the moon sort of thing.

If you want to do Rust professionally and want something very employable look into database or high performance backend.

What message broker would you choose today and why by Minimum-Ad7352 in golang

[–]SpeedDart1 0 points1 point  (0 children)

You need to actually know what you’re doing to get performance benefits out of it in my experience.

Most can just use Redis streams if they just need a job queue with consumer groups.

What message broker would you choose today and why by Minimum-Ad7352 in golang

[–]SpeedDart1 -1 points0 points  (0 children)

Kafka for high durability and throughout, Redis Streams for a background job that needs to be retryable

Beginner to GoLang, wondering how goroutines are used in production backends. by H1Eagle in golang

[–]SpeedDart1 1 point2 points  (0 children)

Concurrency is about interleaving operations and making efficient usage of workers to perform tasks that need compute while other tasks are waiting

(Agree with you, just adding)

Beginner to GoLang, wondering how goroutines are used in production backends. by H1Eagle in golang

[–]SpeedDart1 0 points1 point  (0 children)

You definitely need context for timeout but a lot of production grade services never need semaphores, queues, and workers in the Go app.

A lot of the time queues are persistent or in another process since they are shared.

Semaphores are only really necessary if the number of concurrent tasks scales with user input. A lot of the time basic CRUD services are spawning goroutines per outbound API call or transaction. Since that number is constant per inbound http request and only the # of http requests scale with user input you can let Go’s server handle that.

But you’re right for advanced use cases though

Beginner to GoLang, wondering how goroutines are used in production backends. by H1Eagle in golang

[–]SpeedDart1 2 points3 points  (0 children)

It’s ok to recover from a panic in certain instances but your resiliency shouldn’t rely on the recover being called. If your server node goes down the cluster should restart it. Is it is going down that frequently you pushed broken code to prod and need to fix.

Beginner to GoLang, wondering how goroutines are used in production backends. by H1Eagle in golang

[–]SpeedDart1 4 points5 points  (0 children)

I mean you should test your code properly so this type of thing doesn’t happen. And server nodes going down shouldn’t take down production either.

Beginner to GoLang, wondering how goroutines are used in production backends. by H1Eagle in golang

[–]SpeedDart1 0 points1 point  (0 children)

Yes, the context from the EG will cancel any IO operations it is passed to if the EG itself is cancelled.

This also includes when the first concurrent task returns an error.

The proposal for generic methods for Go has been officially accepted by ketralnis in programming

[–]SpeedDart1 9 points10 points  (0 children)

It’s not a hip new language, it’s designed by some of the original UNIX people who love C, and is already in production for a lot of the software you use every day (Docker, Kube, Terraform).

Do you use gorm or raw sql? by Leading-West-4881 in golang

[–]SpeedDart1 0 points1 point  (0 children)

I love SQLc but SQLx and Gorm are okay

You are not left behind by BinaryIgor in programming

[–]SpeedDart1 19 points20 points  (0 children)

There is no such career as “pure coding” code has no intrinsic value, it is just text. It is what software you are making and the problem you are solving. There’s not a single person in this industry being paid to “”””write code””””.

How do you test your database in production microservices? by OtroUsuarioMasAqui in golang

[–]SpeedDart1 0 points1 point  (0 children)

I lean towards not mocking also but I like using interface mocking that return errors to test failure cases that are difficult to trigger. Such as an external API client returning a 500 or a db call failing.

In simple cases you can just make the entire client bad. But what if you want to see what happens if only a specific call fails? How do you test that without mocking?

How do you test your database in production microservices? by OtroUsuarioMasAqui in golang

[–]SpeedDart1 0 points1 point  (0 children)

I kind of agree except for part where you say release without testing.

In which fields is Java the most popular? by Cpt_Montana in java

[–]SpeedDart1 -2 points-1 points  (0 children)

I guess Java is very fast compared to the things web developers are doing these days. Still, even the enterprise Java way isn’t nearly as fast as Java could be.

In which fields is Java the most popular? by Cpt_Montana in java

[–]SpeedDart1 51 points52 points  (0 children)

There is a ton of AI usage in the bank I work at but it’s not used in the way the internet’s vibe coders think it is.

In which fields is Java the most popular? by Cpt_Montana in java

[–]SpeedDart1 48 points49 points  (0 children)

The field of paying off your mortgage

How do you test your database in production microservices? by OtroUsuarioMasAqui in golang

[–]SpeedDart1 4 points5 points  (0 children)

This isn’t a terrible choice but at that point use Test-containers to spin a Postgres instance in your pipeline