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.

Universities generate enormous amounts of data that are used for a plethora of reasons, including planning and management of revenue and donations, fees, growth and development; institutional reporting to the government; and tracking progress towards achieving goals.

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.

ELK is the acronym for three open source projects where E stands for Elasticsearch, L stands for Logstash and K stands for Kibana. ELK is a robust solution for log management and data analysis. In this blog, I am going to show you how to configure ELK while working with Talend Cloud. The blog will focus on Loading Streaming Data into Amazon ES from Amazon S3.