Back to top

CDN - Content Delivery Network

A Content Delivery Network (CDN) is a system of distributed servers that work together to deliver internet content quickly and efficiently to users based on their geographic location. CDNs improve the performance, availability, and security of web services by caching content at various edge locations around the globe, thus reducing latency and server load. This setup ensures that users receive content from a server that is geographically closest to them, resulting in faster load times and a smoother browsing experience. For more detailed information on CDNs, you can visit the Wikipedia page on Content Delivery Networks.

Audienceware utilizes Amazon Web Services (AWS) CloudFront as its standard CDN. AWS CloudFront is a highly reliable and scalable service that accelerates the delivery of web content, including HTML, CSS, JavaScript, and image files, as well as APIs and live streaming. By leveraging AWS CloudFront, Audienceware ensures that its clients' content is delivered swiftly and securely to users, no matter where they are located. This integration not only enhances user experience but also helps in efficiently managing network traffic and reducing bandwidth costs. You can learn more about AWS CloudFront on its official webpage.

Furthermore, AWS CloudFront seamlessly integrates with AWS Web Application Firewall (WAF), providing an additional layer of security. AWS WAF protects web applications from common web exploits and vulnerabilities by allowing administrators to create custom security rules that control traffic based on various criteria. This integration means that Audienceware’s CDN setup not only optimizes content delivery but also ensures that it is secure from potential threats. The combined use of AWS CloudFront and AWS WAF offers a comprehensive solution for delivering fast, reliable, and secure web content to users globally.

 

Back to top

UAT - User Acceptance Testing

from Wikipedia https://en.wikipedia.org/wiki/Acceptance_testing#User_acceptance_testing

User acceptance testing (UAT) consists of a process of verifying that a solution works for the user.[6] It is not system testing (ensuring software does not crash and meets documented requirements), but rather ensures that the solution will work for the user (i.e., tests that the user accepts the solution); software vendors often refer to this as "Beta testing".
 
This testing should be undertaken by a subject-matter expert (SME), preferably the owner or client of the solution under test, and provide a summary of the findings for confirmation to proceed after trial or review. In software development, UAT as one of the final stages of a project often occurs before a client or customer accepts the new system. Users of the system perform tests in line with what would occur in real-life scenarios.[7]
 
It is important that the materials given to the tester be similar to the materials that the end user will have. Testers should be given real-life scenarios such as the three most common or difficult tasks that the users they represent will undertake.[citation needed]
 
The UAT acts as a final verification of the required business functionality and proper functioning of the system, emulating real-world conditions on behalf of the paying client or a specific large customer. If the software works as required and without issues during normal use, one can reasonably extrapolate the same level of stability in production.[8]
 
User tests, usually performed by clients or by end-users, do not normally focus on identifying simple cosmetic problems such as spelling errors, nor on showstopper defects, such as software crashes; testers and developers identify and fix these issues during earlier unit testing, integration testing, and system testing phases.
 
UAT should be executed against test scenarios.[citation needed] Test scenarios usually differ from System or Functional test cases in that they represent a "player" or "user" journey. The broad nature of the test scenario ensures that the focus is on the journey and not on technical or system-specific details, staying away from "click-by-click" test steps to allow for a variance in users' behaviour. Test scenarios can be broken down into logical "days", which are usually where the actor (player/customer/operator) or system (backoffice, front end) changes.[citation needed]
 
In industry, a common UAT is a factory acceptance test (FAT). This test takes place before installation of the equipment. Most of the time testers not only check that the equipment meets the specification, but also that it is fully functional. A FAT usually includes a check of completeness, a verification against contractual requirements, a proof of functionality (either by simulation or a conventional function test) and a final inspection.[9][10]
 
The results of these tests give clients confidence in how the system will perform in production. There may also be legal or contractual requirements for acceptance of the system.

 

Back to top

WAF - Web Application Firewall

A Web Application Firewall (WAF) is a security system designed to protect web applications by filtering and monitoring HTTP traffic between a web application and the Internet. WAFs operate by analyzing incoming requests to detect and block potentially harmful activities such as SQL injection, cross-site scripting (XSS), and other web exploits. By doing so, a WAF adds a crucial layer of protection that helps safeguard web applications from malicious attacks and unauthorized access. For more comprehensive information on WAFs, you can visit the Wikipedia page on Web Application Firewalls.

Audienceware employs AWS WAF as its standard Web Application Firewall. AWS WAF is a cloud-based service that provides robust protection for web applications by allowing users to create and manage custom security rules. These rules can be tailored to the specific needs of the application, offering fine-grained control over which traffic is allowed or blocked. AWS WAF's flexible rule engine and real-time monitoring capabilities ensure that web applications remain secure against a wide array of threats. More information about AWS WAF can be found on its official webpage.

The integration of AWS WAF with AWS CloudFront, Audienceware's standard Content Delivery Network (CDN), creates a powerful security framework. AWS CloudFront distributes content efficiently to users around the world, while AWS WAF provides continuous protection by inspecting incoming traffic at the edge locations. This combined approach ensures that malicious traffic is detected and mitigated before it reaches the web application, enhancing both performance and security. The seamless integration of these AWS services allows Audienceware to deliver fast, reliable, and secure web content to its users, maintaining a high standard of protection and performance.

Back to top

User login