The future: For everything an API

It’s becoming apparent already: Anything that consumes power is going to be connected in some way to the Internet. Cars, refrigerators, thermostats, TV, personal drones, you name it. There will be a way to connect with it, interact with it, and control it.

APIs are a powerful way to glean extra value from an enterprise’s data assets and digital resources, extending the reach of products and services, building the brand, and even generating revenue. It requires a thoughtful approach and commitment of resources to make it work.

“We call it the ‘Internetting space,’” says Kamenetska. “We’re really in a post-website era…Anything that you touch is going to become Internet-enabled, and the apps that are going to be there and the experience that you’re going to be having on those devices are really made possible by APIs.”



You may also would like to see:
1. ABCs of APIs
2. Performance monitoring: There’s an API for that
3. Testing on mobile devices
4. Web application monitoring

Performance monitoring: There’s an API for that

While IT departments are quickly racing into the private API game with their own data, they’re also being transformed by the ability to consume a greater number of vendor services by API. For example, data access via API can help ensure competitive performance for websites and apps by providing timely access to actionable data, and the ability to quickly filter the noise from the meaningful numbers. Keynote offers APIs that enable clients to grab their data in real time in order to create the visualizations that best serve their operational data needs — including combining with data from other sources — and to leverage software tools to quickly surface potential performance issues. -

With our API, Keynote frees client data from our systems,” says Aaron Rudger, product marketing manager at Keynote Systems. “Operations groups need to implement their own analysis, and integrate multiple tools to do their job. All their data is more valuable if it can be leveraged together. The Keynote API lets them pull in their performance data to use however they need it.

You may also would like to see:

1. Mobile developer tools
2. Mobile Testing Services
3. Web Application Monitoring

Birth of the Web API

APIs did not start with the Web. In fact, one of the most successful API stories ever is the Microsoft Windows API, which enabled all those third-party developers to create applications for Windows, and in turn propel it to near-monopoly status in desktop operating systems. Today, though, the talk is all about Web APIs and the interconnected ecosystems they support.

Among the earliest players to embrace Web APIs were the Internet giants-to-be such as Google, Amazon, and Salesforce. They started leveraging APIs in their early days, which helped them to become the dominant online forces they are today.

“They looked at these platforms they were creating and asked themselves, how do we generate interest?” says John Rakowski, a Forrester Research analyst serving infrastructure and operations professionals. “How do we generate further partnerships with our customers and with partners out there who can help us innovate a lot quicker, who can utilize our platform to build our brand, but also to create a partner ecosystem?”
The answer was to pursue a proactive API strategy, reaching out to developers and supporting them as they created their own layers of interface and functionality on top of Google’s or Amazon’s or Salesforce’s data. The developers could be using the APIs to create applications for niche markets, or to integrate with other applications.

In addition to creating a partner ecosystem, Rakowski says that opening up a platform via APIs “also gets your brand out there and makes people aware of it very, very quickly, because they can interact with your platform, which means all-in-all, it leads to faster growth because there’s more awareness of your platform in the market.”

Source: Keynote Benchmark

You may also would like to see: 
1. ABCs of API
2. Mobile Testing Challenges for Web Applications
3. Testing Mobile Applications
4. Cloud application performance monitoring

The Four Types of Clouds Explained

In meteorology, you have cumulus, cirrus, stratus, and nimbus. In computing, you have private, public, hybrid, and community. Here's what each means:

Private cloud: The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premise or off-premise.

Public cloud: The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).

Community cloud: The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.

You may also would like to see:
1. Performance monitoring for your cloud applications and services
2.  Private Cloud Monitoring

An Overview Of APIs And How They're Changing

Virtually anything you do online all day long — and virtually everything that makes the Internet in 2013 so convenient, helpful, portable, and smart — is made possible through the magic of APIs. Application Programming Interfaces enable all the devices on the Internet to access data and resources without the user having to actually visit the source.

It’s reasonable to say that APIs have totally made the online experience what it is today. They extend our Internet connection far beyond the browser to phones and tablets and every kind of connected device, to the point where one no longer thinks of being “online” — we’re just connected. And when you’re accessing the Internet the old-fashioned way, through a browser on a computer, APIs have transformed websites into data-driven, interactive, media-rich experiences.

Before long, everything we do, from driving our cars to managing our health and finances to entertaining ourselves to controlling every gadget, system and device in our lives, will be accomplished through the interaction of APIs.

