When it comes to application responsiveness and performance, the stakes have never been higher. Google, Facebook, and countless other digital brands have set the expectation for every company they interact with. Customers expect instantly available, highly personalized digital experiences and have zero tolerance for companies that can’t meet their demands. Your apps are the face of your business, and you must deliver them to your customers’ delight.

In this keynote by Gus Robertson, you will learn more about the critical importance and impact that application delivery has on your business, how tools and techniques have evolved to meet user expectations, and what NGINX does to help you outpace the competition and move from failures to flawless.

In this keynote by our Head of Products, Owen Garrett, you’ll hear about the latest and greatest from NGINX; including a recap of recent product releases, some exciting new features in both our commercial and open source tools, and where we plan to evolve our products in coming months.

If you didn’t fail with microservices at least once you didn’t really try anything new! Even though microservices are an established architectural style in the industry, they still come with their own challenges.

This session focuses on a topic that is usually overlooked in the early stages of building a microservices architecture: traffic management. It comes into the picture after we fail an SLA, whether the cause is a misbehaving client, a legitimate increase of traffic, or a DDoS attack. We then start asking questions like how to ensure a fair usage policy for clients across microservices, how to protect clients from an abusive peer that is generating a spike in traffic, and how to protect microservices themselves from abusive clients.

NGINX comes with options for rate limiting that usually work great for a single node. Extending NGINX's capabilities to distributed environments increases the complexity of the solution. Can rate limiting be applied transparently without visible impact on latency? Is it easy to scale? Is it reliable? In this session, I'll introduce you to an open source solution contributed by Adobe I/O and used with success in real-life scenarios. The solution is based on an asynchronous communication model that supports high-throughput scenarios with minimum impact on latency. If you've had similar problems in the past or if you're concerned about how clients interact with your microservices then this session is for you.

A high-performance site doesn't necessarily need every query optimized and every asset compressed and minimized. With this one weird tip, you'll learn to quickly deal with the Thundering Herd problem and avoid the consternation that comes when you first have to deal with tens of thousands of hits per second (millions of hits per day).

In this session I'll explain how to configure NGINX as a page cache that uses stale content to avoid many of the problems that arise when first having to deal with high traffic. Additionally I'll cover how to design your site for scalability from the ground up. You'll learn simple scalable application design, the importance of utilizing a stale cache, and how to use NGINX plus CDNs to front web sites and services.

In this session I'll dive into the features of the NGINX TCP/UDP load balancer. The Stream module has received a lot of attention from developers since its introduction in NGINX 1.9.0 in April 2015, becoming a mature and well-proven addition to the NGINX load-balancing stack.

I'll give an overview of the supported load-balancing methods, SSL/TLS support, and additional features provided by NGINX Plus such as proactive application health checks and on-the-fly reconfiguration. I'll cover the typical use cases for TCP and UDP load balancing, and will also share a few tricks using nginScript, the JavaScript-based scripting language for NGINX.

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.

There's a lot of hype surrounding HTTP/2, which sometimes makes it hard to sift out the ashes from the cinders. In contrast to a large number of marketing-driven articles, this session will reveal the bad sides of HTTP/2. I'll discuss not only benefits, but also disadvantages, of the new protocol so you will better understand why it can't replace HTTP/1.x everywhere. This knowledge is extremely important to making the right choice for your particular use case.

Star Trek’s Borg were a collective community known for their extreme resilience: they had no single point of failure, with each member having extreme independence. Killing some Borg didn’t measurably impact their overall capabilities or performance, and destroying some of their infrastructure didn’t stop their entire ship.

There’s a lot we can learn from the Borg and apply as we build applications with ever-increasing numbers of Docker-based microservices. I’ve been working with some of the earliest adopters of large-scale microservices architectures, and in this session I'll share how they’ve been able to create the same levels of fierce resistance to failure that everyone’s favorite Star Trek villains have.

