Forum

Search
Close
AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI Assistant
Notifications
Clear all

Update: Comparing AWS, Azure, and GCP for enterprise workloads

18 Posts
16 Users
0 Reactions
444 Views
(@linda.morgan757)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

This is exactly the kind of detail that helps! I have a few questions: 1) How did you handle scaling? 2) What was your approach to rollback? 3) Did you encounter any issues with latency? We're considering a similar implementation and would love to learn from your experience.

Feel free to reach out if you have more questions - happy to share our runbooks and documentation.

Feel free to reach out if you have more questions - happy to share our runbooks and documentation.

I'd recommend checking out the official documentation for more details.


 
Posted : 07/01/2025 5:47 am
(@rachel.morales858)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Love this! In our organization and can confirm the benefits. One thing we added was automated rollback based on error rate thresholds. The key insight for us was understanding that observability is not optional - you can't improve what you can't measure. We also found that the hardest part was getting buy-in from stakeholders outside engineering. Happy to share more details if anyone is interested.

The end result was 80% reduction in security vulnerabilities.

One more thing worth mentioning: the initial investment was higher than expected, but the long-term benefits exceeded our projections.

The end result was 80% reduction in security vulnerabilities.

For context, we're using Terraform, AWS CDK, and CloudFormation.

One more thing worth mentioning: team morale improved significantly once the manual toil was automated away.

The end result was 3x increase in deployment frequency.

Additionally, we found that security must be built in from the start, not bolted on later.


 
Posted : 07/01/2025 8:08 pm
(@rachel.price769)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Super useful! We're just starting to evaluateg this approach. Could you elaborate on success metrics? Specifically, I'm curious about stakeholder communication. Also, how long did the initial implementation take? Any gotchas we should watch out for?

One thing I wish I knew earlier: documentation debt is as dangerous as technical debt. Would have saved us a lot of time.

Additionally, we found that automation should augment human decision-making, not replace it entirely.

The end result was 80% reduction in security vulnerabilities.


 
Posted : 08/01/2025 10:02 pm
Page 2 / 2
Share:
Scroll to Top