locked
What about making domain specific "Enterprise Library" ? RRS feed

  • Question

  • Presently "Enterprise Library"  is related to Application Development Process.

    Desinging "Enterprise Library" for the best practices is good.

    But what about making enterprise library... related to Solution Specific, I mean to say domain specific... For eg.

    - Financial, Manufacturing, ...etc.

    Friday, January 20, 2006 12:53 PM

Answers

  • Hi,

    Very interesting point.

    I have heard of template driven persistent store(i.e table layouts) designs
    being done for some domains such as retail, manufacturing.

    Prasanth
    Monday, January 23, 2006 8:33 AM
  • Hi,

    Don't you think it is tough because we are inhibited by today's languages (i.e C#, Java)... ? ;)

    I am not an expert in languages, but I feel Charles simoyni http://www.intentionalsoftware.com/ is doing something about it.

    Prasanth
    Monday, January 23, 2006 8:40 AM
  • Developing a shelve architecture for a vertical market is a much greater effort compared with createing a set of basic application blocks

    see for example the insurance application architecture by IBM http://www-03.ibm.com/industries/financialservices/doc/content/solution/278918103.html 

    Arnon

    Monday, January 23, 2006 9:10 PM

All replies

  • I think if Tom and his team start developing EntLib for every domain, they will be coding forever...

    Domains are huge, and even though you get a domain specific EntLib, trust me, you will still have to go ahead and change tons of stuff to get it fixed as a base of ur app.

    I rather have a common EntLib (like the one which we have now) and customize it to suite the backbone of my app. This customized EntLib can then be used in various other apps in my org... Don't you agree its much better option?

    My 2 cents

    Cheers!

    Monday, January 23, 2006 7:10 AM
  • Hi,

    Very interesting point.

    I have heard of template driven persistent store(i.e table layouts) designs
    being done for some domains such as retail, manufacturing.

    Prasanth
    Monday, January 23, 2006 8:33 AM
  • Hi,

    Don't you think it is tough because we are inhibited by today's languages (i.e C#, Java)... ? ;)

    I am not an expert in languages, but I feel Charles simoyni http://www.intentionalsoftware.com/ is doing something about it.

    Prasanth
    Monday, January 23, 2006 8:40 AM
  •  pven wrote:
    Hi,

    Don't you think it is tough because we are inhibited by today's languages (i.e C#, Java)... ? ;)

    I am not an expert in languages, but I feel Charles simoyni http://www.intentionalsoftware.com/ is doing something about it.

    Prasanth

    Hi Prashant, on the contrary i think it is more easier now that we can built solutions without the language factor in mind...

    Monday, January 23, 2006 10:17 AM
  • Developing a shelve architecture for a vertical market is a much greater effort compared with createing a set of basic application blocks

    see for example the insurance application architecture by IBM http://www-03.ibm.com/industries/financialservices/doc/content/solution/278918103.html 

    Arnon

    Monday, January 23, 2006 9:10 PM
  • Hi Rohan,

    I agree with you that we  have  grown to looking at architectures solutions w/o language factor. However, I feel language plays a crucial role when modelling the domain.

    I don't want to push this post to another orbit but here is an analogy.

    We have matured to relational databases from network databases, file databases.. But the fact still remains a relational database is not the silver bullet to all needs. It has its own issues for ex: ORM issues.

    Personally, whenever I see a relational database I feel it is a pigeon hole (Yes,  it is due to my poor aptitude in math )



    Tuesday, January 24, 2006 6:59 AM