Star Wars fans are welcome.

Modern day apps rely on ability to deliver smaller components of services and rapidly deploy, scale and service at will. This brings in the challenges of coordination, SSL Termination, socket connection support etc. Looking at different cloud providers and orchestration tools , features supporting Socket connections, SSL Termination and geo distributed load balancing are missing. Leveraging capabilities of NGINX (NGINX Plus), several problems discussed above can be solved. This presentation gives an overview of of Use Case study of leveraging capabilities of NGINX to solve problems arising from microservice, reactive services.

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.

More and more companies are solving their distributed delivery problems by building their own CDNs. While this might sound daunting, the principle of a CDN is quite simple: direct clients to the closest server able to provide the resource they want. That said, the devil is in the details. In this session I'll explain how we built a CDN at Time Warner Cable, what our considerations and goals were, and how we customized the CDN to deliver ABR video.

Those who fail to learn from history are doomed to repeat it. When things go wrong, and our services are impacted, we need to tell the story of our failures so that we can grow and learn as team. Postmortems offer us an opportunity to share this knowledge, so that we can build on our successes and avoid repeating our mistakes in the future. In this session we will discuss how Datadog runs our internal postmortems from data collection to building timelines to the blameless review. Attendees will leave with a framework they can apply right away to make postmortems more impactful in their own organizations.

In this session I'll cover various aspects of dynamic modules, which were introduced in NGINX 1.9.11 and NGINX Plus R9, including design goals, implementation details, and corner cases. I'll also explain how to convert your own modules so they can be loaded dynamically.

Software developers have been looking at different ways of building software and different architectural patterns have emerged. In this sort of revolution, Microservices and APIs have increasingly assumed greater importance as both a technology and a design pattern. While improving certain aspects of monolitich software, Microservices also add additional complexity that has inspired the creation of new design patterns, one of them being the usage of API Gateways. This talk highlights the challenges of microservice-oriented architectures, exploring the role of API Gateways and illustrating real-world use cases of their application.

Key Takeaways

• Kong + NGINX provide API Management at unprecedented scale
• Treating your APIs as their own products
• NGINX as the platform for innovation for open-source projects
• The API Gateway pattern
• Microservice orchestration

A typical microservices architecture has five tiers:

• You need a web proxy like NGINX to handle slow clients and to serve static files
• You need an application web server like Apache or Django to run your application logic
• You need a caching layer like Memcached or Redis to cache frequently accessed data
• You need a database proxy to handle sharding and replication, abstracting that stuff away from the application
• You need a database management system to store your data

Five tiers – isn't it too many? Yeah, that's what we think too. So we've come up with an idea to shrink the whole bunch of tiers down to just a couple. The web proxy and database proxy are combined into one tier, now just a proxy. The application server, the cache, and the DBMS are packed into the other tier. Fewer tiers mean less problems and more bonuses like data consistency and better performance. In this session, I'll explain how to do this magic and how it works under the hood.

Your NGINX instance is the perfect location to add a Web Application Security layer. Each update you make to your application can introduce vulnerabilities that are ideal for attack and exploitation. NGINX-based reverse proxy servers and load balancers can be the last barrier between an attacker and vulnerable applications.

By examining the headers and body of requests, as well as how the application responds, it is possible to identify and filter illegitimate traffic. NGINX instances already have traffic to analyze – now, learn how to use it to make your applications and APIs more secure!

In this session I'll explore:

• How to mitigate attacks that target vulnerabilities of your application (OWASP Top10)
• How to stop bots from crawling your website
• How to deal with application-layer (Layer 7) DDoS attacks

This session is a detailed look at what Expedia has learned from using NGINX to ease the migration of applications to the cloud. Specifically, I'll examine how to avoid "knife-edge" cutovers by building resiliency into your migration strategy and adding a fail-safe for migrated applications during the cutover. I'll share:

