The first half of 2020 has turned “business as usual” on its head, underscoring the criticality of both the cloud and cloud cost management in our digital era. For the last 16 years, the world of IT has been gradually moving from on-premise data centers to the public cloud, with SMBs and enterprises alike, drawn to the promise of scalability and potential cost-savings.
Across the world, many network operators, fiber network wholesalers, municipalities, and local authorities are in a race to put fiber in the ground. New techniques and specialized tools have reduced the time it takes to deploy optical fiber and increased the amount of fiber held in a single duct, this makes the dream of providing fiber to every premise a cost-effective reality.
GitOps has been around for quite some time now and continues to pique developer interest when it comes to driving operation tools. This technology-agnostic model embraces operations best practices, using Git as a single source of truth for declarative infrastructure and applications.The term GitOps for this operating model is now an industry standard and has rapidly made a name for itself among the Kubernetes and cloud-native communities.
The pandemic has heightened IT leaders’ need for efficiency in managing what we’re seeing more and more as a hybrid cloud world. We recently polled IT leaders across the US and EMEA on their current challenges, changes, and goals around hybrid cloud deployments, infrastructure visibility, use of AI/ML, and more.
TL;DR note: if you want the bzip2 -9 version of this post, scroll down to the very last section for some quick pointers. If you want to learn a bit about Linux system logs, please continue, as we’ll talk about all these and more.
Lambda is an AWS service that allows you to run your code completely in the cloud without the need for on-prem servers. As the world has shifted away from on-prem and toward serverless computing, Lambda has grown in popularity: 1700 companies report using Lambda as part of their data infrastructure in StackShare.
Marc Andreessen famously said, “Software is eating the world.” Dr. Steve Willmott subsequently retorted, “APIs are eating software.” This is because API based architectures are enabling companies to get away from monolithic architectures and move to microservices. Innovative, disruptive companies like Netflix, Airbnb, Uber, Square, and Slack all build their infrastructure and technology using APIs.
Usually, organizations use an internal network to prevent unauthorized people from connecting to their private network. By using their own network infrastructure and connectivity, they can maintain their desirable level of security for their data. But it would be convenient for users to connect to that private network while they are away from the office through their own internet connection.
Managing dependencies is a fact of life in modern software development. But at Cloudsmith, we’re focused on ensuring that the process is as painless as possible. To that end, we’re delighted to announce both upstream proxying and caching for Maven packages. Together they mean simpler, more reliable integration of third party packages into the development process. Better software, faster.
In the first article, we talked about CI or Continuous Integration. This post looks at the second half of the CI/CD acronym, Continuous Delivery. Continuous delivery takes the build originating in the CI process and puts it into an acceptance environment for further evaluation before promoting the code to production (the released version). To back up a moment, CI is the planning, coding, testing, and building of software in a rapidly repeating process.