You may also would like to see:

1. Mobile web readiness use cases

2. Characteristics of Web 2.0 Applications

3. Testing Mobile Applications

Web Performance Monitoring Just Got More Better

Recently, Keynote released an exciting new product Keynote Real User Perspective. This newest member in the Perspective family of monitoring services delivers actionable insight into the performance of Web and mobile sites based on the experience of real users.

Real User Perspective is special in 3 ways:

1. Lightweight SaaS
2. Start-to-end Real User Journeys
3. Integrated with Synthetic

Keynote now offers the most comprehensive offering for end user experience monitoring delivered as a service. It culminates a tremendous amount of development, infrastructure orchestration, and feedback from the scores of customers who participated in our product advisory and beta programs. Customers can now complement active, clean-room, synthetic monitoring with passive, real user monitoring that aligns to business outcomes—a marriage made in heaven! We think that’s more intelligent web performance monitoring.

You can request for a free trial now!

Devices For The Always-On-Workforce

Today’s mobile email, document shuffling, and occasional presentation are small potatoes compared to what’s coming. Off-the-shelf productivity apps? Yesterday’s news. Businesses mobilizing their core enterprise systems will give workforces anytime, anywhere access to company data, systems, and infrastructure. It’s not unreasonable to think that ultimately, anything that can be done on a company-networked computer will be able to be done on a smartphone or tablet. (And a significant number of those devices will be personally owned by the workers.) - 

Marketing managers will access corporate analytics on their phone while they’re in a meeting. Plant supervisors will order parts for their assembly line from an iPad. Field service reps will check the warehouse for repair parts while they’re at a customer site. And of course, the emails will continue to flow back and forth while workers are at the opera, with their kids at the playground, or on the road. 

Some companies are well on their way towards such uber-connectedness. And many more are taking their first steps in that direction.

Related Links
1. The March Towards Mobilization
2. Mobile Web Optimization
3. Mobile User Experience Trends

Get Moving Toward Enterprise Mobility

The smartphone and tablet revolution has passed the tipping point in the enterprise, driven from every side. Businesses want increased productivity, efficiency, and agility.

Employees want flexibility to work anywhere using their preferred mobile device. And the major software providers and their partner ecosystems are scrambling to build the conduits and apps to connect enterprises with their workers, wherever those workers may be.

A device adoption strategy, security policy, app development process, and automated testing programs are the obvious overall steps toward enterprise mobility. Not so obvious are the myriad infrastructure and management requirements behind the scenes, such as readying the back-end for mobile, building the data conduits, and managing a large and heterogeneous device pool. It’s a complicated and multifaceted process, but one that can pay big rewards in terms of increased productivity and efficiency, cost savings, responsiveness, and employee satisfaction.

Related Links

1. The March Towards Mobilization

2. Challenges To Making The Enterprise Road-Ready

3. Making mobile testing manageable

4. Smartphone application testing

5. Mobile Software Testing

Challenges To Making The Enterprise Road-Ready

There’s a lot more to enterprise mobility than building apps and distributing them to the workforce. Security, functionality, performance, and connectivity are among the major challenges IT departments face.

Since the early days of mobility, IT departments kept their mobile workers locked down with closed systems and standardized, company-issued phones. It was largely a BlackBerry world, with only authorized apps allowed on the phone. This simplified the security challenge, with IT maintaining reasonable access control, as well as the ability to remotely wipe phones if these were compromised.

The smartphone revolution, though, first saw workers double-clutching — the company BlackBerry in one hand, their own iPhone in the other — and then demanding that IT enable their personal phones to access company data so they could ditch the BlackBerry entirely. It was the beginning of the new, Bring Your Own Device phenomenon. But mixing up company and personal data and apps on phones that aren’t in IT’s control, on unsecured networks, has opened up Pandora’s box for corporate data security. This remains one of the biggest challenges for enterprise mobilization.

Ensuring the performance of new mobile apps is another huge challenge. Building mobile apps is more complicated than desktop apps, typically involving up to four operating systems and various form factors. iOS and Android are musts. The BlackBerry is still in play in many enterprises. And some are anticipating that Windows Phone will get a boost with the rollout of Windows 8.

