Production use? about go-linq

[cleitonmarx]

What type of application is it?

The application is an event ticketing API

How performance critical is it?

Sometimes we have peaks in numbers of requests, so performance is critical. To improve performance in this scenarios, we are reducing the database calls and removing the aggregation processing from the database and using go-linq to help us with the aggregations processing and with complex/nested objects composition in the API server side, what is easier to scale.

If you are using go-linq since May, you must have used v1. So, can you give any details on migrating to v2?

Unfortunately, I didn't have the chance to migrate to the v2, but I'm considering to make it soon.

[kalaninja]

@bsideup it preserves the order when the goroutines are starting, but then result are put into the channel as soon as the job is done. So you may introduce a new parameter, then put it inside the result and use smth like

FromChannel(results).OrderByT(
        func(result ResultType) int { return result.Priority },
    )

thanks @cleitonmarx for new "-T" methods syntax.

[cleitonmarx]

Hey @frankandrobot, I have been using it in production since May. Works fine! 😃

[kalaninja]

@cleitonmarx Thanks for the reply. Can you give any more details on the use case? What type of application is it? How performance critical is it?

If you are using go-linq since May, you must have used v1. So, can you give any details on migrating to v2?

[bsideup]

We use go-linq in http://github.com/zeroturnaround/configo to improve the readability and make it a bit more functional

[ahmetb]

@bsideup thanks for the answer. I guess this issue is not something we can “resolve” per se. We have nice changes (like generic functions) coming up with v3, make sure to check the new stuff out!

[bsideup]

@ahmetalpbalkan generic functions? I think you mean interface {}s everywhere, right?

[cleitonmarx]

@bsideup You can check it out the new generic functions preview here:
https://github.com/ahmetalpbalkan/go-linq/tree/v3-dev#generic-functions

[bsideup]

@cleitonmarx oh, so you decided to implement #26 ? Cool! Will check it soon.

[ahmetb]

Yeah and I was thinking this idea sounds familiar lol. We observe 5-15x performance penalty (see benchmark_test.go) but it yields cleaner code of course.

[bsideup]

@ahmetalpbalkan Errr... looks like AsParallel().AsOrdered().Select(...).AsSequential() is gone, and with channels API it's totally unclear how to do the same :(

[kalaninja]

@bsideup Can you give an example of what you are trying to do?

[bsideup]

@kalaninja sure, luckily it's open sourced:
https://github.com/zeroturnaround/configo/blob/master/sources/composite.go#L27-L38

[kalaninja]

@bsideup The "Concurrent" example on our website does mostly the same thing.

The idea is to start a new goroutine per each item manually, output each result to the channel and close the channel when all the goroutines are done. FromChannel() method waits until the channel is closed to continue iterating the query.

I know that the current syntax is messy, it is more like a workaround. But it gives you more control on what you want to do, and making "plinq" api for the current version is also on our todo list.

[bsideup]

Does it preserve the order?

[ahmetb]

Closing as it is now answered.