Sam Gentile's Blog: All Comments

RE: Enterprise Service Buses (ESBs) Drive SOA Adoption Part 5 - Itinerary Based Routing

prefabrik — Fri, 20 Jan 2012 12:14:41 GMT

I like your sharing.It's very intersting and different...

RE: .NET Dependency Injection/IOC Container Recomendations?

Konteyner — Thu, 19 Jan 2012 10:57:42 GMT

it's very intersting.I like your sharing...

RE: Enterprise Service Buses (ESBs) Drive SOA Adoption Part 5 - Itinerary Based Routing

Konteyner — Thu, 19 Jan 2012 10:55:32 GMT

it's very intersting.I like your sharing...

RE: Enterprise Service Buses (ESBs) Drive SOA Adoption Part 5 - Itinerary Based Routing

Prefabrik — Wed, 18 Jan 2012 07:04:23 GMT

thanks for your sharing...

RE: Enterprise Service Buses (ESBs) Drive SOA Adoption Part 5 - Itinerary Based Routing

Şile evden eve nakliyat — Fri, 30 Dec 2011 07:14:08 GMT

thank you very much. :)

RE: Entity Framework in Three-Layered Services Application Pattern, ASP.NET MVC and Firewalled Layers?

GaryGS — Thu, 29 Dec 2011 18:43:20 GMT

I have found it pretty normal over the years that Microsoft choose to ignore the 3 physical tier architecture when designing their data access strategies. Thsy almost got it right with WCF Data Services mapped to EF but do not allow full CRUD when you chain them across two domains (it works for queries).

I recently used WCF Data Services to house the App Server service and expose the EF model. This is then called by the Web Server and the Entities are returned but are disconnected, so the only thing you have to do to use them is reconnect them to the model before updating. Seems to work well but I've only used it on a small sub-set of our data as an experiment so far. If you need more info, let me know. Gary

RE: Enterprise Service Buses (ESBs) Drive SOA Adoption Part 5 - Itinerary Based Routing

Sultanbeyli evden eve nakliyat — Thu, 29 Dec 2011 09:07:52 GMT

teşekkürler

RE: Mario Cardinal and Urban Turtle Scrum Tool for TFS

UNLEASHPM — Mon, 19 Dec 2011 10:50:24 GMT

Hi,

Unleash is an integrated solution for managing projects, collaborative Gantt scheduling, real-time reporting, bug tracking / QA, document management etc. The tool is fast, easy and builds on principles of team empowerment, increased communication, transparency, and collaboration.

http://www.unleashpm.com/

Thanks & Regards

www.unleashpm.com

RE: Entity Framework in Three-Layered Services Application Pattern, ASP.NET MVC and Firewalled Layers?

anonymous developer — Tue, 29 Nov 2011 15:29:02 GMT

“Because of this, the Domain Layer with EF (to reference the complex return types) had to be referenced by both the WCF services project and the MVC project”

Your DL should only be referencing the interfaces and not the types and your interfaces should not be defined in your EF project. Actually, according to the MS N-Tier architecture guidelines, your domain layer is where you should be defining the interfaces and then your wcf services should returning all of the objects as those interfaces.

Your projects should be setup like this:

Web box

Domain Services Project-> Defines Interfaces, implements business rules

MVC->References domain services

App box

EF -> References Domain Services, implements domain interfaces

WCF ->References EF and domain services, returns domain interfaces

See diagram on Page 35, in the Overview DDD N-Layered Architecture (4h Workshop).pdf

RE: Entity Framework in Three-Layered Services Application Pattern, ASP.NET MVC and Firewalled Layers?

Terra — Wed, 09 Nov 2011 16:50:49 GMT

You should consider the maxim that new is not always better. All these new technologies are not really designed to support decent architecture and we are all trying to find workarounds. When the effort of the workaround exceeds the benefit of the new technology it is defunct. Asp.Net MVC has rolled though 4 versions (inc beta 4) in under three years, which should ring alarm bells. Besides, ORMs and Entity Framework are for amateurs, the performance and concurrency degradation is unwarranted in high availability applications. Database is still the most common bottleneck in application performance, and throwing more hardware at it is not really an option (even azure is limited to a single instance/server under the hood - so much for cloud computing being infinately scalable - sorry a little off topic). Basically there is a lot of Hype around at the moment but the fundamentals haven't really changed. Our industry is due a reality check.