Times change and so we do. If you are one of those who pay attention to their surroundings, who does not miss anything, you surely realized that our website has since a few days ago a mysterious new tab in its browsing menu that corresponds to the acronym “SaaS”.
We are moving our Apache 2.0-licensed source code in Elasticsearch and Kibana to be dual licensed under Server Side Public License (SSPL) and the Elastic License, giving users the choice of which license to apply. This license change ensures our community and customers have free and open access to use, modify, redistribute, and collaborate on the code.
It’s been said that the devil is in the details. Well, along the same lines — and as we all know from miserable experience — when it comes to guarantees, the devil is in the small print. And there’s no better (or worse) example of this than with respect to the gleaming, confidence-inspiring claim by web hosts that they deliver 100% guaranteed uptime. Except, well, they don’t.
One problem that pops up quite frequently when people try to build serverless applications with AWS API Gateway and AWS Lambda is Execution failed due to configuration error: Malformed Lambda proxy response. There is nothing worse than generic error messages that don’t tell you anything you need to fix the problem, right? And AWS isn’t particularly known for its error message design, if you can even call it that, let alone for giving you the means of fixing the problem.
Shipa’s application management framework, integrated into OKE, provides an out-of-the-box way for organizations to build, deploy and operate the full life-cycle of Kubernetes applications. With Shipa and OKE, organizations can make up for lost time and start getting value out of Kubernetes immediately. In this webcast, you will learn how Shipa and OKE.
Machine learning (ML) and analytics make data actionable. Without it, data remains an untapped resource until a person (or an intelligent algorithm) analyzes that data to find insights relevant to addressing a business problem. For example, amidst a network outage crisis a historical database of network log records is useless without analysis. Resolving the issue requires an analyst to search the database, apply application logic, and manually identify the triggering series of events.
At Cloudsmith, we are proud of our partnership network. We work hard to collaborate and integrate with the best DevOps tools available. Building performant, modern workflows requires frictionless integrations between tooling. Integrating Cloudsmith repositories with your CI/CD processes facilitates rapid development. Build, test, and deploy/distribute your software in repeatable, performant ways.
A lot of very good writing from some reliable commentators has been suggesting that organizations have been forced into a digital-first environment. Covid has been the enforcer and business and public sector alike have adapted to having a distributed workforce by putting the infrastructure in where there were gaps. This is OK as far as it goes but it’s not quite right. The best organizations have not gone ‘digital-first’.
