Twitter | Search | |
Libby Clark
Editorial Director at The New Stack. News, podcasts, e-books, and more content for devs. FOSS lover.
5,095
Tweets
1,918
Following
3,184
Followers
Tweets
Libby Clark Jan 15
"All modern developers are turning into distributed systems developers" and that requires understanding failure modes and network partitions, says via
Reply Retweet Like
Libby Clark Jan 11
Replying to @SonyaKoptyev
- sorry for the misspelling!
Reply Retweet Like
Libby Clark Jan 11
I was shocked to learn in my interview w/ @sonyakopyev that most large orgs have no idea what cloud services they're using. And to Sonya's point: If you don't know they exist, how can you secure them?
Reply Retweet Like
Libby Clark Dec 14
What is Grafana Loki? We dive into the open source log aggregation tool that took Hacker News and KubeCon by storm this week...
Reply Retweet Like
Libby Clark Dec 13
Loved meeting Athena at the booth
Reply Retweet Like
Libby Clark Dec 13
Replying to @lenadroid
Great talk, yesterday! I learned a lot. My biggest takeaway was engineers need to understand CRDs to understand how to run ML workloads on K8s.
Reply Retweet Like
Libby Clark Dec 12
I've seen talks from IBM, Alibaba and now Cloudera about their ML platforms on K8s and all are emphasizing the ability to manage and monitor GPU vs CPU for various workloads. Seems cool but is this something data scientists want to manage?
Reply Retweet Like
Libby Clark retweeted
Joab Jackson Dec 12
The Oracle Cloud Native Framework includes support for many open source cloud native infrastructure technologies, including Oracle Functions, a new serverless cloud service based on the open source Fn Project.
Reply Retweet Like
Libby Clark Dec 12
Some people say K8s is going to kill Hadoop, but it's an AND not an OR approach to machine learning for enterprise users.
Reply Retweet Like
Libby Clark Dec 12
The Apache and Hadoop ecosystem hasn’t had much overlap with K8s in the past, but that is changing says
Reply Retweet Like
Libby Clark Dec 12
Gartner analyst Simon Richard is interested in service mesh across clouds pancakes
Reply Retweet Like
Libby Clark Dec 12
One key pain point of devs is making sure they develop with security in mind. But putting it in your code creates operational problems. That should be part of the platform and Google is working on building that into Istio pancakes
Reply Retweet Like
Libby Clark Dec 12
The next step for Istio needs to be getting it production ready and then figuring out enterprise user needs so it improves the developer workflow via Pere Monclus VMware pancakes
Reply Retweet Like
Libby Clark Dec 12
What are the next features in Istio? It’s a rich feature set for a 1.0 project. The focus needs to be on adoption says IBM’s Jason McGee pancakes
Reply Retweet Like
Libby Clark Dec 12
Is Istio going the direction of Kubernetes? At some point Google will consider donating the project to CNCF via IBM and Google. pancakes
Reply Retweet Like
Libby Clark Dec 12
Let’s not spend decades trying to create competing versions of service mesh. Let’s choose one and all advance together. Via Google’s Jennifer Lin pancakes
Reply Retweet Like
Libby Clark Dec 12
It’s not necessarily about when to adopt service mesh as a whole but what portion of the Istio capability to adopt and when. Via IBM’s Jason McGee pancakes
Reply Retweet Like
Libby Clark Dec 12
The 1st thing MasterCard solved with service mesh was making sure the network was available globally all the time and second was gaining visibility into dependent services via Ken Owens pancake breakfast
Reply Retweet Like
Libby Clark Dec 12
“There will be many service meshes” via Jennifer Lin at Google pancakes
Reply Retweet Like
Libby Clark Dec 11
Love to get listeners on the podcast! It makes TNS complete. :)
Reply Retweet Like