Here’s a scenario that might feel painfully familiar. Your marketing department captures customer leads, and passes them to the sales department. Marketing’s success is measured in part on the number and size of deals that result. But a squabble breaks out over how the sales department handles, nurtures, and attributes those conversions. Result: Neither department really wants to share their data.
It’s hard to overstate how challenging software development is today. The market for web and mobile applications is more competitive than ever. Customers expect their applications to deliver a flawless, beautiful, and intuitive experience every time. Hiring and retaining high-quality software developers and engineers feels next to impossible given the low unemployment rate for IT professionals (just under 2% in the U.S. according to the U.S. Bureau of Labor Statistics).
On Nov 13, 2019 Github made it’s CI/CD solution GitHub Actions generally available to the world. Since then tens of thousands of shared workflows have been published. It is now the default for most Github projects given how easy it is to integrate with an existing repo. Projects of all sizes have adopted it from our homegrown Terraform module to the Docker Cli. This is why at Speedscale we’ve published a template for how to use Speedscale in conjunction with GitHub Actions.
It's not for nothing that Kubernetes is a popular choice for running a cloud workload. It can be a powerful tool for orchestrating your applications. However, one thing that can often be a last thought in a production workflow, or maybe forgotten altogether, is load testing. It might be tempting to think that Kubernetes can handle it all. In many cases it can, but it's always smart to know how much your application can take. After reading this article, you'll be equipped to determine which tools would best serve you for load testing your application.
Data lakes serve as central destinations for business data and offer users a platform to guide business decisions.
