Worldwide Locations
23 Results Found
Discover how the enhanced performance and reliability of Amazon Aurora will help AWS customers reduce performance bottlenecks in their applications. The relatively low cost of Aurora will tempt many customers to migrate workloads to this implementation of RDS.
Amazon Redshift opens up enterprise data warehouse (EDW) capabilities to even the smallest of businesses, yet its costs, security, and flexibility also make it appealing to the largest of enterprises. It allows companies to easily and conveniently scale their EDW needs both up and down, and as a managed service, it allows your team to offload all of the "undifferentiated heavy lifting" of building and maintaining an EDW. Its raw storage costs are about one-fifth to one-tenth of traditional in-house EDW, and AWS has taken great care to ensure its performance is still competitive with those in-house solutions. Before deciding to use Amazon Redshift, however, it's important to understand what it is and is not.
The process of learning how to subnet IP addresses begins with understanding binary numbers and decimal conversions along with the basic structure of IPv4 addresses. This paper focuses on the mathematics of binary numbering and IP address structure.
Network Functions Virtualization (NFV) is gaining momentum along with Software-Defined Networking (SDN). This paper examines the history of NFV and explores the prospects for networking to gradually evolve from a hardware-centric approach to a software-driven model. It concludes with an examination of future market implications and how NFV can help organizations to achieve their goals.
After a review of Software-Defined Networking (SDN) and its close cousin Network Functions Virtualization (NFV), this white paper addresses three main deployment scenarios: SDN without deploying cloud computing, cloud computing without deploying SDN, and deploying cloud computing in conjunction with SDN. We'll look at use cases, when the approach makes sense, and any applicable limitations.
Database Management Systems (DBMS) have been monolithic structures with their own dedicated hardware, storage arrays, and consoles. Amazon Web Services (AWS) realized that while each company can use unique methods of collecting and using data, the actual processes of building the management infrastructure are almost always the same. AWS remedies DBMS problems with its Amazon Relational Database Service (Amazon RDS).
Session Initiation Protocol (SIP) is an internet signaling protocol, developed by the IETF (starting in 1996), for establishing, maintaining, and tearing down sessions between a variety of real-time media, including voice, video, and chat. SIP allows endpoints to locate other endpoints, whether stationary or mobile. SIP doesn't have to worry about transporting voice or video as Real Time Transport Protocol (RTP) takes care of that. It also relies on Session Description Protocol (SDP) to negotiate capabilities and codecs. SIP does not provide a Directory Service or Authentication, but it does work with services such as LDAP or RADIUS. SIP is only concerned with signaling. This white paper is going to look at the way SIP is used in the converged Unified Communications environment.
A local area network (LAN) provides a path of communication, allowing the delivery of packets of data, voice, or video originating from the sender (logical source address) to the receiver (logical destination address). Ethernet is the most common LAN used. As you start to learn about networking, remember that communication and the movement of large numbers, whether it is people, cars, mail, or network traffic, have a commonality. Everything you know and use in your daily life can be compared to the way traffic moves.
The OSI model is a conceptual tool used to discuss and describe network functions. The use of a standard reference model is essential to communicate ideas as well as create new technologies. It is a good idea to be familiar with the OSI model, the features assigned to each layer, and examples of common protocols or technologies associated with the OSI layers.
As with the adoption of any new technology, the move from IP version 4 to IP version 6 will take a number of years to complete. During that transition phase, various mechanisms will be necessary to continue support of the older protocol as the newer gains widespread momentum. In addition, there has been some evolution even within the availability of these mechanisms, some of which have already passed from general use into deprecated status. Network engineering professionals already proficient in the use of IPv6, as well as the available coexistence mechanisms, will undoubtedly stay in high demand throughout this process.