What is the Nile Architecture?
Overview
The Nile Architecture is based on the core principles of Core, Environment, and Context. These three pillars form the foundation of the Nile network design and management approach.
Core, Environment, Context
Core
When we talk about 'Core' in this context we are referring to the Nile Service Block which provides wired and wireless access infrastructure as a service. Designing our own hardware means we can embed physical and virtual sensors through out the NSB in order to gather the deep intelligence required to deliver fully automated infrastructure.
Environment
An autonomous vehicle uses an array of sensors to monitor it's surrounding environment, using this data to inform decisions and, if necessary raise alerts. Nile monitors the environment where NSB is deployed using a similar model.
Physical Wi-Fi sensors and dedicated monitoring radios in our APs provide real-time data on the wireless environment, while switches in the NSB monitor for cabling health and power fluctuations.
Context
In the Nile Architecture, Context refers to the users and devices connected to the NSB, as well as the services and applications being consumed/delivered. Nile's context monitoring doesn't end with device status, monitoring user/device experience at the point of consumption is vital to our 360 degree view.
For example; when a wireless user establishes a connection they will be authenticated using RADIUS or other NaaC services. Once authenticated they receive an IP address via DHCP from internal systems or Nile DHCP. The user accesses enterprise cloud applications, requiring DNS.
Nile monitors the availability and response time of these services, building an ongoing 'pattern-of-life' dataset which our AI tools can use to take action if there are deviations in normal operations.
The same methodology is used to monitor the user experience across 3,800 automatically identifiable applications.
This 'Outside-in' approach is both unique and fundamental to the Nile Access Service.
No Comments