digitalmarks

[digitalmarks @digitalmarks]

A9: Wherever possible, strongly consider taking a greenfield approach with respect to design and development targeted for multi-cloud deployment. Doing so will instill both benefits and a discipline that will serve your team and your business... #eweekchat https://t.co/TS7szCXb3t

[digitalmarks @digitalmarks]

@JamesMaguire re: edge, absolutely! I consider it an abstraction. #eweekchat https://t.co/ij2aNPWvKX

[digitalmarks @digitalmarks]

A8: The future of multi-cloud is one where more powerful abstractions (e.g. serverless) allow for more sophisticated strategies. As we’ve seen with other tech paradigms the increased sophistication will make it easier for some and more challe... #eweekchat https://t.co/rKxdGcC1GM

[digitalmarks @digitalmarks]

A6: Multi-cloud introduces complexity, and you want to go in with your eyes wide open. If a single provider is meeting your business needs, you should really take the time to weigh your motivations, the perceived benefits, against the complex... #eweekchat https://t.co/tDNfMYJtgQ

[digitalmarks @digitalmarks]

A6: That if you’re not doing multi-cloud, you’re doing something wrong. Not to undermine any of the advantages we’ve been discussing, but if you’re happy with a single provider, that’s OK! #eweekchat https://t.co/PP9rH0C65k

[digitalmarks @digitalmarks]

A5: Designate a group to own strategy and management. At a minimum, task them with instituting controls around performance and spending. Tools, capabilities, and standards are evolving, and this group should regularly evaluate those in conjun... #eweekchat https://t.co/7vUbYKBwum

[digitalmarks @digitalmarks]

A4: Hands down, management and governance. From monitoring spending and performance to data management and DevSecOps. It’s difficult and you need to be intentional. #eweekchat https://t.co/y6Fc3umQR8

[digitalmarks @digitalmarks]

A3: Conversely, companies that embraced multi-cloud with a clear strategy, instituting best practices and controls around the building, managing, and governing their cloud presence, will feel much more comfortable. #eweekchat https://t.co/F1ORFpOovu

[digitalmarks @digitalmarks]

A3: Companies that adopted multi-cloud in silos, where individuals or BU's took advantage of the ease of signing up, end up in a world where individuals view it as a success, while those with a 10k foot view are uncomfortable or confused abou... #eweekchat https://t.co/5iWNFr53o7

[digitalmarks @digitalmarks]

A3: Again, this one varies depending on how a company adopted mutli-cloud, what’s important to them, and how they measure success. #eweekchat https://t.co/y5V2dFeyvn

[digitalmarks @digitalmarks]

A2: I think of multi-cloud as the intersection of strategy and technology. While adoption itself could near full saturation, I don’t believe it will ever “peak” but rather continue to evolve creating new opportunities for us to optimize our o... #eweekchat https://t.co/kYy9rjCrng

[digitalmarks @digitalmarks]

A2: The adoption of multi-cloud is mature. Competition, and the desire for more market share, have driven the evolution of cloud provider infrastructure and capabilities to the point organizations could not ignore the richness of the marketpl... #eweekchat https://t.co/XvnYWzygqA

[digitalmarks @digitalmarks]

A1: The inherent advantage of multi-cloud is aligning your organization's needs with cloud provider strengths, optimizing for what’s most important to you. #eweekchat https://t.co/sdLPHsaPjn

[digitalmarks @digitalmarks]

A1: Motivations for choosing multi-cloud are going to vary. For some it’s a strategy motivated by a desire to align their needs with the strengths of cloud providers, or to optimize cost or performance. For others, it’s a necessity driven by ... #eweekchat https://t.co/fGL5FHPtyB

[digitalmarks @digitalmarks]

@chrispederick Amazon GO sandwich purchase efficiency QC is what’s next

[Laura Thomson @lxt]

These benchmarks on @fastly's Compute@Edge vs Cloudflare workers are seriously flawed.The biggest problem is that they conflate network round trip time with “execution at edge” time. CF is measuring cherry-picked RTT instead of edge compute performance. From their blog:

[Noah Chestnut @noahchestnut]

As of today, you can download @buzzer & watch live NBA 🏀 moments tonight for 🆓*

1. Download the app: https://t.co/B8dssJcXbH
2. Get hyped for tonight's games: @buzzerbeats
3. Hang out in the Discord: https://t.co/bfVSahn410

*for this week - happy League Pass Preview Week 🎉

[digitalmarks @digitalmarks]

@noahchestnut Same, but American Chopper meme.

[digitalmarks @digitalmarks]

@whyisjake Two sides to every story

[digitalmarks @digitalmarks]

@chrispederick @mclaughj Let’s iterate on this. Fail fast and all that. We need a JIRA board ASAP.