Testing enterprise mobile apps is an even more complicated issue. Even if development is restricted to the two leading operating systems, there are scores of screen sizes, resolutions, UI nuances and other variations to deal with, particularly on the Android side. Proving an app on one device (or even several) for an OS does not guarantee it will function properly on most or all devices running that OS. It’s a complex and critical development challenge.


Related Links

The March Towards Mobilization

Optimize End User Experience For Mobile Devices

Characteristics of Web 2.0 Applications

The network as a platform
Applications are delivered entirely through a browser, or even a microbrowser that resides on a handheld device such as a PDA or mobile phone.

A collaborative environment
Whereas a traditional Web site publishes content, many Web 2 sites act as a hub for sharing content. Site users may supply,
even control, the published content.

Social networking
Many Web 2.0 applications include features that connect people with common interests

Hybrid applications (mashups)
Standard Web protocols and interfaces allow third-party applications to integrate both data and functions from existing ones.

Rich media interfaces
Compared to the original concept of the Web as a collection of HTML hypertext documents, user interfaces are now more dynamic and more
interactive, incorporating a variety of media including audio and video streams and voice interactions.


Related Links

1. Testing Web Applications
2. Web application monitoring

Mobile Cloud Testing Is ‘The New Norm’

With the deal of expensive and daunting task of setting up in-house mobile testing capabilities, more and more companies are turning to the cloud. Cloud service providers such as Keynote DeviceAnywhere provide immediate access to robust toolkits and, critically, a broad pool of real devices that can be tested live on carrier networks.

Currently, 28 percent of WQR respondents say they do their testing in the cloud; 39 percent report that they will be doing cloud testing by 2015. This rapid increase in adoption prompted the WQR authors to declare that “testing in the cloud is becoming the new norm.”-ibid. Device selection, speed, lower costs, and on-demand availability are some of the reasons companies are opting for cloud testing services instead of attempting to handle mobile testing in-house.

“It seems like just about everyone is interested in mobile testing services at this point,” Obstler says. “We see certain industries leading the way. Financial — look at how popular and powerful mobile check deposit has quickly become — and then healthcare, and insurance. Companies in these industries are focusing on both internal and external apps. It becomes very important, very quickly to have a process and platform in place to test these apps, or else it’s just overwhelming.”

Related Topics

1. Building a Mobile Automation Testing 2. Mobile Testing Challenges for Web Applications

US Analysts Predict a Rapid Migration to Mobile

Over the few years since 2007, There have been an explosion in mobile apps to make our lives convenient and more efficient. And it appears there is no letting up. Recently, Forrester Research noted that there are now 7.3 billion mobile devices in a world where there are only 7 billion people.


"Mobile applications in the Enterprise may be a future vision for many companies, but mobile is a vision that is being realized much quicker than many had expected.  What does the rise of mobile mean for the enterprise?

The global Enterprise Mobility (EM) market is expected to grow annually by 15 percent every year, eventually reaching $140 billion by 2020. By 2020 roughly 10-12 percent of the enterprise IT budgets will be spent on mobility, compared to less than 5 percent today. These numbers are based on a report by Nasscom in association with Deloitte.

Read the full blogpost on Keynote Mobility

Related Links
1. How do you plan to deliver content and services to your mobile audience in 2013?
2. New IDC Report: The Evolution of Mobile and Web Load Testing
3. Mobile Applications Testing & Strategies

Continuous Testing of Mobile Applications

How you can ensure continuous testing while developing mobile applications How do you ensure that updates and upgrades work correctly answer is fingers and eyes! Many mobile devices and applications that can not be avoided for the fingers and the eyes of the method is the only way to test the application, at least in this situation.

Manual testing should be performed in the cycle before it begins and life after the release of the application. Despite the advantages smells, manual testing can also be disrupted by the following reasons: Drastically slow down the development process and it leaves a wide margin for error."

Hence, the need for automation. This provides the ability to remotely automate your test cases on  mobile devices, from anywhere in the world. This advanced "scripting" and "recording" technology finally provides the tools necessary for efficient mobile testing. Supplemented with manual testing on new devices, it can provide the perfect balance between efficiency and optimization to ensure the highest quality of any mobile app or website.

Know more about automating your mobile testing

Related Links;

1. Optimize End User Experience For Mobile Devices 2. Mobile Device Emulation

Responsive Web Design and Mobile Performance

