Daily Wrap Up – April 20, 2023 (#072)

I’ve got a lot of things for you to pick from today! I read (or watched) good items related to AI misconceptions, cloud cost optimization, and communicating tough decisions.

[article] Istio as a Platform for Running Microservices. Video and transcript of a talk on Istio as a service mesh product that adds value to your distributed systems.

[blog] Announcing Google DeepMind. We’re not messing around! This combination of teams is one to watch. Also see Sundar’s post about it.

[article] How to Communicate a Tough Decision to Your Team. You can tell a lot (everything?) about a manager by how they handle tough circumstances. Good advice in this article.

[blog] The Prompt: Debunking five generative AI misconceptions. The AI hype-meter is off the charts right now, so get a bit of grounding by reading this useful post.

[article] Kubernetes Security in 2023: Adoption Soars, Security Lags. If you don’t get ops and security right, you’ll never get past the POC stage with modern tech and architectures.

[blog] Stack Overflow embraces generative AI as developers voice concerns. Stack Overflow represents a huge source of tech knowledge that will power many generative AI models. How do they stay relevant and interesting to devs who might switch to other experiences to get answers?

[blog] Framing up FinOps: How to optimize your cloud costs on Google Cloud. Good framing, along with specific tips.

[blog] 4 cloud cost optimization strategies with Microsoft Azure. Valid cost management advice in this post as well.

[youtube-video] Inside Envoy: The Proxy for the Future. Spend a night at the movies by watching this ~30 minute video about the Envoy proxy. It’s more interesting than it sounds!

[blog] What’s Different About Today’s AI? This is one of the more insightful things I’ve seen related to this wave of AI, and that’s saying a lot! Is this adoption curve driven by a user experience evolution as much as technological one?

[blog] When Is Microservices Architecture Worth It? Not breaking a ton of new ground here, but always good to get a reminder about when (or when not) to use a particular architecture pattern.

[blog] Scaling a Monolith with 5 Different Patterns. Related to the prior post, there are cases where a monolith is ok, or you can scale the current architecture without major refactoring. Here are a few patterns to consider.


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 )

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.