# Lessons Learned: Don't Expose EF Entities to the Client Directly

DevFeed: [Lessons Learned: Don't Expose EF Entities to the Client Directly](<https://devfeed.tech/articles/lessons-learned-don-t-expose-ef-entities-to-the-client-directly-21169.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2012/10/lessions-learned-dont-expose-ef-entities-to-the-client-directly/>)

Published: 2012-10-23T00:00:00Z

Content type: opinion

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [ASP.NET](<https://devfeed.tech/topics/aspnet.md>), [mvc](<https://devfeed.tech/topics/mvc.md>), [API](<https://devfeed.tech/topics/api.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [web applications](<https://devfeed.tech/topics/web-applications.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [backend](<https://devfeed.tech/tags/backend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [json](<https://devfeed.tech/tags/json.md>), [mvc](<https://devfeed.tech/tags/mvc.md>), [rest](<https://devfeed.tech/tags/rest.md>)

## AI overview

The article examines the risks of directly exposing Entity Framework entities through an ASP.NET MVC REST backend to a rich-client JavaScript application. It highlights oversized JSON responses caused by entity relationships and warns that exposing entities couples the client to backend implementation details.

## Source excerpt

Lorem ipsum dolor sit amet