Monish Nagisetty's Space

Building connectivity on-premise, in the cloud and beyond

Announcing MOCSDUG (Mid-Ohio Connected Systems Developers User Group)

Drum roll…

I’ve been given the exciting opportunity to start a subgroup under CONDG (Central Ohio .NET Developers Group).  You can read more about the recent updates at CONDG on Steve Harmans’ blog post.  The sub group is named MOCSDUG (pronounced mocks-dug) which stands for Mid-Ohio Connected Systems Developers User Group.  You may wonder why the sub group does not use “Central” for the first word within the acronym.  I will leave that your imagination.

The motivation behind starting MOCSDUG is to raise awareness about specific type of challenges we face today in the Enterprise (note the big E).  Most of members of CONDG are already familiar with the challenges they face when building client/server, smart client, and web applications.  The challenges are not new and we can build manageable solutions using different frameworks and patterns (EntLib, NHibernate, Active Record, Monorail, etc) in our enterprise.

So where does this brings us? We now have 5 or more custom applications each possibly using a different database, framework and language in our Enterprise.  Pretty soon someone will ask you how we can make App A to talk to App B, App C to App A, App D to App A and so on.  One of the first approaches to this problem is to write custom code to integrate each application with another application.  This is called point-to-point integration.  Although this is a reasonable approach within an enterprise that has a handful of apps, it quickly becomes complex and unmanageable.  If you have 5 applications and they all need to talk to each other, the number of points of integration (custom code in each app) will equal to 10.   The formula for this is n*(n-1)/2 where n is the number of apps.  There are multiple solutions available to address the point-to-point problem and you can read all about them at your leisure.

The Integration Problem is central to the challenge I was referring to earlier and our approach to connecting systems will address this problem.  Enter ESB, SOA, BPA, BPI, and Click here to generate another acronym.  Also enter BizTalk, WCF, and WF.  The goal of MOCSDUG is to focus on these technologies and approaches to understand how we can better solve the integration problem.

I am currently still working to get a site setup for MOCSDUG so please be patient.  In the meantime, do not hesitate to contact me (mnagisetty at if you would like to be added to the mailing list.

It looks like some of you are already excited and blogging about MOCSDUG.  That’s great! Spread the word! 


February 7, 2008 - Posted by | Uncategorized | ,

1 Comment »

  1. You bet I’m excited. Now it’s a matter of negotiating with my wife for yet another night “out/off”. Such is the geek life. 😉

    Comment by Jeff Hunsaker | February 7, 2008 | Reply

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: