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.

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.

If there’s no customer, there’s no job. In a competitive marketplace, every site element matters from the functionality of your service to your UI; your documentation to your marketing. Your SLA should mirror that structure. Building a strong customer experience is about consistency on every level. The key is visibility, offering all the verification your customers need with an intuitive click of the mouse.

There are many articles and videos about practicing Continuous Delivery (CD) with applications, but not nearly as many for infrastructure. The same can be said for GitOps applied to infrastructure. That is a bit strange given that applications and infrastructure are almost the same today. Both are defined as code, and everyone stores code in Git repositories. Hence, GitOps is just as good of a fit for infrastructure as for anything else.

In today’s world, with many microservices fuelling hundreds of components, the failure of just one piece can cause a crash for the whole system. For example, a lack of memory in one component can cause a database failure. This database failure could be the reason for authentication problems for particular users, causing those users to not be able to login. And of course, finding the core problem manually can be complex and time-consuming.

As Kubernetes is eating the world, discover an alternative certified Kubernetes offering called K3s, made by the wizards at Rancher. K3s is gaining a lot of interest in the community for its easy deployment, low footprint binary, and its ability to be used for specific use cases that the full Kubernetes may be too advanced for. K3s is a fully CNCF (Cloud Native Computing Foundation) certified Kubernetes offering.

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!

“Gartner predicts that by 2022, more than 75% of global organizations will be running containerized applications in production.”