![]() ![]() The other thing is you want to look at workflows. There are various things like caching, compression, various smart tools, and those type of tools that give way to performance at the front end of the site. You need to at your load testing how you can optimize and tune for performance. In a certain way, in this day you need to know that the amount of users coming to a website is going to be far greater-can I handle that many users at the front of my website? Brick and mortar retailers think of that logically okay I need extra staff to handle the cash registers or answer any queries. That’s making sure that you’ve got enough staff in your store to handle the amount of customers coming to your store. You want to load test for concurrency, which is making sure you can handle the amount of users coming into the site. You’re tracking the response time to that individual it’s critical in making sure you are delivering that experience. ![]() If you have low performance of the front end to the client, you’ll lose that client and they’ll go somewhere else. The second thing is that you want to also track response time, because at the end of the day, what you want to do is deliver the best user experience possible. I think too many companies only monitor the infrastructure and not the app, or they’re not monitoring the app the whole way through to various components where they can identify the weak areas. The weakest link may be an individual service or a product catalog. And you want to not just see the traffic flowing at the front, but you also want to track that traffic that flows through the entire application to the weakest link. I think a lot of companies are monitoring the infrastructure but not necessarily the actual application itself, or vice versa. If you are not monitoring the application and the website, then you’re not going to see where the errors are. Robertson: Things we recommend, number one, is monitoring. ![]() SD Times: What are the things you can do right to make sure you are set up and prepared for the holiday? Discussing these questions with your team could save the company money and keep customers on sites and in applications by itself. #Qmapshack report bug software#(Related: Security testing should be on every DevOps team’s Black Friday checklist)ĬEO of software company NGINX, Gus Robertson, recommended you ask your software team questions like how many users can be handled at once, how do you plan to scale when traffic soars, who will monitor traffic, how can you recover, and who has your back. The IT team, project managers and the CEO will have to answer to shareholders, and discuss why so much money was missed on one of the best days of the year for sales.Įven tech-savvy companies can experience website and application crashes, and the reason is application and web delivery is complex, especially when a site experiences a traffic increase of tens of thousands of users all trying to have one great shopping experience. A lot of revenue is generated during this period of time, and if a site goes down, it’s not just one person who is going to have to do some explaining. Thanksgiving through Black Friday is a busy season for e-retailers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |