Faster – A key-value store for large state management

Re:Faster – A key-value store for large state management by softwarefounder on Friday June 08, 2018 @01:51PM (#17267942)

This is getting down-voted, but there's some truth here.

I didn't adopt .NET Core until v2, and happy I waited. Much stronger support from MSFT now, and a much more stable framework.

[ Parent | on HN ]

Re:Faster – A key-value store for large state management by noir_lord on Friday June 08, 2018 @02:34PM (#17268418)

Insane performance on the most recent techempower benchmarks (usual proviso of all bencharks are meaningless etc etc.) they've caught Go with fasthttp already on one of them.

[ Parent | on HN ]

Re:Faster – A key-value store for large state management by setquk on Friday June 08, 2018 @04:47PM (#17269545)

For typical workloads that doesn’t make a whole load of difference. 10% difference in API meh. 90% of the latency and load is what goes on behind that and that’s your party not theirs.

[ Parent | on HN ]

Re:Faster – A key-value store for large state management by Thaxll on Friday June 08, 2018 @03:54PM (#17269131)

Not sure if it's good or bad, fast http is made by one guy and it's not official, aspcore is done by MS and dozen of engineers work on it.

[ Parent | on HN ]

Re:Faster – A key-value store for large state management by manigandham on Friday June 08, 2018 @08:57PM (#17270906)

ASP.NET Core is a full-stack web framework and has about 100x more features and support. fasthttp is quick but it doesn't even implement the http spec completely.

[ Parent | on HN ]

Re:Faster – A key-value store for large state management by noir_lord on Friday June 08, 2018 @04:25PM (#17269387)

both top the charts and are within 1% of the fastest on the chart so pretty good for the go dev and MS.

[ Parent | on HN ]

Re:Faster – A key-value store for large state management by setquk on Friday June 08, 2018 @02:04PM (#17268109)

Exactly the other side of my point. Once it’s supoorted it’s good.

[ Parent | on HN ]