161–170 of 408 posts
Earlier quoted context omitted.
What happened is the realisation that FOSS developers also have to pay their bills and idealism only takes so far. So anyone that refuses to pay for their tools will eventually either loose them, or contend to be happy to use lesser ones.
“Loose” is the opposite of “tight,” “lose” is the opposite of “find.” Easy to remember because the opposites have the same number of letters.
Earlier quoted context omitted.
Throwing out a question to the room: if the worst happens and Nginx gets butchered, would it be so bad to go back to using Apache? I've never used it really, everything I've done has been Nginx, but is there some technical reason why Apache wouldn't be a fine fallback option for an open-source server?
Apache takes a few ms more for ssl termination. It's generally something around 20-50ms extra last time I did some benchmarks
I've recently been getting quite a few marketing emails from nginx pushing for replacing F5 with nginx. Just checked and the last one I received was last thursday, March 7th. Interesting how recently nginx was continuing this campaign. I wonder how effective the "replace F5 with NGINX" marketing push was at increasing the price and urgency for the acquisition. For the curious, the big headline at the top of the messa…
Earlier quoted context omitted.
According to the public statements, F5 is committing to maintain the current level of resources NGINX has allocated to their open source programs, to keep the same dev team involved, to keep licensing as it currently is, not change any of the repositories on Mercurial and GitHub and to keep the NGINX brand. Which only means that NGINX will get even better over time.
Hopefully if it declines we can have a MariaDB type fork take it's place.
But yeah, hopefully the community around it is solid enough to make that a possibility. I'd really prefer to not go back to Apache...
Earlier quoted context omitted.
Hopefully if it declines we can have a MariaDB type fork take it's place.
nginy? But yeah, hopefully the community around it is solid enough to make that a possibility. I'd really prefer to not go back to Apache...
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…
According to the public statements, F5 is committing to maintain the current level of resources NGINX has allocated to their open source programs, to keep the same dev team involved, to keep licensing as it currently is, not change any of the repositories on Mercurial and GitHub and to keep the NGINX brand. Which only means that NGINX will get even better over time.
Earlier quoted context omitted.
It used to actually a BSD rig with a CLI/admin interface on top.
The control plane can be a raspberry pi. Its what allows you to modify the rules how you route. Its the interface. The data plane is where you have high speed logic and data traveling. That's where you do the multiple 100GBps software defined networking, and its crazy fast chips doing it. And the control plane has interconnects to program the data plane chips to the rules you want. So the data never hits the control…
We were getting slammed on duty for the product and we were looking at ways of getting the appliances built locally using licensed F5 software, as the software itself wasn't as heavily taxed as the physical hardware. Everything in it seemed fairly commodity, except for the big F5 logo on the front.
It was an appliance that worked fantastically well. One deployment had an uptime of over ten years.
So...what is the future of enterprise open source? Is there a future for enterprise open source? If you start a company and open source your core/clients, your product becomes part of AWS, and AWS runs you into the ground. If you mix in proprietary licenses to protect yourself, AWS forks your core, adds in open-source licensed clients, then runs you into the ground (and you lose open-source contributors/supporters as…