Check out the full version on our YouTube channel now! #GOTOcon #SoftwareArchitecture #MasterSoftwareArchitecture #SolutionArchitecture #Microservices #ModularMonolith #Complexity #Simplicity #Programming #MaciejJedrzejewski #SoftwareEngineering #TodayInTech #ViralProgrammingShorts #Viral #ViralShorts #TodayInTech #GOTO

Microservices, Kubernetes, Modular Monoliths, “best practices”...What if they’re just opinions, not truths? 👀
Maciej “MJ” Jedrzejewski breaks down why most teams overengineer too early — and what actually matters: building for now, not some imaginary future.

Full version available here:
https://youtu.be/ZCrCqbblXjk

Maciej «MJ» Jedrzejewski - Tech Agnostic Architect & Author of “Master Software Architecture” @learnsoftwarearchitecture 

RECOMMENDED BOOKS
Maciej «MJ» Jedrzejewski • Master Software Architecture • https://leanpub.com/master-software-architecture
Gregor Hohpe • Platform Strategy • https://amzn.to/4cxfYdb
Gregor Hohpe • The Software Architect Elevator • https://amzn.to/3F6d2ax

CHANNEL MEMBERSHIP BONUS
Join this channel to get early access to videos & other perks:
https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join

Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at https://gotopia.tech
Sign up for updates and specials at https://gotopia.tech/newsletter

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

GOTO's resource offers insights, tutorials, and resources for software developers, architects, and technology leaders. Readers can learn about emerging technologies, industry trends, and best practices for software development. With articles, talks, and workshops, GOTO provides  guidance and expertise for staying ahead in the ever-evolving world of technology.

GOTO Conferences

A short opinion piece arguing that software developers over-engineer systems by blindly following architectural 'best practices' like microservices, Kubernetes, or modular monoliths without considering their actual current needs. The core message: stop building for hypothetical future scale and instead architect for what you need right now. Complexity should be introduced only when it becomes a real, present problem — not preemptively.

Built for Scale… with 100 Users – Why "Best Practices" Fail You • @learnsoftwarearchitecture