Live data from Hacker News

Nginx to Be Acquired by F5 Networks

nginx.com

331–340 of 408 posts

Re: Nginx to Be Acquired by F5 Networks

#331

Earlier quoted context omitted.

I have always wondered what this enterprise support means? So if a big company starts using vagrant, they would dole out 100k for a support contract? I find this hard to believe but what do I know.

My enterprise company wont even get us Postman Premium to the tune of ~$150 per seat per year... So here we are slacking postman collections back and forth on our current year mac books.

Did you consider to create testing app to simulate customer experience? I can be a single html+js file in a git, for each major feature

Re: Nginx to Be Acquired by F5 Networks

#332
post #49

I guess that signals it's time for nginx users to check out possible alternatives - just in case, if things turn out for the worse. I can recommend having a look at https://varnish-cache.org/ - while its performance might not be 100% up to par with nginx in some (very, very high-end) scenarios, it has many other fortes that nginx (at least in its FOSS release version; I've never used nginx plus) just cannot match in…

Then again most nginx users are going to be fine with haproxy/traefik in front of good old apache or lighttpd. Or even just apache.

I've replaced most of my nginx instances with traefik, except those just serving static files. The configuration is more straightforward and the EncryptIt integration is a lot more elegant than in nginx's case.

Re: Nginx to Be Acquired by F5 Networks

#333

Earlier quoted context omitted.

There absolutely is a future for enterprise open source. It's not through direct monetization, but rather driving down the price of complements for existing product lines. Running a service on AWS requires two goods. High-margin computing resources that Amazon really wants to sell, and the software to turn those computing resources into solutions to business problems. Solving the business problems has a fixed dollar…

Amazon figured this out and surrounded their high-margin computing resources with a dizzying array of free-as-in-beer tools. But they also figured out that making their free-as-in-beer tools also free-as-in-freedom open source, they'd lift all clouds and not just their own. As the dominant player, Amazon loses from anything that reduces vendor lock-in. That's why precious little of Amazon's cloud tooling is released…

This! Kubernetes in some ways was a shot in AWS’s direction. It gives companies a reason to switch to Google. GKE is still far more stable and mature than EKS.

AWS still beats gcp in most other ways though (imho), so it’s far from a slam dunk. But it has opened up a door for Google.

Re: Nginx to Be Acquired by F5 Networks

#334

Earlier quoted context omitted.

You could AGPL and sell proprietary exceptions. Amazon won't touch AGPL code.

Others are happy to provide AGPLv3 code as SaaS, look at MongoDB's issues. You can build a ton of tooling around said code to enhance performance, adding features and billing, all while not modifying the core AGPLv3 code and thus avoiding the need to contribute back. This is a scummy business practice, but technically legal.

Why is it a scummy business practice?

Re: Nginx to Be Acquired by F5 Networks

#335

Earlier quoted context omitted.

