Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Cloud-Native Applications in Java

You're reading from   Cloud-Native Applications in Java Build microservice-based cloud-native applications that dynamically scale

Arrow left icon
Product type Paperback
Published in Feb 2018
Publisher Packt
ISBN-13 9781787124349
Length 406 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (4):
Arrow left icon
 Olsson Olsson
Author Profile Icon Olsson
Olsson
 Mahajan Mahajan
Author Profile Icon Mahajan
Mahajan
 Kumar Gupta Kumar Gupta
Author Profile Icon Kumar Gupta
Kumar Gupta
 S S
Author Profile Icon S
S
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Title Page
Dedication
Packt Upsell
Foreword
Contributors
Preface
1. Introduction to Cloud-Native FREE CHAPTER 2. Writing Your First Cloud-Native Application 3. Designing Your Cloud-Native Application 4. Extending Your Cloud-Native Application 5. Testing Cloud-Native Applications 6. Cloud-Native Application Deployment 7. Cloud-Native Application Runtime 8. Platform Deployment – AWS 9. Platform Deployment – Azure 10. As a Service Integration 11. API Design Best Practices 12. Digital Transformation 1. Other Books You May Enjoy Index

Testing patterns


Testing large internet applications for the cloud requires a disciplined approach where a few patterns come in handy.

A/B testing

The original intent of A/B testing, also called split testing, was for experimentation to find out the user response of a few selected users to two different web pages with the same functionality. If the users responded favorably to a certain pattern as compared to the other set, it was selected.

This concept can be expanded to the introduction of new features in a phased manner. The feature, campaign, layout, or new service is introduced to a controlled set of users and the response is measured:

After the test window is over, the results are aggregated to plan the effectiveness of the updated functionality.

The strategy in such testing is that for the selected set of users, an HTTP 302 (temporary redirect) is used to switch the users from the regular website to a newly designed website. This will require running a variation of the website or functional...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £13.99/month. Cancel anytime
Visually different images