Joao Grassi — a .NET developer, front-end hobbyist, and friend of Sentry — likes .NET very much. So do we. With the help of one of Sentry’s top 10 SDKs, .NET developer teams process roughly half a billion .NET events every month. In this post, we strive for app security with Azure Key Vault and Sentry. By now, it’s not big news that ASP.NET Core is the future of web development with .NET.
By Des Nnochiri Budgetary constraints are often a key factor in determining how an organization sets up its IT infrastructure. The hybrid cloud typically leads to cost savings of between 5% and 30% for enterprises that make the transition. Besides the monetary aspects, performance benefits and easier administration also inspire many organizations to consider moving to a hybrid cloud.
Serverless has become something of a buzzword lately - but it’s much more than a trend. Its benefits have gained the attention of professionals and amateurs in the tech industry, mainly due to how much cloud vendors have raved about the design. For mid-sized ventures, the idea of serverless is exceptionally appealing, for those looking for budget-friendly, but useful pieces of technology. It’s genuinely breaking the ground and is sure to make even more moves in the tech industry.
Cloud infrastructure refers to both hardware and software components—ranging from servers to storage to networking and virtualization software—that are required to support cloud computing. Thus, cloud infrastructure optimization refers to optimizing these components for: efficiency, performance, and cost.
Some say you have to move all of your server infrastructure into the cloud. Others counter that you should keep your data safe and secure in your own datacenter. And then there are many people in between who use cloud services as an addition to their self-hosted servers. In fact, there’s no right or wrong, because as always in IT: It depends. We at Icinga always try to find a way to make everyone happy with their monitoring – be it in the cloud or on premise.
A common pattern in serverless architecture is to have a queue before a function. This is great because you can create a second queue for all of the messages that failed in the function execution (or, if we want to put it in terms that don’t sound like we’re aggressively shaming them, we can classify them as having “encountered an error at some point”). This second queue is known as a “dead letter queue” or DLQ for short.
One of the most common reasons for system failures is changes to the underlying infrastructure. Amazon CloudTrail does a great job of recording when actions are taken but a lot of organizations don’t take advantage of it. FireHydrant now includes this data, giving you visibility into changes to your infrastructure while you’re investigating an incident.
Cloud spend optimization is a challenging endeavor for most companies. The major reason for this is that most don’t have sufficient visibility into their live cloud costs, so they can’t tie day-to-day decision-making to those staggering AWS bills that arrive at the end of each month (way too late to make meaningful changes).
AWS Lambda has gained good traction for building applications on AWS. But, is it really the best fit for all use cases? Since its introduction in 2014, Lambda has seen enthusiastic adoption – by startups and enterprises alike. There is no doubt that it marks a significant evolution in cloud computing, leveraging the possibilities of the cloud to offer distinct advantages over a more traditional model such as EC2.