In this post, we will discuss about what will be possible in the future using responsive web design, and what still needs to be improved.

Like the quest for the Holy Grail, Web developers have been searching for a magical solution that will make every website shine on any and every device. It appears that, if not the actual Grail itself, they have come upon something that takes them leagues closer to that elusive goal. It’s Responsive Web Design, or RWD, and in the past year it has been picking up tremendous momentum as the go-to solution for getting content onto an ever-growing and ever-more-disparate pool of Web devices.

Through a combination of techniques, responsive web design promises to render content in a visually pleasing, highly usable format, true to the designer’s intentions, on virtually any device. Many websites are achieving that promise in large measure. But at the same time, questions arise as to whether mobile performance is taking a back seat to visual appeal and usability. The short answer is, it doesn’t have to. As with any development technique for mobile or desktop, performance depends on what’s being included and how it’s being included.


Related Links
1. Perform Website And Web App Testing
2. Racing Toward Responsive?
3. Verify Mobile Content by Emulating Over 2,200 Devices

The Case for Automated Mobile Testing

Automating your mobile testing has two main advantages, increasing efficiency and cost savings. With automated testing, imagine you are able to conduct manual tests with simple scripts and run it repeatedly. You save human resources and money. Automated testing helps QA teams quickly create and test scripts to capture, verify and replay user interactions.

Every second saved by forgoing continuous manual input adds up, thus relieving the stress and resources, enabling testing to be streamlined. Some companies are able to automate all of their mobile testing. Depending on the type of app you are testing, at least 80 percent of it can be automated, however, factoring app functionality on different devices and platforms, there is often a need to supplement it with ad hoc manual testing.

Leveraging the tools that help measure and evaluate the quality of your mobile app or website, you can use real device testing or automated scripting to assess the quality of services. This will help you to determine the user’s experience in the environment of the App or service once its launched.

Need more reasons to know why you should automate? Read this Why Test Automation

Easy Way to Record Mobile Testing Scripts!

Keynote Systems -  global leader in Internet and mobile, cloud testing & monitoring. Recently announced new, advanced scripting tool – ScriptObjects.

With DeviceAnywhere ScriptObjects, users can create object-level scripts for native, web, and hybrid applications within a real-device testing environment. Coupled with DeviceAnywhere’s existing image and text UI-based scripting capabilities, DeviceAnywhere ScriptOjects enables you to use the best testing and verification technique for your use case, with one script that seamlessly works across devices.

Object-level scripting for mobile web content acts on individual web elements at the code level.  This means that you can record a script on one device, and play the exact same script back on another device regardless of the screen-size, manufacturer or operating system. Object-level scripting for native apps does the same thing for devices of the same platform while acting on native objects. Your scripts will be more resilient through UI changes, lowering maintenance costs.

Request Mobile Automated Testing Free Demo 

Related Links

1. Mobile Application Testing
2. Mobile Browser Compatibility Testing

Building a Mobile Automation Testing

Desktop-based testing it’s a no-brainer: Use object-based scripting to maximize reuse across platforms/browsers.

In today’s mobile world it really isn’t that easy. There are many different platforms, OS versions, form factors and carrier/manufacturer customizations. Multiply that by mobile web, native app, or some hybrid in-between and you’ve got yourself a healthy testing matrix. A daunting task for even the most skilled Automation Engineer.

In order to tackle this problem, an Automation Engineer cannot simply look at it from a “one size fits all” perspective to create a set of objects and re-use them across all combinations of platforms. For example, there are fundamental differences in how an app behaves on iOS and Android, even with something as basic as a “back button” has its quirks.

In order to truly make your mobile testing easy, TCE automation is the right solution for the job. The solution combines the convenience and efficiency of test automation with the accuracy of live mobile interactions to generate reliable, reportable and actionable results.


Related Links

1. Mobile Device Testing
2. Mobile Web Readiness
3. Mobile Application Testing Strategies

A Quick Checklist To Ensure Site Uptime When Switching Web Hosts

There comes a time in every website's life when it must grow up and leave behind the infrastructure that got it to where it is. As traffic scales up, site uptime and speed become paramount; Web hosting companies are compared, and finally it is time to move house, i.e. to switch Web hosting companies. Moving sites without a glitch is important, even critical, and with some experimentation, I hit upon a checklist that should help anyone plotting a move. Follow these steps and your site will remain up throughout the move and your site visitors and online business teams will thank the IT department for its forethought.

