Log in
Forgot password ?
Become a member for free
Sign up
Sign up
New member
Sign up for FREE
New customer
Discover our services
Dynamic quotes 

MarketScreener Homepage  >  Equities  >  Nasdaq  >  F5 Networks, Inc.    FFIV


News SummaryMost relevantAll newsPress ReleasesOfficial PublicationsSector newsAnalyst Recommendations

Infrastructure Architecture: Containers Creating Fourth Plane

share with twitter share with LinkedIn share with facebook
share via e-mail
07/22/2019 | 10:05am EST

But there's another kind of orchestration at work that's under the hood and largely unseen by operators. It has nothing to do with management except that it's appropriating some responsibilities from human operators.

The distinction here is that the actions are triggered automatically by changes to the environment during execution rather than as a deployment event. But the information about what has changed is vital, and that means it has to be obtained somewhere.

In a traditional operational model that information usually comes from change tickets or requests. In the case of modern operational models and, specifically, containers this information comes from service registries via a discovery mechanism.

Service Registries and Discovery

The nature of container environments includes the assumption that IP addresses effectively don't matter to the application environment. But they do matter to infrastructure because data still has to be routed and forwarded from device to device in order to traverse the path between the client and the application. In modern environments, those IP addresses often exist for short periods of time (the lifetime of a container/service).

Consider these findings from DataDog (emphasis added):

The rapid adoption of orchestrators (see fact 4) appears to be driving containers toward even shorter lifetimes, as the automated starting and stopping of containers leads to a higher churn rate. In organizations running an orchestrator, the typical lifetime of a container is about 12 hours. At organizations without orchestration, the average container lives for six days.

From https://www.datadoghq.com/docker-adoption>

Imagine if you, as an operator, had to update the routing tables or load balancing pools every six days, let alone every twelve hours. You would do little else. The potential for misconfiguration would be significant and likely grow the longer you were forced to operate in manual mode to manage the changes in a container cluster.

A service registry - like Consul - becomes a critical component of your container deployment. Service registries keep track of instances and services and their associated IP addresses. In this respect, they can be likened to a 'DNS for containers and services'.

So the service registry tracks the current characteristics of containers in the cluster. Discovery is the process of connecting to the service registry (via API or by subscribing to a message queue) of matching instances to IP addresses.

This means that for infrastructure that needs to route traffic to a specific service or instance inside a container cluster, it must be able to retrieve an IP address. Because as much as containers hide the network from the application, they still rely on it to get data from one place to another.

The Fourth Plane: Orchestration

What that does is introduce a new architectural layer into infrastructure that interacts with container orchestration environments. This layer - the orchestration layer - integrates with the container environment and makes use of capabilities like service discovery to automate the discovery of services and instances. That means that a load balancer can automatically discover the members of a pool and continuously update it based on changes in the environment. This alleviates the burden on operations to update load balancing pools manually - and increasingly tedious task when containers are living on average less than one week.


F5 Networks Inc. published this content on 22 July 2019 and is solely responsible for the information contained therein. Distributed by Public, unedited and unaltered, on 22 July 2019 14:04:07 UTC

share with twitter share with LinkedIn share with facebook
share via e-mail
Latest news on F5 NETWORKS, INC.
02/25F5 : to Host Analyst and Investor Event
02/24F5 : Silverline Managed Services Continues Asia Pacific Expansion with New Point..
02/24F5 : Empowers Customers with End-to-End App Security
02/13F5 : New Research Shows Global Service Providers are Increasingly Under Fire fro..
02/11F5 : State of Application Services Research Highlights Key Opportunities to Scal..
02/05F5 : Form10-Q
02/04F5 NETWORKS : Reports Inducement Grants under NASDAQ Listing Rule 5635(c)(4)
02/04BETTERINVESTING : Magazine Releases April Stock To Study And Undervalued Stock C..
02/04SECURE CLOUD ARCHITECTURE : Planning for Business Outcomes
02/03F5 : FormS-8
More news
Financials (USD)
Sales 2020 2 393 M
EBIT 2020 741 M
Net income 2020 388 M
Finance 2020 1 422 M
Yield 2020 -
P/E ratio 2020 20,0x
P/E ratio 2021 17,4x
EV / Sales2020 2,62x
EV / Sales2021 2,15x
Capitalization 7 689 M
Duration : Period :
F5 Networks, Inc. Technical Analysis Chart | MarketScreener
Full-screen chart
Technical analysis trends F5 NETWORKS, INC.
Short TermMid-TermLong Term
Income Statement Evolution
Mean consensus HOLD
Number of Analysts 21
Average target price 149,65  $
Last Close Price 126,45  $
Spread / Highest target 38,4%
Spread / Average Target 18,3%
Spread / Lowest Target -16,2%
EPS Revisions
François Locoh-Donou President, Chief Executive Officer & Director
Alan J. Higginson Non-Executive Chairman
Francis J. Pelzer Chief Financial Officer & Executive Vice President
Mary Gardner Chief Information Security Officer
Geng Lin Chief Technology Officer & Executive VP
Sector and Competitors
1st jan.Capitalization (M$)
F5 NETWORKS, INC.-9.45%7 709
ACCENTURE-6.40%125 158
VMWARE, INC.-0.07%60 273