Operations | Monitoring | ITSM | DevOps | Cloud

Now that you’re invited, here’s the lowdown: Starting this Wednesday, you get the unique chance to attend four weeks of live working sessions with some of the top minds in serverless. They’ll prepare you to build production-ready serverless applications with the best practices of AWS top-of-mind. Along the way, you’ll get the chance to earn awesome prizes as you unlock milestones like deploying a stack and finishing your app.

Incidents happen all the time because of bad code deploys. You write some code that passes code review, it then is automatically shipped to production after a test suite passes, and BAM, an outage happens. This fairly common occurrence has ways to prevent it entirely. Using some simple ideas we can defend ourselves from the hidden mistakes that code reviews and chaos engineering sometimes won’t catch.

Starting today, any developer can locally debug and develop any Lambda function, in any language or framework, against live cloud resources with any IDE, for free. You don’t even need a Stackery account. This capability can be obtained by installing the Stackery CLI either automatically via the Stackery VS Code Serverless Tools Plug-In or manually alongside any IDE.

Kubernetes is an open-source container-orchestration system for automating application deployment, scaling, and management. It was originally designed by Google, and is now maintained by the Cloud Native Computing Foundation.

The last decade has ushered in a golden era of software engineering. The rise of cloud computing freed companies from managing their own data centers and provided on-demand scaling. These services allow for provisioning servers on the fly using configuration and code. Treating that task as just another type of software development led to the advent of DevOps.

If you’re a CFO or finance leader at a company that uses public cloud services like AWS, chances are you’ve had a bill cross your desk that may seem confusing. You or your team of financial analysts may have frequent conversations with engineering about how AWS services are allocated across different engineering initiatives.