In fact, with the vigorous development of financial Internet services, more and more banking businesses have put forward higher and higher requirements on the capacity and flexibility of the system architecture. As for this, many banks’ data center operations and maintenance personnel may have a deep understanding of this change. As for F5, what are the solutions that can help data center IT to transform, improve the efficiency and value of the operation, and make the architecture better meet the requirements of business development? How is the effect?
Cloud-Native is an inevitable trend of application development based on a multi-cloud environment. It can be seen that Cloud Native is still a huge challenge for most traditional enterprises, whether it is a technical form of organizational culture. It cannot be achieved overnight, and the development of technical architecture is inevitable. Continuous iterative development under the premise of ensuring business security. We are currently in such a period of digital transformation. Changes in the basic environment, business agility requirements, and cost control all require IT architecture to have Cloud-Ready features. These changes can be found in:
The traditional data center has completed the virtualization of computing resources;
IaaS platform construction has been completed;
SDN and private cloud has been completed;
PaaS platform construction has been completed or is being completed;
Public cloud and multi-cloud have been used widely;
Banking Technology Company-the development of financial technology;
The rapid development of the business under digital transformation;
Fast application iteration;
R&D agility requirements are getting higher and higher;
O&M and development cross-departmental collaboration has increased;
Service-oriented development requires platform flexibility and flexibility;
Service development requires the decoupling of platform units;
Cloud-Ready is the first step towards cloud-native. The Cloud-Ready mentioned here does not specifically mean that applications must be used by the cloud. It emphasizes that the IT architecture and operation and maintenance are guided by the idea of Cloud-Ready. The specific features are as follows: Use API to automate changes, change the service delivery method from the traditional passive order-taking service to active self-service, change the system architecture to have better flexibility, gray release capabilities, and visualization of application behavior performance.
Facing the trend of DevOps, traditional operation and maintenance personnel need to adopt a new way to carry out IT operation and maintenance. For the current traditional operation and maintenance problems, F5 proposes Super-Netops, which is based on F5 RESTful API, BIG-IQ, and Ansible automation modules, AS3, and other specific technical forms to empower operation and maintenance personnel to achieve efficient operation and maintenance. Super-Netops is a free training program.
L4/L7 separation architecture
Application managers need more fine-grained application policy routing management. F5 operation and maintenance personnel also urgently need to avoid deploying too many applications on a set of F5 equipment to reduce operation and maintenance risks. ADC architecture needs to have better expansion. In order to cope with the increasing business traffic growth, flexible and collaborative two-tier architecture is proposed to solve these problems. According to different actual scenarios, consider the F5+VE architecture or F5+Nginx architecture, which are introduced as follows:
User traffic is accessed through the first layer of the data center hardware F5, this layer mainly solves the boundary high-performance access, SSL offloading expansion, DDOS defense, mainly four-layer processing, and provides load distribution for the second layer to achieve the layer expands horizontally.
On the second layer, F5 VE or Nginx Plus products can be considered according to different conditions. If you require the ADC capability, you can choose VE. If the current operation and maintenance tools are based on F5, and you want to achieve consistent management, you can also choose VE; and if the second layer environment is mainly a containerized environment, you can choose Nginx Plus and realize unified configuration and monitoring through Nginx Controller. At the same time, if you want to implement application publishing and processing based on each App on the second layer, or if you want to use the API gateway capability, you can also give priority to Nginx Plus. In general, the separated L4/L7 layer architecture helps to achieve better architectural flexibility and is the preferred architecture for current data centers.
The F5 Cloud Edition (CE) solution further helps the traditional data center to transform the ADC architecture, achieving a more flexible and automated ADC architecture under the premise of ensuring a consistent user experience. The CE solution is based on F5 Per-App VE and BIG-IQ, which also supports Vmware and AWS environments. Its main features are:
VE deployment based on each application granularity, and it can reduce the operation and maintenance risks caused by application coupling;
Provide detailed application performance and access visualization based on the application perspective;
Different user roles and permissions can be defined, self-service services can be realized, operation and maintenance change methods can be changed, cross-department collaboration can be integrated;
The L4/7 separation idea realizes a more flexible architecture and can realize automatic expansion based on applications.