Skip to content
0:00 / 0:00

#modularity#springdata#domain-drivendesign

Whoops! Where Did My Architecture Go? • Oliver Gierke • GOTO 2016

GOTO Conferences

1M subscribers • 91 videos on Hallway • Conference channel

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Oliver Gierke, Lead of the Spring Data Project at Pivotal
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

9.7K views9 years ago2 recommendations

Software designSoftware architectureDesign patterns

Oliver Gierke discusses the fundamentals of modularity and how to enforce architectural boundaries in software systems.

This presentation was recorded at GOTO London 2016 gotoldn.com Oliver Gierke - Lead of the Spring Data Project at Pivotal ABSTRACT Maintainable software needs to be modular to allow pieces of it to be evolved independently and at different paces. Accepting that, the question of which means to use to implement and enforce modularity still stays open. The talk starts by looking into the fundamentals of modularity [...] Download slides and read the full abstract here: gotocon.com/london-2016/presentations/show_talk.jsp?oid=8008 twitter.com/gotoldn facebook.com/GOTOConference gotocon.com 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=1

Why it's here

2 people recommend this

What people say. Recommended for learning how to structure packages and maintain modularity in Java applications.

u/Smoke_DeGrass_Tysonin r/typescript • Recommends

On “A Full Stack TypeScript+Java App I created after working a year as a Junior Dev”

…inal random UUID for each entity upon instantiation and adding it to the equals/hashcode. Wouldn't recommend using the generated ID. Also, learn how to properly use Optionals. A nitpick is the package structure. Would do by feature rather than by type. Much easier to maintain. Also look into how trasaction-management works in depth. see: 1: [video 2: https://junit.org/junit5/docs/current/user-guide/#writing-tests-assertions 3: https://vladmihalcea.com/eager-fetching-is-a-code-smell/ 4: [video…

u/rick-rebelin r/softwarearchitecture • Recommends

link to this video Whoops! Where Did My Architecture Go? by Pivotal's Oliver Gierke