• Design patterns and code that show how to migrate traffic without a knife-edge cutover
• How to use health checks across regions to make your migration more resilient
• How to use the NGINX error handler to build fail-safe mechanisims

Nobody wants to get to a WTF moment, particularly when it comes to a production cloud applications or SaaS environments. Simple poll-check alerts can’t relate to overall system performance. Log monitors can’t give a complete understanding of a system running cloud applications. APM can’t track custom application metrics that are the true indicators of business performance and customer experience. WTF - is there a better way?

This talk will cover how a unified metrics-driven approach to monitoring combined with real-time analytics forms the core of modern service assurance architectures. The talk will also cover how to apply query analytics to improve anomaly detection and intelligent alerting at production scale, with examples from the operational trenches of leading SaaS companies.

Nchan is a scalable, flexible pub/sub server for the modern web, built as a module for the NGINX web server and supporting WebSocket, EventSource, long polling, and other types of subscribers. It can be configured as a stand-alone server, or as a shim between your application and tens, thousands, or millions of live subscribers. It can buffer messages in memory, on disk, or via Redis. All connections are handled asynchronously and distributed among any number of worker processes. It can also scale to many NGINX server instances with Redis.

In this session I'll focus on use cases and the architecture of Nchan.

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.

Since NGINX is one of the most critical elements of an app infrastructure, it's important to have good visibility into the behavior of the servers running it. It is equally important to make sure the configuration elements are all aligned to avoid pitfalls with your NGINX setup. NGINX Amplify brings the required visibility and control to your system architecture built on top of NGINX.

Being the fastest web server on Earth, NGINX is often used as a component that is run in virtualized environments (virtual machines or containers).

Being the leading virtualization platform provider on the hosting market, Vrtuozzo cares about performance and the density of services running on hosting infrastructure.

In this session I'll share our experience and measurements of running web services, especially NGINX, inside Virtuozzo containers. I will show what technologies are used in the Virtuozzo Containers product and how they enable hosting providers to offer their users higher density and higher performance of their services than other virtual solutions such as KVM or VMware.

This session will illustrate how to accelerate and secure your web and mobile applications using NGINX running on Amazon Web Services. You'll learn several deployment models and design opportunities using NGINX along with popular AWS Services such as Amazon EC2, Amazon Route53, Amazon CloudFront, Amazon Relational Database Service, and Amazon Certificate Manager. The example deployments in this session will also showcase geographic and latency-based routing capabilities along with multi-regional data transit and replication constructs.

In this session, I'll discuss the advanced techniques available in NGINX for URL manipulation and content generation. I'll cover using rewrite and location rules, the differences between internal and external redirects (and HTTP status codes), using and blocking cookies with upstream servers, and actual web-page generation – all within NGINX, without necessarily using any resources external to the configuration file itself.

I base the material on my experience running semantic URL services like mdoc.su and bxr.su, as well as on-the-fly modification of the behavior of applications like the Java-based OpenGrok with the help of nginx.conf.

The Tokenization microservice at Thales e-Security is implemented in C as a statically linked NGINX module. It uses shared memory for interprocess communication and reads configuration data from a PostgreSQL database, which is then retained in several caches for performance reasons. The Tokenization microservice parses JSON requests, cryptographically tokenizes a credit card number (or any other data one may want to tokenize), and returns the token as a JSON response, at a rate of more than 1 million tokenization operations per second. While the Tokenization Server scales almost linearly with the number of CPU cores, up to 48 physical servers can be combined into a cluster for a theoretical performance of more than 50 million operations per second.

NGINX makes HTTP caching really easy and extremely efficient. Underneath any caching system is an extremely hard problem lurking in the dark – cache invalidation.

While this session does not solve the cache invalidation problem itself – it is one of the two hard problems in computer science, after all) – it highlights the options available for invalidating items in the NGINX cache and introduces a new system of smart invalidation–invalidating groups of associated items based on tags.

