START with a Monolith, NOT Microservices
Start with a Monolith! Why? Finding boundaries is a difficult thing to do and even harder to get right. Having to define those boundaries up-front for a microservices architecture is a recipe for additional and unneeded complexity. If you develop a loosely Coupled Monolith by applying the same principles when developing Microservices, you'll be in a better place to refactor and change your boundaries as you gain insights.
🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1
💥 Join this channel to get access to perks!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join
👍 THANK YOU for supporting my channel!
📝 Blog: https://codeopinion.com
0:00 Intro
1:02 Finding Boundaries
2:20 Monolith
4:30 Database Coupling
5:15 Messaging between Boundaries
6:20 Refactoring to Insights
CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion
#softwarearchitecture #microservices #monolith
Видео START with a Monolith, NOT Microservices канала CodeOpinion
🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1
💥 Join this channel to get access to perks!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join
👍 THANK YOU for supporting my channel!
📝 Blog: https://codeopinion.com
0:00 Intro
1:02 Finding Boundaries
2:20 Monolith
4:30 Database Coupling
5:15 Messaging between Boundaries
6:20 Refactoring to Insights
CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion
#softwarearchitecture #microservices #monolith
Видео START with a Monolith, NOT Microservices канала CodeOpinion
Показать
Комментарии отсутствуют
Информация о видео
Другие видео канала
![Asynchronous Messaging in a Loosely Coupled Monolith](https://i.ytimg.com/vi/Qi6TaIYprqc/default.jpg)
![Avoiding a Big Ball of Mud! Coupling in a Monolith](https://i.ytimg.com/vi/MLjjWkN44q4/default.jpg)
![Service Oriented Architecture: Commands & Events Explained!](https://i.ytimg.com/vi/oJiUjiWeesQ/default.jpg)
![MediatR: Why should you use it?](https://i.ytimg.com/vi/yhpTZDavtsY/default.jpg)
![Monoliths Mystery Explained in Telugu | Monolith Mystery Telugu](https://i.ytimg.com/vi/oUbJaeAzO50/default.jpg)
![Splitting up a Monolith to (micro)Services](https://i.ytimg.com/vi/Inscvakv5XI/default.jpg)
![Organize Code by Feature | Vertical Slices](https://i.ytimg.com/vi/PRns0rqPonA/default.jpg)
![★ What are microservices?](https://i.ytimg.com/vi/PY9xSykods4/default.jpg)
![CQRS Myths | 3 Most Common Misconceptions](https://i.ytimg.com/vi/O9qpcZt6jW0/default.jpg)
![Scaling Monolithic Applications](https://i.ytimg.com/vi/qZB_uGuWvUI/default.jpg)
![Hangfire + MediatR = Message Dispatcher](https://i.ytimg.com/vi/ngeEYUy9hI8/default.jpg)
![Handling Duplicate Messages (Idempotent Consumers)](https://i.ytimg.com/vi/xeBY8fCWfvU/default.jpg)
![Thin or Fat Events? Are your boundaries right?](https://i.ytimg.com/vi/vDtK-ccQWkw/default.jpg)
![Monolithic vs Microservice Architecture Debate](https://i.ytimg.com/vi/RJkn9VHM7lc/default.jpg)
![Complexity of Caching: Strategy, Invalidation & Fallbacks](https://i.ytimg.com/vi/Cx8ONrUq4a4/default.jpg)
![Talking C# Performance with Steve Gordon | Guest Series](https://i.ytimg.com/vi/6rc-ErztbCs/default.jpg)
![Creating a Loosely Coupled Monolith](https://i.ytimg.com/vi/48C-RsEu0BQ/default.jpg)
![Solution & Project Structure of a Loosely Coupled Monolith](https://i.ytimg.com/vi/-1DU9c95ERs/default.jpg)
![Reliably Save State & Publish Events (Outbox Pattern)](https://i.ytimg.com/vi/u8fOnxAxKHk/default.jpg)
![GOTO 2014 • Microservices • Martin Fowler](https://i.ytimg.com/vi/wgdBVIX9ifA/default.jpg)