No Image

NGINX and F5: Our Continued Commitment to Open Source

2019-03-20 KENNETH 0

NGINX and F5: Our Continued Commitment to Open Source Last week, we announced that F5 will be acquiring NGINX. The response has been overwhelmingly positive from customers, the community, partners, employees, and throughout the industry. It’s humbling and we thank everyone for their ongoing support of NGINX. But we also heard loud and clear: F5 and NGINX need to continue demonstrating our joint commitment to open source. Let me explain what we’re doing. I’d like to hear from you if we’re not meeting expectations. NGINX and F5 Are Committed to NGINX Open Source Let me take a moment to be very explicit: F5 is committed not only to supporting the development of NGINX Open Source and other NGINX open source projects, but to increasing investment over time. Just to repeat that. F5 is committed to the NGINX open source technology, [ more… ]

Do I Need a Service Mesh?

2019-03-14 KENNETH 0

Do I Need a Service Mesh? “Service mesh” is a red‑hot topic. It seems that every major container‑related conference last year included a “service mesh” track, and industry influencers everywhere are talking about the revolutionary benefits of this technology. However, as of early 2019, service mesh technology is still immature. Istio, the leading implementation, is not yet ready for general enterprise deployment and only a handful of successful in‑production deployments are running. Other service mesh implementations also exist, but are not getting the massive mindshare the industry pundits say that service mesh deserves. How do we reconcile this mismatch? On the one hand, we hear “you need a service mesh”, and on the other hand, organizations have been running applications successfully on container platforms for years without one. Getting Started with Kubernetes Service mesh is a milestone on your journey, [ more… ]

NGINX to Join F5: Proud to Finish One Chapter and Excited to Start the Next

2019-03-12 KENNETH 0

NGINX to Join F5: Proud to Finish One Chapter and Excited to Start the Next I’m incredibly excited that today we announced NGINX has signed a definitive agreement to be acquired by F5. While there will be a lot of press and formal announcements explaining the reasoning behind the decision, I wanted to share a few words of my own. We’ve built an incredible company, which led to today’s event. As I reflect on how we achieved this success, I landed on three key themes: technology, family, and vision. How We Got Here: Technology, Family, and Vision At the core of NGINX’s success is the amazing technology that Igor Sysoev wrote back in 2002. His decision to open source this technology literally changed the world. You may not see it that way, but the honest truth is that over my [ more… ]

Simplifying API Definition with the NGINX Controller API Management Module

2019-03-08 KENNETH 0

Simplifying API Definition with the NGINX Controller API Management Module API lifecycle management begins with planning, designing, and defining APIs. This blog spotlights how easy the NGINX Controller API Management Module makes it to define APIs and publish them to NGINX Plus API gateways. Many API management tools require you to create a separate definition of a given API for each different deployment environment. With the NGINX Controller API Management Module, you define an API just once and publish it to as many environments as you want. This “create once, publish many” approach eliminates user errors as well as saving time and effort, especially if you have to define a lot of APIs. The API Management Module provides a logical framework for defining APIs and the associated configuration. Let’s go through each logical entity. Defining the Entry Point The entry point for an [ more… ]

No Image

Introducing Internal Routing in NGINX Unit 1.8.0

2019-03-05 KENNETH 0

Introducing Internal Routing in NGINX Unit 1.8.0 h4 { font-weight:bolder; font-size:110%; } h5 { font-weight:bolder; font-size:110%; } Today we’re announcing NGINX Unit 1.8.0, with a different approach than in the past: this time it’s example first, description after: “routes”: { “blogs”: [ { “match”: { “uri”: [“/phpmyadmin/*”, “/wp-admin/*”] }, “action”: { “pass”: “applications/blogs-admin” } }, { “match”: { “host”: “!blog.example.com” }, “action”: { “pass”:”applications/goaway” } }, { “match”: { “method”: “POST”, “uri”: “/media/upload” }, “action”: { “pass”:”applications/uploader” } } ] } Now, the details. Internal Routing When we released the initial version of NGINX Unit, some of our users wondered why the API included a separate listener object – it perhaps wasn’t clear why it was necessary. In NGINX Unit 1.8.0, we’re introducing the internal routing feature that makes use of the listener object in a more sophisticated way and enables new [ more… ]