Microservice Applications bring many powerful benefits – scalability, component isolation, and a much simpler platform for feature updates and additions. In many respects, these benefits are enabled by splitting the functional components of an application apart into separate services and using the network as the mechanism for interprocess communication. While this fundamental change in application architecture has many benefits, it also has some inherent problems: it is difficult to link components together, make them secure and make them fast. This presentation discusses a series of architectures that address these problems using NGINX Plus for network management in your microservices applications.

Speed and productivity are musts in today's complex technology environments. NGINX and IBM are partnering to bring you the tools you need to move from development to deployment and to scale to the large, larger, and largest volume of users. NGINX and IBM Websphere Liberty and IBM Power Systems bring new and improved advancements to web application development and delivery for the agile enterprise.

Join us Thursday morning for a series of short 10-minute talks!

• Building a Loosely Coupled API Gateway with NGINX, Gopal Raghavan, HERE Inc.
• SEO Improvements Using NGINX, Eugenia Timasheva
• Building Mintigo for Scale with NGINX, Tal Segalov
• Creating Dynamic NGINX Modules, Tejas Gopalakrishna
• Users and Their XY Problems, Francis Daly

The next generation HTTP protocol has arrived. Learn what it can do for you, and how to bring support for it in NGINX. Find out how it interoperates with older protocols, and offers new features while preserving legacy compatibility.

Since release 1.12, Docker, with the integration of Docker Engine and Docker Swarm, Swarm Mode supports multi-host container orchestration, which simplifies deployment and management of containers across a cluster of Docker hosts. Load balancing is an essential part of any reliable high-performance web application. In this talk we will give an overview of the basic built-in load balancing options available in Docker Swarm Mode and discuss how to integrate NGINX and NGINX Plus with Docker Swarm Mode to provide an advanced load balancing solution for a Swarm cluster. We will show how to utilize the dynamic reconfiguration options available with NGINX Plus to make integration simpler.

One of the greatest challenges to developing an API is ensuring that it lasts. After all, you don’t want to have to release and manage multiple versions of your API just because you weren’t expecting users to use it a certain way, or didn’t think ahead far enough down the roadmap. In this session I’ll talk about the challenge of API longevity, as well as ways to increase your API lifecycle, including the proper mindset, careful design, agile user experience and prototyping, best design practices including hypermedia, and the challenge of maintaining persistence.

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.

It's not news that A|B testing is crucial for driving continuous improvement of your product. But it can be difficult to design a test infrastructure that properly exercises technically complex products and sites. In this session I'll explain how to build a simple and configurable frontend infrastructure on NGINX for A|B testing complex, high-traffic sites. I won't be discussing how to map/reduce data or how to visualize it.

Modern applications are moving away from the traditional request/response loop to more event-driven patterns. The concept of “serverless” computing is floating around in discussions of microservices and modern architectural design patterns. But what is "serverless", and how is it different from microservices – if it actually is?

We’re entering a world where developers won’t have to think about provisioning resources to run their code. While serverless computing sounds like nirvana, there’s an upfront investment in changing development and operational patterns to allow for such a level of automated orchestration. Meanwhile, innovative teams have embraced the use of microservices as a direct response to the costly and cumbersome monolithic methodologies of the past, but new questions have arisen around use cases, planning, and best practices for implementation.

In this session, I'll explain why now is the dawn of the serverless age. I'll also discuss best practices and tools that are available to address the challenges of service-driven architectures head-on while deploying in a serverless environment.

In the last few years, application security has been forced to reinvent itself due to the advent of cloud, containerization, agile, DevOps, and other modern development technology and process improvements. The old ways of doing application security are phasing out with the new approach being embedded into the fabric of how we build software. However, sometimes with innovation comes confusion.

In this session we will talk about the different types of modern web application security approaches, which types are good for what use cases, and how you should consider changing your approach to web application security to better fit today’s modern development world.

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.