1. Move When the Traffic is Low.
2. Switch Your Email Profile at Both Web Hosting Companies.
3. Create a Mirror Site and Monitor It.
4. Copy and Import Your Zone File.
5. Setup a Virtual Host at the Destination Server.
6. Start Your DNS Move.
7. Monitor the Move Using Website Performance Monitors.
8. Setup Availability Alerts to Fire If Content is Missing.
9. Conduct a Traceroute Test from All Over the World.
10. Tweet and Enlist Your Customers.

And that's all folks! You can read Keynote Recent Blog Post detailing these 10 steps to ensure that your website remains up and running during any change to its infrastructure. Follow them, and mimize or eliminate all downtime.

Related Links

Challenges of creating and managing robust applications 

Analyzing software applications and supporting infrastructures

Insights on DDoS Attacks Against Websites

Recently, Keynote Systems was asked to comment on a widely publicized attack against a company online. The attack, known as a distributed denial of service(DDoS), was targeted at a network of web servers primarily located in Europe. DDoS attacks against websites have occurred periodically for years. Unlike past incidents, the nature of this particular attack was characterized as severe enough to have caused broad disruption on the Internet. The suggestion made was that users like you and I may have found our email delayed and websites either slow or unavailable.

While many methods exist to understand the impact of web attacks like this, Keynote's web performance,  monitoring service and global network provide a unique perspective--the end users' perspective. Keynote  business is monitoring websites for their customers so that they have a consistent and accurate source of information about their site's performance. But they also use that same technology to monitor select sites across the Internet and make this data publicly available in the form of an index--actually, 43 indices. And they also use it to provide another free service called The Internet Health Report that shows what's happening across the major U.S. Internet Service Providers in real time.

Keynote periodically test a wide range of websites from their network of hundreds of monitoring agents connected to different ISPs all over the world. These agents pretend to be a site visitor and measure performance during their visit.

One of their indices monitors the U.S. banking sector. The financial services industry has been hit hard of late by DDoS attacks. You can read the Keynote blog post Understanding the Impact of Web Attacks - the User Perspective


Source: Keynote Systems

Optimize End User Experience For Mobile Devices

Today it’s all about CONTENT, being able to access it QUICKLY wherever you are and whenever you want…and iPhone does that well.

The first thing I did after getting my phone was not a phone call, but I went to Facebook and updated my status.

If I am a content provider, I would love to get the full insights for my website. Since my users could be coming from any device, I will need to understand how my site downloads and performs on different devices. This will help me improve the end users experience at least on popular devices, if not all of them. Optimizing it for one device is just not good enough!!!


Related Links

• Mobile Device Testing From End User's Perspective
• Website Availability Monitoring
• Mobile Application Testing - On Any Device, Any Network

Monitoring Internal Applications with Cloud Application Perspective

With Cloud Application Perspective (CApP), Keynote can now be used to monitor internal and private applications just easily as one might monitor a public one. Since CApP is a customer installable monitoring agent, it can be easily deployed in branch offices, customer locations, and of course data centers to monitor internal private communications. Much of what the First Mile and API How To posts cover with respect to scripting and deploying measurements are equally applicable to internal applications.

An important detail when deciding to monitor internal applications is why. Well the obvious answer is that internal users are impacted by performance issues, which in turn influences their productivity and satisfaction. These are factors that a sophisticated IT operation should care about in the age of cloud computing and web applications. However, another reason is vendor selection and contract renewal. Monitoring services with Cloud Application Perspective provides a wealthy of good data that can be used to better choose among vendors, inform contract renewals, and in general keep them honest.

Here is the complete guide on Cloud Application Monitoring.

Can the right mobile optimization trick be a treat for customers?

After a night of trick or treating on Halloween, all children will agree; there's always that one piece of candy in their bag that nobody wants. The treat may have been given with good intention but really ends up being sour grapes in a wrapper instead.

Online retailers have their own sets of tricks of the trade to better acquire and retain mobile customers. But sometimes, those treats can be sour grapes in a wrapper for the end user.

With increasing statistics showing the impatience of mobile customers (65 percent of mobile users prefer a sub-4 second download speed), previous holiday season was a critical test on mobile user patience and retail performance.

Implementing key best practices can help you prepare for the next holidays.


Related Links

