Artwork

Content provided by Artur W., Grzegorz Godlewski, Marek Urbanowicz, and Artur Wolny. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Artur W., Grzegorz Godlewski, Marek Urbanowicz, and Artur Wolny or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

#021: What went wrong with Microservices

36:16
 
Share
 

Manage episode 359064427 series 3310419
Content provided by Artur W., Grzegorz Godlewski, Marek Urbanowicz, and Artur Wolny. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Artur W., Grzegorz Godlewski, Marek Urbanowicz, and Artur Wolny or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

πŸ“š ABOUT THE EPISODE
In the 21th episode Grzegorz Godlewski and Artur Wolny share their negative experiences with implementing Microservices. Three examples of misuse of that useful pattern shows us that even the greatest idea can lead us down the blind alley, when we are narrow-minded about it.
Listen and take conclusions from those lessons that we learned!
πŸ“‘ TOPICS COVERED
πŸ‘‰ Impact of blindly following recommendations: costly premature optimisations.
πŸ‘‰ Thing that might go wrong when you're focused too much on domain assignment of feature and too less on the app maintainability.
πŸ‘‰ How microservice hype-trains and poor organisational decisions lead to project failure.
⌚ TIMELINE
00:00:00 - Intro
00:02:08 - Story #1: Blindly following recommendations.
00:08:22 - Story #2: Too much domain, too little maintainability.
00:14:20 - Story #3: Microservice hype-train.
00:19:15 - Microservices or monolith? Benefits & drawbacks.
00:34:46 - Outro
🀝 CONTACT US / COLLABORATION
If you:
- want to send us your valuable feedback
- you would like to appear on the show as a guest
- you would like to help out the show to grow
- you would like to sponsor the show
Then please contact us via: podcast@artistryofcode.com
You can also check out our website: https://artistryofcode.com
😍 FOLLOW US ON SOCIAL MEDIA
Facebook: https://www.facebook.com/ArtistryOfCode
Twitter: https://twitter.com/ArtistryOfCode
LinkedIn: https://www.linkedin.com/company/artistry-of-code
Reddit: https://www.reddit.com/r/ArtistryOfCode/
Grzegorz Godlewski
LinkedIn: https://www.linkedin.com/in/ggodlewski/
Twitter: https://twitter.com/GGodlewski
Marek Urbanowicz
LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/
Twitter: https://twitter.com/UrbanowiczDev
Artur Wolny
LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/

  continue reading

28 episodes

Artwork
iconShare
 
Manage episode 359064427 series 3310419
Content provided by Artur W., Grzegorz Godlewski, Marek Urbanowicz, and Artur Wolny. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Artur W., Grzegorz Godlewski, Marek Urbanowicz, and Artur Wolny or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

πŸ“š ABOUT THE EPISODE
In the 21th episode Grzegorz Godlewski and Artur Wolny share their negative experiences with implementing Microservices. Three examples of misuse of that useful pattern shows us that even the greatest idea can lead us down the blind alley, when we are narrow-minded about it.
Listen and take conclusions from those lessons that we learned!
πŸ“‘ TOPICS COVERED
πŸ‘‰ Impact of blindly following recommendations: costly premature optimisations.
πŸ‘‰ Thing that might go wrong when you're focused too much on domain assignment of feature and too less on the app maintainability.
πŸ‘‰ How microservice hype-trains and poor organisational decisions lead to project failure.
⌚ TIMELINE
00:00:00 - Intro
00:02:08 - Story #1: Blindly following recommendations.
00:08:22 - Story #2: Too much domain, too little maintainability.
00:14:20 - Story #3: Microservice hype-train.
00:19:15 - Microservices or monolith? Benefits & drawbacks.
00:34:46 - Outro
🀝 CONTACT US / COLLABORATION
If you:
- want to send us your valuable feedback
- you would like to appear on the show as a guest
- you would like to help out the show to grow
- you would like to sponsor the show
Then please contact us via: podcast@artistryofcode.com
You can also check out our website: https://artistryofcode.com
😍 FOLLOW US ON SOCIAL MEDIA
Facebook: https://www.facebook.com/ArtistryOfCode
Twitter: https://twitter.com/ArtistryOfCode
LinkedIn: https://www.linkedin.com/company/artistry-of-code
Reddit: https://www.reddit.com/r/ArtistryOfCode/
Grzegorz Godlewski
LinkedIn: https://www.linkedin.com/in/ggodlewski/
Twitter: https://twitter.com/GGodlewski
Marek Urbanowicz
LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/
Twitter: https://twitter.com/UrbanowiczDev
Artur Wolny
LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/

  continue reading

28 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide