Welcome!

Machine Learning Authors: Yeshim Deniz, Pat Romanski, Elizabeth White, Liz McMillan, Zakia Bouachraoui

Related Topics: Microservices Expo, Java IoT, Machine Learning , Agile Computing

Microservices Expo: Blog Feed Post

Three Web Performance Mistakes and How to Avoid Them

Could you imagine NASA sending a rocket into space without testing it first?

Could you imagine NASA sending a rocket into space without testing it first? What about a racing team putting a brand new car on the track without taking it for a few laps to test the handling and stability? It seems to me that testing is inherent in every technical field — except for website development that is.

Too often we see websites where it’s clear that design was the main priority, while testing the site’s functionality and user experience was just an afterthought. What you’re left with is a great looking website that feels like it is being sent over the Internet via carrier pigeon. And that’s going to send your customers to another site, and fast.

So let’s look at the three biggest performance mistakes many developers make when they create a website and some simple ways to fix them.

Identify your audience. When developing a website, many organizations fail to identify who their audience is and where they are located. This is important for sales and marketing purposes, but also for identifying which of the many available architectures, platforms, and technologies can best handle that anticipated traffic. As a general rule, the farther away from something you are, the higher the probability you will experience latency or other performance issues. So before starting development, test various architectures to see which ones best meet the parameters of your target audience. If your audience is scattered geographically, consider a CDN to localize delivery of content and alleviate some of the issues that can come with distance.

Avoid the quick fix. One of the most common development issues relates to database performance. Database performance issues are typically the result of misconfiguration or a lack of optimization, and they manifest themselves as web delays or slowdowns. To keep on track with tight production schedules, organizations often don’t take the time to understand the root causes of these issues. Instead they attempt a quick fix, simply throwing more bandwidth, memory, or servers at the problem. This is a costly and incomplete remedy for an issue that will likely arise again if not dealt with appropriately from the start. Instead, developers should look to enhance site speed through caching, CDN deployment, or image optimization.

Test early, test often. Often web development teams wait until post-production to test a website’s performance, when the finishing touches have already been applied. But what if your testing reveals weaknesses in your site’s performance or architecture? Will you be prepared to go to your boss (who is anticipating the site to launch at any time now) and break the news that a serious fix is in order? That an error overlooked since the early stages of development is threatening to push your website launch past deadline and over budget? And will your organization be willing to make these concessions, or will it choose (or be forced) to forge ahead with a vulnerable site just to launch on time?

Performance issues uncovered this late in the game will be more difficult, time consuming, and costly to resolve than if you had caught them early on. And if you choose not to resolve them you risk a critical website malfunction and the lost business, customers, and bad press that come with it.

Performance testing should be strategically budgeted and accounted for at various stages of the development process, not regarded as just another check in the block, a formality to be completed before rolling out your site. Before development even begins, you should set benchmarks for how many concurrent users you want the site to be able to serve and what its traffic limits will be. Then, periodically throughout the development cycle, test your site’s ability to meet those goals, and optimize web performance.

By no means are these the only mistakes or pitfalls an organization can run into when launching a new website. What other web development or performance problems have you run into?

Read the original blog entry...

More Stories By Sven Hammar

Sven Hammar is Co-Founder and CEO of Apica. In 2005, he had the vision of starting a new SaaS company focused on application testing and performance. Today, that concept is Apica, the third IT company I’ve helped found in my career.

Before Apica, he co-founded and launched Celo Commuication, a security company built around PKI (e-ID) solutions. He served as CEO for three years and helped grow the company from five people to 85 people in two years. Right before co-founding Apica, he served as the Vice President of Marketing Bank and Finance at the security company Gemplus (GEMP).

Sven received his masters of science in industrial economics from the Institute of Technology (LitH) at Linköping University. When not working, you can find Sven golfing, working out, or with family and friends.

CloudEXPO Stories
By 2021, 500 million sensors are set to be deployed worldwide, nearly 40x as many as exist today. In order to scale fast and keep pace with industry growth, the team at Unacast turned to the public cloud to build the world's largest location data platform with optimal scalability, minimal DevOps, and maximum flexibility. Drawing from his experience with the Google Cloud Platform, VP of Engineering Andreas Heim will speak to the architecture of Unacast's platform and developer-focused processes.
Wooed by the promise of faster innovation, lower TCO, and greater agility, businesses of every shape and size have embraced the cloud at every layer of the IT stack – from apps to file sharing to infrastructure. The typical organization currently uses more than a dozen sanctioned cloud apps and will shift more than half of all workloads to the cloud by 2018. Such cloud investments have delivered measurable benefits. But they’ve also resulted in some unintended side-effects: complexity and risk. End users now struggle to navigate multiple environments with varying degrees of performance. Companies are unclear on the security of their data and network access. And IT squads are overwhelmed trying to monitor and manage it all.
To Really Work for Enterprises, MultiCloud Adoption Requires Far Better and Inclusive Cloud Monitoring and Cost Management … But How? Overwhelmingly, even as enterprises have adopted cloud computing and are expanding to multi-cloud computing, IT leaders remain concerned about how to monitor, manage and control costs across hybrid and multi-cloud deployments. It’s clear that traditional IT monitoring and management approaches, designed after all for on-premises data centers, are falling short in this new hybrid and dynamic environment.
Serveless Architectures brings the ability to independently scale, deploy and heal based on workloads and move away from monolithic designs. From the front-end, middle-ware and back-end layers, serverless workloads potentially have a larger security risk surface due to the many moving pieces. This talk will focus on key areas to consider for securing end to end, from dev to prod. We will discuss patterns for end to end TLS, session management, scaling to absorb attacks and mitigation techniques.
We are seeing a major migration of enterprises applications to the cloud. As cloud and business use of real time applications accelerate, legacy networks are no longer able to architecturally support cloud adoption and deliver the performance and security required by highly distributed enterprises. These outdated solutions have become more costly and complicated to implement, install, manage, and maintain.SD-WAN offers unlimited capabilities for accessing the benefits of the cloud and Internet. SD-WAN helps enterprises to take advantage of the exploding landscape of cloud applications and services, due to its unique capability to support all things cloud related.