> it throws out all of the interesting parts of Borg This is not true. It throws out the Google-specific parts of Borg (like integration with Google's service discovery, load balancing, and monitoring systems) and improves a number of things compared to Borg. For a good reference on the evolution of Borg into Kubernetes, I recommend the recent Kubernetes Podcast interview with Brian Grant: https://kubernetespodcast.c…

Unfortunately we can't discuss the parts of Google's platform that aren't in Kubernetes on this forum. If we could, I think I could defend my statement reasonably well. But perhaps you just don't think that the pieces I would mention qualify as interesting.

go/-link or it didn't happen.

Re: Nginx to Be Acquired by F5 Networks

#336
post #235

Earlier quoted context omitted.

But K8s is not a development of Google software. It is developed specifically for the public, it throws out all of the interesting parts of Borg, and Google themselves don't use it, or barely do. As for that other stuff it seems to have worked out fine for Google: they describe obsolete technologies and the outside world develops hideous analogs of those and uses them for decades. Hadoop for example is just an unbeli…

Implementation matters to google, more than to say the average company that uses Hadoop. At "Google-scale" small imperfections become huge imperfections. What's good for the bottom 90% of tech companies probably isn't for the top 10%.

I am a consultant working on Hadoop installations across the globe. As an average I usually able to save 70% disk usage and 30% overall cost by changing the defaults to a reasonable value as well as migrating companies out of HDFS to something like S3. I have spent majority of my career (10 years) working on Hadoop and I can tell you that it is a terrible piece of software with insane ineffciency all over the place. If you would switch over all the Hadoop installations on Earth at once to something more reasonable it would be visible on the global CO2 production chart quite a bit. What is good for the bottom 90% of companies is a financial question not a technological question. It is a bit unfurtunate that Hadoop is so popular and nobody cares about efficiency, not even the Hadoop vendors (maybe with the exception of MapR, which is not opensource).

Re: Nginx to Be Acquired by F5 Networks

#337
post #49

I guess that signals it's time for nginx users to check out possible alternatives - just in case, if things turn out for the worse. I can recommend having a look at https://varnish-cache.org/ - while its performance might not be 100% up to par with nginx in some (very, very high-end) scenarios, it has many other fortes that nginx (at least in its FOSS release version; I've never used nginx plus) just cannot match in…

The replacement should be written in a memory-safe language. Including the TLS library. "There is more to life than increasing its speed."

> The replacement should be written in a memory-safe language. Including the TLS library.

No. Memory safety is a vanishingly small subset of all bugs and security problems. PHP is memory-safe, for example. Where has that gotten us?

> "There is more to life than increasing its speed."

Not if you're a computer.

Re: Nginx to Be Acquired by F5 Networks

#338
post #148

Earlier quoted context omitted.

Thanks. As the industry [0] continues to put its weight behind NFV [1] and SDNs [2] along with the rise of IDNs [3], do you see network-appliances keeping up the share of the market against those solutions? I believe @Edge network might continue to require these appliances for WAF, Firewall/DPI (and other things I don't know about)... but that'd be a niche? [0] http://opennetworking.org/ [1] https://www.opnfv.org/ [2…

Not gonna lie, that question is almost not something i'm qualified to answer, since I was more focused on specific ssl technologies/integrations, but I'll have a go. Obviously they won't go away, but network appliances definitely won't keep their share because not everyone needs them as SDNs get better. I see the SDN and IDN as mostly solving multivendor integration issues and making it easier to configure at least s…

Thanks a lot!

Re: Nginx to Be Acquired by F5 Networks

#339
post #245

Earlier quoted context omitted.

But K8s is not a development of Google software. It is developed specifically for the public, it throws out all of the interesting parts of Borg, and Google themselves don't use it, or barely do. As for that other stuff it seems to have worked out fine for Google: they describe obsolete technologies and the outside world develops hideous analogs of those and uses them for decades. Hadoop for example is just an unbeli…

Can you mention some of the interesting parts of Borg that are missing in k8s?

among other things, I miss Autopilot and generally the extensive machinery to help with massive capacity planning.

Think of Autopilot as an automation that tweaks a pod's request/limits according to what it actually needs in order to reduce waste and thus improve cluster utilization.

(I _think_ this no longer qualifies as secret after https://github.com/kubernetes/kubernetes/issues/44095)

That said, k8s is quite extensible and it would definitely be possible to add such a component as a controller.

Re: Nginx to Be Acquired by F5 Networks

#340
post #245

Earlier quoted context omitted.

Can you mention some of the interesting parts of Borg that are missing in k8s?

among other things, I miss Autopilot and generally the extensive machinery to help with massive capacity planning. Think of Autopilot as an automation that tweaks a pod's request/limits according to what it actually needs in order to reduce waste and thus improve cluster utilization. (I _think_ this no longer qualifies as secret after https://github.com/kubernetes/kubernetes/issues/44095 ) That said, k8s is quite ext…

Autopilot is coming as VPA: https://stupefied-goodall-e282f7.netlify.com/contributors/de...
Post reply on HN