Could you please describe me difference between backbone,lastmile,private last mile & Software Private agent
Best Answer
See if this helps:
- Backbone: tests are run from major datacenters throughout the globe that allow for "lab grade" testing for availability and performance that is good for alerting upon.
- Last Mile: tests are run from real user machines in various locations throughout the globe. Users volunteer to have these 'peers' installed on their machines which check in to see if any tests are asked of them. These are good for getting an idea of what real users might be experiencing on your site but since it is dependent on client connectivity and their physical PCs it's not as good for alerting
- Private Last Mile can be considered to be the same as last mile but your organization is able to install peers on your own machines (possibly in different org locations) to run tests. The benefit here is you can create your own testing locations based on things like different offices you have to get some performance/availability data for your personnel
- Software Private Agent: somewhat similar to PLM but instead of somewhat 'slimmed down' capabilities of a last mile agent you essentially get the full feature set and configuration options that come with Backbone tests. These software agents are installed on your own hardware you have available to turn them into your own testing node. Prior to the software version of the private agent I believe you needed Dynatrace managed hardware installed in locations to get these capabilities
HTH
James
With regards to James' comment on Software Private Agent (SPA), think of this like an on-premise Backbone node. It uses the same scheduling and alerting logic as Backbone, but is installed (by you) on your on-premise hardware. Unlike PLM, SPA can run multiple browser engines concurrently and can scale to 1000s measurements per hour - PLM is a single process application so can only run as many tests that logically fit into a 60 minute block. Because SPA uses the backbone scheduling engine, test execution is almost instant - no waiting for populations to. It also means that scheduling is much more precise, stating tests per minute opposed to #tests per hour.
Thanks James for sharing the information indetails.
Thanks,
Venkat