In this session, I'll explore how to use Chef to orchestrate autoscaling with NGINX Plus across multiple cloud providers utilizing the knife-cloud plug-in. There are many ways to handle autoscaling in cloud environments, but most are targeted to single providers. In this talk I will show how you can utilize Chef tools to build an autoscaling solution with NGINX Plus that does not depend on a single cloud provider.

TLS (Transport Layer Security) is the backbone protocol for Internet security today, providing the foundation for expanding security everywhere in the network. Security is an element of networking infrastructure that must not be underemphasized or taken for granted. While critical to the foundation of networking, adding security into existing infrastructures generally comes with a trade-off between cost and performance. Utilizing NGINX's efficient connection-level scheduling capabilities in conjunction with Intel® QuickAssist Technology and the new asynchronous features added to OpenSSL 1.1.0, networking performance can be unleashed without experiencing the bounds of adding end-to-end cryptography. In this session I'll focus on several of the new features introduced in OpenSSL 1.1.0 and the significant performance gains that can be achieved when integrating with NGINX and taking advantage of Intel® QuickAssist Technology. I'll show that efficiency and application-level performance gains via Intel® QuickAssist Technology can be achieved with a low cost of adoption.

NGINX offers a number of streaming features through the RTMP module and NGINX Plus has additional modules. The RTMP module delivers streams over the RTMP protocol and can dynamically convert RTMP into HLS and MPEG-DASH in real time. NGINX Plus can stream HLS and HDS from .mp4 and .f4f files. However, a few missing features have kept streaming service providers from building their service on NGINX. For example, NGINX Plus can transmux to HLS and HDS but not VOD content to DASH. Also, in serving HLS segments NGINX Plus relies on URL query strings that include start= and end=, which makes the streams hard to scale to a larger audience through a CDN cache.

In this session, I'll show how to build a streaming server using open source NGINX with FFmpeg and GPAC's MP4Box, which can dynamically transmux .mp4 files to HLS and DASH. A FastCGI script and FFmpeg can dynamically generate a manifest file, and a FastCGI script with FFmpeg/GPAC can dynamically cut .mp4 files into smaller segments and repackage them for HLS and DASH upon request.

In the 20 years since the introduction of SSL by Netscape, the overall use of HTTPS on the Internet has remained depressingly low. In late 2015, a free certificate authority named Let's Encrypt opened, making free digital certificates easily avaiable for the first time.

In this session you'll learn all about Let's Encrypt and how it has changed the sad story of poor HTTPS adoption in just a single year! I'll also demonstrate how to install a digital certificate on NGINX with Let's Encrypt and test it with Qualys's SSL Labs.

Did you ever wonder what happens when you try to access Photoshop’s Stock library or how images are being processed on your mobile phone? For the past few years Adobe has been leveraging the cloud to provide an increasing number of functionalities as a services to developers. NGINX is a core component in this process, proxying, monitoring and tracking hundred of million of requests a day, and has helped us not only to offer the best performance in terms of latency and stability but also to answer some deep questions that come naturally when dealing with data at scale:

• How can we investigate issues that may occur in the request/response interaction by logging the API error logs?
• How can we detect anomalies and notify service providers by applying machine learning algorithms to the incoming traffic?
• How can we provide interactive analytics for both service consumers and providers?

Processing and storing high volumes of data is providing powerful insights into the way applications interact with microservices, and In this session I'll demo some of the work done around this topic.

IBM has partnered with NGINX to improve performance, scalability and resiliency of Web applications. Come hear why POWER8 is a better platform for running Web applications leveraging NGINX. A technical overview of the key Power Systems performance and RAS features will be presented. Two solution areas IBM is exploiting NGINX will be discussed:

• LAMP
• Java Docker Deployment

