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.

As many on-site organizations scramble to adopt remote work, DevOps teams are turning to messaging and integrated workflows to collaborate effectively. Usual office work practices are changing, and people are having to adapt to a remote-first approach. This demands a change to your company culture, a remote mindset and the tools to deliver it.

The best way to stay out of danger is to keep far away from where danger lurks. But in the internet age, the global network means risk to your systems is from everywhere, at all times. With estimates that worldwide damage from cybercrime will exceed 6 trillion dollars by 2021, many companies choose, or are required by regulations to isolate their most sensitive systems to avoid any type of security breach.

At CloudZero, we talk to leadership teams at SaaS and companies every day. When it comes to individual customer profitability, the vast majority of them fall into two camps: they’re either taking their best guess — or they have no idea. Typically only the largest companies - those with the resources to dedicate a 5-10 person engineering team to calculating cost - have this level of insight. And you can be sure they yield that knowledge to their competitive advantage!

In the previous article, we have created the Continuous Integration (CI) pipeline for a simple Java application. It is now time to start working on the Continuous Deployment (CD) pipeline that will take the Java application and deploy it to AWS. To build the CD pipeline, we will extend the existing AWS Jenkins pipeline. If you have missed the previous article on building a CI pipeline for a Java application using Jenkins, make sure you read that first before continuing.