0:00 / 0:00
#softwarearchitecture#microservices#stefantilkov
"Good Enough" Architecture • Stefan Tilkov • GOTO 2019
GOTO Conferences
1M subscribers • 87 videos on Hallway • Conference channel
- Recommended by 3 people: 1 on Lobsters and 2 in engineering communities.
- Presented by Stefan Tilkov, Co-founder & Principal Consultant at INNOQ
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
265K views6 years ago3 recommendations
Software designSoftware architectureSimplicity and complexity
Stefan Tilkov explores how to find the right balance between too much and too little software architecture using real-world examples.
This presentation was recorded at GOTO Berlin 2019. #GOTOcon #GOTOber gotober.com Stefan Tilkov - Co-founder & Principal Consultant at INNOQ ABSTRACT In this session, we’ll take a look at some of the ways we can determine whether the development efforts we’re undertaking suffer from too much or too little focus on architecture. We’ll examine a number of real-world examples that are intended to inspire either admiration or terror, and try to find some recipes of how we can get more of the former and less of the latter in our own [...] Download slides and read the full abstract here: gotober.com/2019/sessions/846/good-enough-architecture RECOMMENDED BOOKS Simon Brown • Software Architecture for Developers Vol. 2 • leanpub.com/visualising-software-architecture Mark Richards & Neal Ford • Fundamentals of Software Architecture • amzn.to/3qmELt7 Gregor Hohpe • The Software Architect Elevator • amzn.to/3tY8evH Michael Keeling • Design It! • amzn.to/37y4OGH George Fairbanks • Just Enough Software Architecture • amzn.to/3bbjqg3 Nick Rozanski & Eoin Woods • Software Systems Architecture • amzn.to/3ajYjsv Peter Coad, Eric Lefebvre & Jeff de Luca • Java Modeling In Color With UML • amzn.to/3bVDTHd Eric Evans • Domain-Driven Design • amzn.to/3tnGhwm Grady Booch, James Rumbaugh & Ivar Jacobson • The Unified Modeling Language Reference Manual • amzn.to/2OA1Qv1 twitter.com/GOTOcon linkedin.com/company/goto- instagram.com/goto_con facebook.com/GOTOConferences #SoftwareArchitecture #Backend #StefanTilkov CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket at gotopia.tech Sign up for updates and specials at gotopia.tech/newsletter SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily. youtube.com/user/GotoConferences/?sub_confirmation=1Why it's here
3 people recommend thisWhat people say. Engineers recommend this talk for its pragmatic perspective on avoiding over-engineering and finding the right architectural balance.
u/avedeiin r/softwarearchitecture • Recommends
…zzled about how you would split a platform into microservices. My first instinct is try to keep everything separate, isolate features as much as possible to prevent a single microservice failure from bringing down the whole platform. Upon reading some more this seems like the naive approach, architectures version of premature optimisation.
Here [video it asks why would you cut your system into tiny, distributed, hard to manage fragments. I agree with this as moving communication over the network introduces the need for HA mechanisms, failure detection, provision hardware for that microservice. Having many microservices will introduces issues with clients as well, as the client either has…