1. App, Website, Or Both? 2. Mobile Device Testing

Which Real Browser Do I Use to Monitor My Site’s Performance?

Which browser should I use to monitor my site’s performance? Should I test for all the most popular browsers? IE still has the majority of users in the market place—but shouldn’t I also test with Firefox?‖
Testing with a real IE browser is the most effective strategy because of the IE audience and because open web standards do not require you to conduct extensive testing using multiple real browsers – you gain the most by testing first using IE. Another reason to test with IE is that application developers often testing their applications using Firefox, only to have the application fail or not perform well when IE users begin to use it. Since most of the other browsers support the World Wide Web Consortium (W3C) features and standards, testing for the most complex browser (IE) is recommended.

The two most widely used browsers are Microsoft Internet Explorer and Mozilla Firefox, with over two-thirds of the market worldwide—nearly 70% of site visitors use these two browsers.

Ask yourself the fundamental question, ―Which browser is our customer base using, and is our Web performance being monitored with that real browser or an imitation browser?

Related Links

1. Why Testing Web 2.0 Sites Requires Real Browser Measurements

2. Website Availability Monitoring 

3. Test Your Site on IE 9 and Measure User Experience  4. Mobile Browser Compatibility

Monitor End-User Performance with Real Browser Technology

The performance of a Web site can be monitored in several different ways. The most basic end-user performance metric comprises the entire time it takes from when a user requests the desired page until he or she can view that entire page on their Web browser. This time includes not only the network components such as DNS lookup, initial connection, and content download, but also any client-side execution of plug-ins and video, sounds, or animation. 

When you measure client-side execution you need to use a real browser-monitoring product if you want to capture the complete end-user experience. WhyReal Browsers Matter

This user performance time also has two distinct versions: performance for a first-time visitor and performance for a returning visitor. Since returning visitors comprise the vast majority of traffic to a Web site, understanding which content is being cached and how the returning user is experiencing the site is critical. 

The use of a real browser allows you to see the browser’s behavior for the returning user and validate that performance is being optimized for the returning user.

Related Links

1. Mobile browser compatibility check

2. Real tests use real devices 3. Mobile device compatibility

A New Approach to Gathering User Experience Data

Keeping in mind the constraints about the group of users you plan to study and the kind of data you need to collect, the next challenge is selecting the right methodology.

The desire for large, unbiased, representative samples suggests using automated methods such as log file analysis. However, the need for rich, contextually sensitive session data suggests usability lab testing. Thus, there is a dilemma of quantity versus quality: log files generate a larger quantity of data, whereas usability labs generate much richer data. Furthermore, each of these methods can produce serious flaws in its area of strength when used inappropriately or inconsistently by different researchers. The solution is in the middle where the two ends of the spectrum meet.

New data collection methods can help usability researchers capture large amounts of user experience data while monitoring website. These solutions combine the best of both approaches with marginal sacrifices. The result is a more robust and standardized process to conduct consistent, reliable, actionable usability research.

Keynote WebEffective™ was developed to automate usability data collection and to strike the right balance between quantity of data collected and the quality of that data. As with other Keynote performance management solutions, WebEffective is deployed as a service using a network of servers positioned
between actual site visitors and Web site servers. for analysis. By redirecting visitors to your Web site through Keynote servers, WebEffective can maintain its position unobtrusively monitoring
and recording user interaction. WebEffective is able to see and capture all HTML content downloaded to the users’ computer as well as all the upstream data requests sent to the Web server. WebEffective then reconstructs the data streams into actual visitor sessions

Related Posts:

1. Monitoring User Experience of the Cloud  2. How to gain actionable data to demand better performance? 3. Website Availability Monitoring From End User's Perspective

Measuring & Monitoring Web 2.0 Applications

The Internet and the Web continue to evolve to deliver new customer
experiences and increased application utility. The label “Web 2.0,” while
imprecise, signifies the newest and best examples of this evolutionary
process.

Web 2.0

Many organizations are now adopting these Web 2.0 technologies and design
methods to enable the creation of richer and more responsive interactions.

But to be effective, the resulting applications must also be significantly more
complex than traditional Web sites, complicating performance management and
imposing new requirements on performance measurement tools.


Related Links

1. App, Website, Or Both? 2. Web performance with streaming media 3.Web Performance Monitoring – From Traditional to a Richer Media