Applications and infrastructure software defined promise to data centers more flexibility, efficiency and resistance virtualization and designs of monolithic applications.
Going beyond virtualization that includes a process provisioning largely manual, which can take a long time and be riddled with errors, containers offer a more modular approach to application development. Developers assembled application software defined from a number of independent components or modules, called microservices. Each microservicio runs in a container and communicates through application programming interfaces. APIs are operated at the microservices, giving a path components in containers to pass data and commands between the various functional modules that create the application running. IT teams automate deployment, monitor performance and scale components to accelerate additional containers and load balance traffic between applications API. Unused containers can be turned off, saving computing resources.
While there are several advantages, an application-defined software can not run on the data center or infrastructure without some degree of control based on the cloud.
the resources behind applications
infrastructure monitoring and automation software define and manage virtual machines (VM ), containers, storage instances, network segments and other elements needed to deploy and scale application components in accordance with established standards and policies. For example, if the system performance of an application queue falls below acceptable speed, software-defined infrastructure components automatically accelerate temporary additional queue, any available server. While any application can be enlarged or reduced over time, this level of scale orchestrated self is important for loads of irregular or unpredictable work.
In this way, the APIs are not only a staple of applications defined by software; they also form a basis for the infrastructure software defined. No behaviors API to determine when additional performance is needed and then initiate steps to remedy the situation, IT professionals should monitor constantly and adjust the resources allocated to an application.
Applications and infrastructure as defined by software increasingly adopt the notion of horizontal scaling against vertically. Traditional applications are based on the vertical scale, increasing the resources allocated to a main instance of software. the horizontal scale, however, doubles instances of application components-usually designed as microservicios- with increasing demand for such functionality.
The horizontal scale is the most attractive approach because it allows better monitoring and automation. For example, when monitoring reveals that API calls time to service a component are unacceptably low, a defined infrastructure software automatically duplicates one or more components-and balances the traffic load API-for these components additional work together to handle the increased workload of the application.
on the other hand, if monitoring reveals that API calls are easily handled with ample resources, infrastructure defined by software can automatically delete or scale down, the additional components to free up resources for other jobs.
the truth about software-defined architecture
The term “software-defined” is linked to a number of technologies: storage, networks, applications, energy, infrastructure and even entire data centers. The concept of using software to deliver and optimize elements of the IT environment has an exciting promise, but add the label defined by software to anything creates confusion and can be misleading for IT professionals navigating the realms of applications and infrastructure software defined.
Take software-defined architecture (SDA), for example. The term, Gartner coined in the sense of an extension of the software defined networks and oriented software architecture is easily confused with infrastructure software defined. However, software-defined architecture tries to encapsulate the hardware and internal services data center, and isolate those resources applications, services and devices that may be exposed to users, segregating effectively producers or suppliers the consumers. The creation of this limit hiding or abstracting the inner workings of the company-the servers, storage systems and networks- scheme enabling IT teams change, update or replace without affecting the applications, services or devices facing the end user .
to create such logical boundary, usually called a gateway software, including data center resources and external users, SDA is based on two sets of APIs. “Internal” API organize and conduct internal systems, optimized for performance data center side. “External” API, which are optimized for the operation of long distance networking can safely access to the internal API.
A gateway software is built from a combination of components software, including integration brokers, managers API, API gateways and SOA interface. When implemented correctly, the gateway software can translate API and handle security, orchestration and routing.
This approach abstracts applications, services and devices underlying data center that provides. This abstraction helps protect the data center and enterprise data; when combined with APIs, abstraction also decouples the end of suppliers users, which means that changes in one will not affect the other.
The vision of Gartner architecture defined by software still in its infancy, and it remains to see how that vision and terminology evolve over the coming years.
No comments:
Post a Comment