Operations | Monitoring | ITSM | DevOps | Cloud

Microservices architecture is getting adopted extensively in the world of distributed applications. There are various options and frameworks available to implement the Micro Services, e.g., Azure Service Fabric, Azure Kubernetes Services, Azure Functions, etc. The hottest trend these days seems to be serverless. The promise of consumption-based pricing, where you only pay for what you use and nothing more, is enticing.

System downtime is a part of the IT infrastructure. Very often, the system goes into a snag or downtime involving an unplanned stoppage of operations. More often than not, this is a direct result of a lack of appropriate maintenance. However, the smallest of downtimes can lead to heavy business and financial losses within the company. Hence, the idea is to conduct maintenance tasks and operate the IT infrastructure to reduce potential downtimes.

In keeping with our vision of offering a universal feature set across all the package formats we support, we are delighted to announce that we are now offering configurable upstream proxying and caching support for RedHat packages. As we touched upon when announcing the same for Debian and Maven packages, there are a lot of reasons why this is a really good thing, so instead of going over those again, let’s jump straight into how you can set this up in you Cloudsmith repository.

As the world collectively evaluates the return to work and shift to remote operations, digitally transformed enterprises are coming out faring better in this transition. This shift is aided by the work developers are putting in to create applications that better their organizations, and they need to continually adopt modern DevOps best practices to increase application delivery velocity and quality in order to stay nimble.

Have you noticed recently that your AWS Lambda invocation requests are getting throttled? If so, your Lambda functions are probably not running as designed. Let’s examine the possible causes and solutions to poor Lambda performance.

Do you need to integrate a new company in with your existing employer and therefore in to your already provisioned Azure AD tenant. Or perhaps just need to share your tenancy and office 365 services with more than one company, then you could find yourself in a position where you need to sync users from another domain and have already configured AD Connect, well there is a way to add the second domain to your current Azure tenancy, so you can sync those users from the second domain.