应用程序外观模式的最佳实践(Best practice for application facade pattern)

 我有一个多层SOA应用程序和一个包含100多个表的数据库。 我正在为我的数据层使用实体框架来处理所有CRUD操作。 
 
 我有一个门面类，它托管在一个服务上，可以通过全部客户端应用程序调用。 
 
 这个facade类包含诸如的方法 
 
private void DoSomething()
{
  //insert to table1
  //insert to table 2
  //delete from table 3
  //more CRUD operations
}
 
 而且Facade类基本上已经充满了类似于DoSomething（）的其他方法。 
 
 因此，客户端基本上将创建Facade类的实例，并获得对所有这些方法的访问权限。 
 
 我现在的问题是，这是门面图案的最佳做法吗？ 我觉得门面类太“重”了，如果我的应用程序扩展得更大，我不确定它是否会影响性能。 
 
 如果我有大量的方法，那么创建一个facade类的实例是一个非常昂贵的操作吗？ 

I have a multi tiered SOA application and a database with over 100 tables. I'm using entity framework for my data layer which takes care of all CRUD operations. 
 
I have 1 facade class which is hosted on a service, callable by client apps all over.
 
This facade class contains methods such as 
 
private void DoSomething()
{
  //insert to table1
  //insert to table 2
  //delete from table 3
  //more CRUD operations
}
 
And the facade class is basically full with loads of other methods similar to DoSomething()
 
So the client will basically create an instance of the facade class, and gain access to all these methods.
 
My question now is, is this the best practice for a facade pattern? I feel that the facade class is way too "heavy" and I'm not sure if it will affect the performance if my application scales bigger.
 
Will creating an instance of the facade class be a very expensive operation if I have loads of methods in it?

原文：https://stackoverflow.com/questions/12738819