LAMP stacks are ubiquitous in the online environment. IBM has teamed up with key partners – Canonical, ZEND, MariaDB, Mellanox – and now it’s newest family member – NGINX - to build a Turbo LAMP stack. This presentation will present the latest findings regarding the integration of NGNIX into the Turbo LAMP stack running on POWER8 as well as how it was tested with the Magento Performance Benchmark Kit.

We will then talk about how we built and set-up a Docker deployment combining a Java EE runtime and NGINX to provide a scalable solution with dynamic routing, where we can quickly and easily scale the deployment up and down to meet varying demand.

In a microservices application, the set of running service instances change dynamically and their assigned network locations keep changing as well. Consequently, in order to load balance requests across the most recent set of service instances, a load balancer like NGINX must use a service-discovery mechanism.

In this session, I'll demonstrate how NGINX and NGINX Plus can load balance HTTP traffic in a Docker-based environment to an arbitrary number of backend servers that are registered with Consul, a popular open source service discovery tool. With open source NGINX, you can use tools like Consul Template, which listens for changes to the service catalog in Consul and then reconfigures and reloads NGINX automatically.

NGINX, Inc.'s commercial offering, NGINX Plus, further improves service discovery integration by enabling you to dynamically add or remove servers in a load-balanced group as they are discovered via Consul, using either NGINX Plus' HTTP-based API or by re-resolving DNS records through Consul's DNS interface. This also eliminates the need to reload the NGINX Plus configuration everytime there is a change the set of load-balanced servers.

NGINX is not just a great web server – it can be so much more. It can be an integral part of your web stack. It can help you solve problems that may otherwise be intractable. With NGINX, Aggrego was able to turn a project around from a colossal failure io a very high-performance platform.

With some creative configuration we decreased response time to 90 milliseconds even when the backend stack took 60 seconds – and not just by caching things for a set amount of time. We amped up the built-in caching mechanism to accurately maintain cache coherency in real time by leveraging:

• NGINX caching
• Lua
• NGINX Memcache module / protocol
• Graph database
• Server Side Includes (SSI)

In this session you'll learn how to leverage NGINX to solve catastrophic problems. NGINX is a great web server – no doubts about that. But it can be so much more.

In this session, I'll discuss NGINX CI and CD pipelines for dynamic modules, covering the following topics:

• What the previous way to build and deploy looked like, with only static modules
• How the NGINX In Place Upgrade works and how to go about automating it
• How you can change your build pipelines to support a build that makes use of dynamic modules
• How a dynamic module works
• What different workflows for this might look like
• How you can add in tests for these modules
• Deployment strategy in regards to the addition of dynamic modules

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.

Your website is running on servers that are either in-house or colocated in a data center. You run them yourself, you have a top-notch IT team, and you are in control.

Now you're under pressure to go to the cloud for cost savings and/or strategic reasons. But the prospect of going "serverless" is scary. There is ample room for "unfortunate decisions".

If this sounds familiar to you, join me at this session. I'll show you:

• How to think about your current infrastructure in "cloud terms" and plan a transition
• How to identify your core assets and make sure they do not get lost in the cloud
• How to leverage your existing IT team's skills
• How to use NGINX to keep your infrastructure under control

This session will be a mix of high-level concepts and clear, down-to-earth examples.

In this talk we’ll show you how to use NGINX and NGINX Plus as an external load balancer for Kubernetes services. We’ll start with a brief explanation of the various load balancing options available in Kubernetes and then focus on the Ingress API, which lets you configure external HTTP(S) load balancing. We’ll see how NGINX and NGINX Plus can be integrated with this API using an Ingress Controller that we’ve developed. You’ll learn how to deploy and configure the NGINX Ingress controller for several use cases:

• Content-based HTTP load balancing
• SSL termination
• WebSocket
• Session persistence and more.

We'll also cover monitoring and collecting logs from NGINX and NGINX Plus when running in Kubernetes. We’ll show how to extend the controller when your requirements go beyond what it offers. We’ll conclude the talk by explaining how to use NGINX and NGINX Plus to load balance TCP/UDP services.

