When people watch videos online, their video quality is mostly dependent on their internet connection. Faster internet means better video. This is great for people with consistent high-speed connections, but those folks are still in the minority. Instead, most people simply end up suffering through low quality videos; we accept it as a sad fact of life—like morning traffic or melting ice caps. It sucks, but it's going to happen. However, at least for video quality, there might be a better way. Enter Per-Title Encoding.
If you work in Application Security you’ve probably already heard about OWASP and the OWASP Top 10, which lists the Top 10 most critical vulnerabilities in web applications. Its latest version was released in 2017 after some changes and reviews from the community. But when it comes to teaching the developers about the basic principles on how to write secure code, there is another OWASP project that is the best option: the OWASP Top 10 Proactive Controls.
The fact that SOLID is being criticized isn’t a bad thing. The problem is that I don’t think the arguments against it are really that good. There’s some valid criticism, but it seems that a large portion of it comes from some misunderstanding of the principles. Some people even read obscure agendas in them. This post is meant to investigate some of the more common criticisms of the SOLID principles, offering my take on why I believe they’re not quite justified.
How does Stack Overflow keep pagination fast? Caching popular queries entirely and paginating in the application code? Using some database black magic?
Over the next few years, companies will be moving to the cloud for the speed in which services can be deployed, the ability to scale services when demand changes, and potential cost savings from eliminating data centers. Many current on-premises applications are backed by a SQL Server database with batch jobs running on SQL Server Agent. Microsoft’s Azure SQL database service does not have a native job scheduler. How can we schedule Transaction SQL (T-SQL) statements to run on a scheduled basis?
Indexes play an important role in improving performance of queries, by allowing SQL Server to scan a limited number of rows. When queries involve tables from the same database, SQL Server can choose the best indexes available. Can SQL Server take advantage of indexes when querying multiple databases? In this tip, I'll explore the performance of cross-database queries in Azure.