Tech Lead Journal cover image

#125 - Patterns for API Design - Daniel Luebke

Tech Lead Journal

CHAPTER

API First

Daniel: We should be conscious not to expose too much of the internal representation of our data model. So how can we come up with a better exposure of our domain model as part of the API request and response? I think really it's what you would call API first nowadays or put it differently. You should have a separate API interface, whether it's open API or something else. Daniel: It's much easier if your brain is working in a conceptual mode, like you're doing your DTT design,. If you're more involved, currently in requirements, discussions, and all these things, it's much easier to build an API which doesn't leak technical information.

00:00
Transcript
Play full episode

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.
App store bannerPlay store banner