Daily Wrap Up – March 2, 2023 (#039)

This week is flying by so far. On this Thursday evening, check out some good reads on product discovery, choosing when to build or buy, and whether we’re asking too much of developers.

[blog] Build vs Buy: Buy when possible, build when necessary. How do you decide whether to buy a product or build something yourself? This enterprise architecture team tries to codify the decision criteria.

[blog] Spring Cloud GCP 4.0 is out! Let’s upgrade the sample Bank of Anthos app. I write more Go code nowadays than Java, but I’ll dust off my Spring skills to try out our updated components for interacting with Google Cloud services from Spring Boot apps.

[blog] Insights from the CDH Benchmark Survey: How Are Teams Adopting Discovery Habits? If you’ve been thinking about how to build better products that solve real needs, you might have started exploring more product discovery techniques. Check out results from this unique survey to see how others are doing it.

[blog] Centralised audit logs in Google Cloud, the new way: Log Analytics. Instead of shoving your logs into an analytics engine for deeper analysis—and maintaining the pipelines to keep the data flowing—it’d be nice if your logs were natively stored in an analytics engine. They are now, in BigQuery.

[article] How Spotify Adopted and Outsourced Its Platform Mindset. Good look at what it means—culturally and technologically—to deliver platform services to internal teams.

[blog] The Case For Go Backends. To me, most programming languages are “good enough” for a variety of things. You can do backends in Go, Rust, C#, or whatever. But I’ve enjoyed learning and using Go more and more, and find it suitable for a lot of scenarios.

[report] State of Cloud Threat Detection and Response Report. Here’s the direct link to a PDF report that summarizes survey results from 400 security leaders. Check it out for a comparison between cloud and on-premises regarding threat detection and response.

[blog] The side effect of increasing developer responsibility. It seems clear that there’s too much responsibility on the shoulders of developers. “Shift left” even more things? Jeremy’s post highlights the challenge and the search for something better.

[blog] AWS is Asleep at the Lambda Wheel. With serverless computing, vendors took on a responsibility to keep runtimes up to date. That’s the deal. AWS is struggling here a bit.


Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:

Author: Richard Seroter

Richard Seroter is Director of Developer Relations and Outbound Product Management at Google Cloud. He’s also an instructor at Pluralsight, a frequent public speaker, the author of multiple books on software design and development, and a former InfoQ.com editor plus former 12-time Microsoft MVP for cloud. As Director of Developer Relations and Outbound Product Management, Richard leads an organization of Google Cloud developer advocates, engineers, platform builders, and outbound product managers that help customers find success in their cloud journey. Richard maintains a regularly updated blog on topics of architecture and solution design and can be found on Twitter as @rseroter.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.