How high-performing teams use automation to focus on work that drives insights and revenue
A step-by-step guide to automate your data pipeline and get back time for high value work.
A step-by-step guide to automate your data pipeline and get back time for high value work.
Editor's note: Today we hear from Dang Nguyen, API Platform Product Owner at Experian, on how the company uses the Apigee API management platform to digitally transform from a traditional credit bureau to a true technology and software provider. Read on to learn how Experian uses APIs to help businesses make smarter decisions and individuals take financial control.
“Quality at Speed” is the new norm in software development. Enterprises are making their moves toward DevOps methodologies and Agile culture to accelerate the delivery speed and ensure product quality. In DevOps, a continuous and automated delivery cycle is the backbone that makes fast and reliable delivery possible. This results in the need for proper continuous integration and continuous delivery (CI/CD) tools.
As outlined in a previous article on security challenges for microservices, DevOps are getting more widely distributed, spread thin, and forced to plan for higher levels of interactivity as well as evolving national security “backdoor” measures. Microservices, born from a still-emerging DevOps laboratory environment, can be deployed anywhere: on-prem, in the public cloud, or a hybrid implementation.
We've received a lot of fantastic feedback from industry analysts about Yellowfin and where we're going as an organization. There are three in particular that have come out recently and made me really proud of what we’ve achieved.
We are excited to announce the release of a new open source project, Kuma – a modern, universal control plane for service mesh! Kuma is based on Envoy, a powerful proxy designed for cloud native applications. Envoy has become the de-facto industry sidecar proxy, with service mesh becoming an important implementation in the cloud native ecosystem as monitoring, security and reliability become increasingly important for microservice applications at scale.
In my experience as a digital consultant for Google Cloud’s Apigee team, I’ve found that when a technology gets classified as “middleware,” it’s often encumbered with a scarlet letter of sorts. Business leaders find it unexciting — so much so that they often resign it to the purview of technology professionals and don’t spare a second thinking about it.
You’ve likely heard of the term CI/CD pipeline. You have probably known about these practices: continuous integration, continuous delivery, and continuous deployment as well. But the uncertainty remains: What are the differences between continuous delivery and continuous deployment? Which one should you apply to your CI/CD pipeline? How are these terms related to one another? How to find out which one suits your team best?
The answer to creating an inclusive data culture is in your hands. At Yellowfin, we firmly believe that organisations are far more successful when all their people engage with data. And whilst this has always been the goal of organisations on their journey to being “data-led”, the reality is most are still a long way off. For this to happen, all decision makers need access to insights, in a way that they can understand, not just the data analysts.