NGINX allows you a great deal of freedom when it comes to developing custom modules. You can hook your own code in different phases of the request life cycle, use chains to capture any data that is passed to your server, and control how access management or logging is done.

In the access management solution at ING Bank N.V., we are moving to use of tokens to control access to the restricted area of our different channels. Tokens will be validated by a separate TokenAPI and stored within NGINX. To make sure availability is increased, authentication state and customer state are distributed via Cassandra to different nodes, even across data centers. The solution will support access tokens but also refresh tokens to allow third-party access as well, even if they are hosted in third-party data centers.

In my talk I'll show how our modules work together and how we add Cassandra persistency to ensure the asynchronous nature is preserved.

Sometimes a business model is so complex that building it in a “traditional” way just won’t cut it. We’re introducing a radical way for you to speak business-level languages, while letting the machine do the intensive coding and optimizations automatically.

Today many developers use NGINX with Lua or OpenResty to build scalable and dynamic online products – whether they’re creating web gateways, web service and ad platforms, or even complete web applications. This works well but we’ve come up with a new way to do it, cutting your business code base and boosting performance to a whole new level for free. Now developers can convey complicated business requirements to machines in the most natural way for humans. For the first time, machines can understand high-level business concepts and rules, and choose the best implementation strategy on their own, optimizing the business systems as a whole.

In this session I'll introduce interesting domain-specific languages designed for various real-world business models. These languages are fun to code in, and also have smart compilers that emit fast and compact Lua code targeting the NGINX or OpenResty environment. Even better, they’ll be ready to deliver over a large network and take effect on the fly.

The cloud has transformed the way we build applications. Early adopters prove that the benefits manifest in delivering value faster to the customer, less operational costs and more productive teams. The interesting question is how to get there, especially if you cannot simply start over and get your current applications benched. Through numerous customer engagements we have learned that there is a pattern followed by companies that do this successfully:

• How to deploy faster without breaking things
• Start decoupling a monolith without breaking your business logic
• Help developers build application using a new paradigm
• Dynamically scale your applications to save costs
• Manage highly dynamic larger-scale micro services without increasing operational costs

As we walk through the journey we share learning covering challenges and possible solutions on the organizational, development and operational side. As a company that has gone through this transformation itself while on-boarding over 500 new customers we have some interesting stories to share.

Many modern applications consist mostly of dynamic content and write-heavy workloads. These applications are typically difficult to accelerate with standard HTTP caching and often developers resort to overprovisioning to survive variable traffic.

To handle some of the world's largest flash sales at up to 5x our baseline throughput, Shopify has relied on NGINX’s performance and scripting API to implement protective features at a low cost. Although flash sales are unique to commerce platforms, the lessons we learn from them are applicable to any service that experiences bursts of traffic.

In this session I'll share our approach to building application-aware caching and rate-limiting into our NGINX load balancers and techniques for debugging them in production.

NGINX is a high-performance, open source web application accelerator that helps half of the world's busiest websites deliver more content, faster, to their users. In the hands-on NGINX Fundamentals course, you'll learn to install, configure, and maintain NGINX. Beyond the basics, you'll learn how to deploy NGINX for common use cases such as load balancing, reverse proxying, and caching. Going step-by-step through the installation and configuration process, you'll learn by doing and have a complete basic NGINX setup at the end. This course is hands-on, so bring your laptop and be ready to go to work. This course covers the core features common to open source NGINX and NGINX Plus.

Objectives

• Why NGINX and how it compares to the alternatives
• Installing NGINX
• Configuring NGINX
• Changing configuration, rotating log files, debugging logs, and upgrading on the fly
• Common backend interactions, processing requests, and working with server blocks
• Important features and use cases to know
• Course project

Audience System administrators who are new to NGINX but have a foundational understanding of web server setup and configuration.

