A coming Data Darkage is on its way, where we’re watching Reddit, Twitter and other companies take what used to be publicly available information and put it behind a paywall or gate.
Because of the way large language models are using this data and the value of the data, we are expecting to see that trend accelerate. This will have profound implications for how we think of, share, and use data in the coming years.
Organizations take a risk when they get locked into a vendor. In today’s episode, we talk a lot about the risks of lock in, both in general and in the context of Oracle.
That discussion takes us into a question of insurance, and if insurance policies could ultimately drive people to reduce lock in exposure. This was a fascinating discussion, not only about lock in but about what would drive organizations to fix their lock in problems.
In the Cloud 2030 Podcast episode on March 31st, Rob Hirschfeld discusses the intricate aspects of vendor lock-in, focusing on the risks associated with relying on a single provider, such as an authentication service like Okta. The conversation delves into the challenges of migrating away from tightly integrated platforms and emphasizes the importance of assessing and mitigating lock-in risks. The broader theme within Cloud 2030 discussions seems to revolve around identifying and understanding various risk factors in building complex infrastructures, aiming to drive market dynamics by addressing and managing these risks. To explore this insightful discussion further, check out the full episode on March 31st at the2030.cloud and become part of these engaging conversations.
The Okta hack highlights the value versus complexity trade off. In today’s episode, we ask if the complexity of using single sign on is the right move in this context. We also think about how to deal with these interconnected systems that have high degrees of complexity.
We also discussed API design, and whether or not we should have more rigid or flexible APIs. You can’t remove complexity from the system, but you can hide it. The structure of APIs will push complexity into either the users’ realm or the operators’ realm.
In the Cloud 2030 Podcast on March 24th, Rob Hirschfeld delves into the complex relationship between complexity, value, and immutability in system design, particularly focusing on API interfaces. He emphasizes the trade-offs involved in exposing options to users, providing flexibility but potentially increasing complexity. The discussion highlights the practicality of using immutability and templates to control API complexity, acknowledging the challenges of finding the right balance and the importance of transparency in decision-making. To explore these insights further, listen to the full episode on March 24th at the2030.cloud and participate in these open conversations.
During this 20 minute check-in we dive security and SaaS infrastructure.
Can we protect the secrets that people are trusting to SaaS providers to store for us? The topic was inspired by the Twitch leak where a lot of sensitive information was exposed exposed to the public. That comes on the heels of all sorts of other leaks, compromises and down time on systems.
Overall, it seems like bad news is coming faster and faster for operators. The fundamental question is NOT can we trust a SaaS provider to secure information. We know the answer is NO. But what to do about it?
