Live data from Hacker News

Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

github.com

21–30 of 43 posts

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#21

I think this sort of project is in short supply. Kubernetes seems to have sucked all the air out of the room, and yet we need variety and different approaches to grow. I look forward to (trying) to replicate something similar for my own understanding. Any architecture docs will be gratefully recveied

I think the architecture of something like K8s pretty well sums up all (or most) of the components needed for a distributed system. What's really needed today is differentiation on the actual end result of that design. We need simpler technology that works better, and that's hard; it's not enough to have a fancy idea and throw together some lines of code. That's been done, and it kinda sucks. What's needed now is to focus on making it easier and simpler to do specific things.

For example: most people just want to receive infinite HTTP requests and route them to custom business logic, automatically scaling as needed. So why can't I just push a button and make that happen? AWS ECS has a command-line client now that attempts to do that, but it's clunky and unreliable. And K8s doesn't have anything like that; it's all hand-crafted YAML files and mountains of custom cluster configuration. I just want to run some code at scale. And we've implemented that (scaling web requests/business logic) a million times by now. But it's never really gotten significantly easier.

Docker is a good example of the amount of work you need to pour into a technical solution to make it a game-changing user solution. Docker is like 50 different technical solutions rolled up into one user-friendly command-line tool and a backend daemon. You could do most of what Docker does in LXC, but it was painful. Docker made it easy. That's what we need for running services at scale in general. Docker Swarm was created basically to scratch that itch, but it still hasn't really taken off. I'm hopeful it does one day.

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#22
post #10

It would create more interesting conversation if you highlighted the merits of your design rather than superficial measures like CNCF blessings (there are thousands of such projects) and GitHub stars (easily gamed).

I am eager to know how to game GitHub stars. Funding agencies love metrics and random KPI so I would love to deliver...

Right up to the moment your funding agency calls you out during DD and then you are in deep trouble. Would not recommend.

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#23

I think this sort of project is in short supply. Kubernetes seems to have sucked all the air out of the room, and yet we need variety and different approaches to grow. I look forward to (trying) to replicate something similar for my own understanding. Any architecture docs will be gratefully recveied

I think the architecture of something like K8s pretty well sums up all (or most) of the components needed for a distributed system. What's really needed today is differentiation on the actual end result of that design. We need simpler technology that works better, and that's hard; it's not enough to have a fancy idea and throw together some lines of code. That's been done, and it kinda sucks. What's needed now is to…

> Docker Swarm was created basically to scratch that itch, but it still hasn't really taken off. I'm hopeful it does one day.

It never will, that ship sailed a long time ago. Docker the company is struggling to survive after making wrong bets multiple times. The "enterprise" part, including Swarm, was sold off to Mirantis after years of neglect, and got some much needed investment and big fixes. Nonetheless, Docker Swarm is basically abandonware with terrible reputation without a viable future.

Hashicorp's Nomad is much better placed to compete with Kubernetes. Shameless plug of my article on the matter:

https://atodorov.me/2021/02/27/why-you-should-take-a-look-at...

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#24
post #17
post #10

Earlier quoted context omitted.

I am eager to know how to game GitHub stars. Funding agencies love metrics and random KPI so I would love to deliver...

One word. Bangladesh.

That made me curious: never thought there was a real market but people really seem to pay 1$ per star. Now I have to only trick someone into giving me money for that.

Would be a fun project btw to detect gh not account and projects that obviously paid to get stars.

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#25

Earlier quoted context omitted.

Is getting listed in cncf landscape a big deal? Is it an official cncf project?

It is an official CNCF project, but its not very difficult to get added, see https://github.com/cncf/landscape#new-entries you need 300 github stars and to be cloud native.

Thanks for your response!

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#26

It would create more interesting conversation if you highlighted the merits of your design rather than superficial measures like CNCF blessings (there are thousands of such projects) and GitHub stars (easily gamed).

The description might not be good enough, but I have to write something. It's used by many companies and projects. And the design is described in github readme, it's rather long to tell here. Thanks!

Hi, are you involved with the project in a substantial capacity? If not, show hn isn't an appropriate qualifier. May be, tell hn (or, no qualifier) is.

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#28
post #23

Earlier quoted context omitted.

I think the architecture of something like K8s pretty well sums up all (or most) of the components needed for a distributed system. What's really needed today is differentiation on the actual end result of that design. We need simpler technology that works better, and that's hard; it's not enough to have a fancy idea and throw together some lines of code. That's been done, and it kinda sucks. What's needed now is to…

> Docker Swarm was created basically to scratch that itch, but it still hasn't really taken off. I'm hopeful it does one day. It never will, that ship sailed a long time ago. Docker the company is struggling to survive after making wrong bets multiple times. The "enterprise" part, including Swarm, was sold off to Mirantis after years of neglect, and got some much needed investment and big fixes. Nonetheless, Docker S…

Thanks for your article, the first pic made me and my colleague laugh really hard.

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#29
post #13
post #11

I love Go to bits, but I really don't like how so many tools revolve around codegen and boilerplate. Look at Kubernetes for example: you can't write an operator without generating a bunch of boilerplate.

I think it's because metaprogramming/macros is a thing Go doesn't have that very many other languages have. Whether the Java/.NET way, the LISP way or the Python way -- most languages have ways of making DSLs and metaprogramming etc in more flexible ways than Go. I wish Go just got something like Lisp macros that could work compile-time only. Running macros at run-time isn't really the big deal, but generating code i…

The irony is that Java and .NET already trailed that path 20 years ago.

Re: Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars

#30

I think this sort of project is in short supply. Kubernetes seems to have sucked all the air out of the room, and yet we need variety and different approaches to grow. I look forward to (trying) to replicate something similar for my own understanding. Any architecture docs will be gratefully recveied

I think the architecture of something like K8s pretty well sums up all (or most) of the components needed for a distributed system. What's really needed today is differentiation on the actual end result of that design. We need simpler technology that works better, and that's hard; it's not enough to have a fancy idea and throw together some lines of code. That's been done, and it kinda sucks. What's needed now is to…

I agree with you. Great comment. I just want to write some code that can scale from zero to infinity. Cluster or deployment Autoscaling in Kubernetes is not exactly what I want.

Kubernetes gets some abstractions right - such as pods, statefulsets, ingress, deployments

What we now need is abstraction of endpoints, routes, request, response type/schema (to do automatic marshalling), id space sharding like vitess or logical server identifiers as part of the guid for what server the data belongs to..microservice becomes a bucket of routes/rpc calls not hardcoded to a microservice.

Envoy, linkerd and hystrix look like a nightmare to configure right. I think the configuration behind them could be more elegant. The software is probably fine but it's a nightmare to get the right data structure that does what you want - hence the mountains of YAML configuration like you mentioned.

I don't want to care if it's the storage layer or the application layer - it should all be scalable.

I want to be able to set a maximum budget in financial terms and open ended autoscaling ceilling.

Post reply on HN