Prerequisites We recommend that you have some experience using the command line and basic Unix commands, including but not limited to the following:

• sudo (and you understand what root access means)
• ssh
• wget
• vim (or your preferred text editor)
• mkdir
• cd
• ls

In addition, if you are using a machine with a Windows OS, it must have Putty installed, or a VMWare player with a Linux OS installed on it.

Join us Friday, September, 9 for "Microservice Network Architectures with NGINX Plus". In this one day hands-on training, you will explore the Proxy, Router Mesh, and Fabric network architecture models through the NGINX Microservices Reference Architecture. In hands-on labs, you will create an NGINX proxy to a microservices application. You’ll then do centralized load balancing in the Router Mesh model. Finally, you’ll do container-to-container load balancing using the Fabric Model.

Audience: This class is for experienced developers and NGINX admins who understand microservices architectures.

What: A one day, hands-on, team-based learning experience with NGINX’s Chris Stetson and professional services team. Participants will explore three microservice network architectures through in class lectures and hands-on activities.

You will:

• Learn how to deploy NGINX Plus as a HTTP gateway to their microservices application
• Deploy NGINX Plus to act as a centralized load-balancer for interprocess communication between their microservices
• Deploy NGINX Plus at the container level to create a fabric network of persistent SSL connections between their microservices
• Collaborate and connect with other participants
• Get your questions answered by experts from NGINX

Prerequisites/Requirements:

• Solid understanding of web server functionality
• Experience working with NGINX .conf files
• Working knowledge of NGINX proxy and load balancing capabilities
• Comfortable working on the command line in a UNIX environment
• Attendees should bring a wifi-enabled laptop to the class

The cloud has transformed the way we build applications. Early adopters prove that the benefits manifest in delivering value faster to the customer, less operational costs and more productive teams. The interesting question is how to get there, especially if you cannot simply start over and get your current applications benched. Through numerous customer engagements we have learned that there is a pattern followed by companies that do this successfully:

• How to deploy faster without breaking things
• Start decoupling a monolith without breaking your business logic
• Help developers build application using a new paradigm
• Dynamically scale your applications to save costs
• Manage highly dynamic larger-scale micro services without increasing operational costs

As we walk through the journey we will share learning covering challenges and possible solutions on the organizational, development and operational side. As a company that has gone through this transformation itself while on-boarding over 500 new customers we have some interesting stories to share.

NGINX Advanced builds on the topics covered in the NGINX Fundamentals course to help you address more complex application scenarios. To help you get more out of your NGINX installation, you will use configuration variables and content manipulation. You will utilize the more complex features of the core, proxy, and rewrite modules common to both NGINX and NGINX Plus. You'll learn how to optimize your web server using advanced location routing, load balancing, traffic control and dynamic reconfiguration, exposing you to some of the unique and powerful features of NGINX Plus. Finally you will learn how to monitor your NGINX instance using custom access logging and the live activity monitoring dashboard. With a deeper understanding of these capabilities, you'll become even more proficient at configuring and monitoring NGINX and NGINX Plus.

Objectives

• Learn the basics of how to set up NGINX Plus
• Understand key variables from core, proxy, and rewrite modules, map and set and content manipulation
• Use advanced location routing
• Load balancing
• Monitor your instance using custom access logging, the status page, and dynamic reconfiguration
• Security and traffic control

Audience Technologists who have installed and are using NGINX, but want to learn more advanced use cases for optimizing and monitoring their NGINX web server

Prerequisites This course assumes a foundational understanding of NGINX.

• Understanding of the NGINX configuration file structure
• Setting up a basic NGINX server to serve static content
• Basic load balancing and proxying
• Basic knowledge of a Linux based operating system and how to use the command line
• A Linux machine to participate on the exercises

We'll resume Microservice Network Architectures with NGINX Plus training post lunch.

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.

Ask the NGINX experts! Join us at the NGINX booth in the Community Hall to get all your NGINX questions answered.