There’s no question that engineering teams at innovative tech companies are busy. No matter how successful your company is, there’s always a long backlog of feature enhancements that can make it challenging to focus on other priorities. So, it’s no surprise that one of the most common questions we get from companies that engage with us is “How much of an effort will this be for my engineering team?” The short answer is that you can get value within minutes.

SaaS or Software-as-a-Service make up a growing amount of business-critical functionality. Gone are the days of hosting every single application necessary to run a successful business. Everything from email hosting, financial systems, and human resources functions are all now done on SaaS-hosted platforms. The knowledge that all of this is out of your hands is both freeing and frustrating.

There’s no doubt the cloud is having a big impact on the nature and make-up of SQL Server estates. The 2021 State of Database DevOps report from Redgate, for example, showed that 58% of organizations now use the cloud either wholly or in combination with on-premises servers, compared to 46% in the same report a year earlier.

Azure Service Health continuously notifies you of issues that may affect the availability of your environment, such as service incidents, planned maintenance periods, or regional outages. We’ve recently enhanced our Azure integration to include additional support for monitoring Service Health issues, enabling you to keep tabs on the health of your Azure environment and take proactive measures to mitigate downtime.

If you haven’t signed up for our upcoming April 21 Work Anywhere Webinar with Exoprise and Forrester, now is a good time. The webinar highlights the challenges that businesses face today due to Covid disruption and innovative solutions to mitigate these challenges. Millions of Americans now work from the comfort of their home using Microsoft 365, Teams, Zoom, and other critical SaaS application services for their daily activities.

Your company, your infrastructure, and probably your whole business rely more and more on cloud services to provide services to your clients and your cloud infrastructure is probably a critical asset for your company. At FlashDrive our mission is to offer a simple and reliable way to deploy apps while we take care of the infrastructure and make sure your apps and services are always online and ready to scale on demand.

Today, we’ll cover some of the ways you might find quite useful in your everyday work. We’ll go through some of the logging best practices in AWS Lambda, and we will explain how and why these ways will simplify your AWS Lambda logging. For more information about similar topics, be sure to visit our blog. Let’s start with the basics (and if you have the basics covered, feel free to skip ahead): How does logging work with AWS Lambda?

AWS is one of the primary providers for services that help users deploy and manage their containerized applications on the cloud. Since launching ECS in 2014 and EKS in 2017, AWS has learned a lot about running containers at scale and in production. AWS developed Bottlerocket OS, a new operating system for hosting containers. This OS was specifically designed to address gaps left by the ECS and EKS-optimized AMIs, which are based on operating systems that run traditional software applications.

While architectures and platforms like Kubernetes get a lot of attention in discussions about application modernization, we ignore the data layer at our own risk. How applications and users access data is a concern that gets more important by the day. It’s a trend we’ve seen playing out for a while, as technological concerns around latency and scalability have ceded ground to business-level concerns around compliance, security, and data privacy.