in

ASP.NET Weblogs

Natty Gur

.Net from enterprise architect point of view.

January 2005 - Posts

  • Microsoft is looking for Enterprise architect.

    I saw that MS is looking for EA (http://jobsearch.monster.com/getjob.asp?JobID=26778830 ). I was really happy if could do that job… not just for fulfilling myself and help the company, but also because of the influence that I could have in such a position on the EA industry. So if someone, which regularly reading my blog, found me capable of performing such a position can say couple of warm words about me I’ll be grateful!

  • How bad is your enterprise condition?

    I've compiled 10 questions that might help you to get an idea about your enterprise condition:

     

    1)      Is your organization has any blueprint or matrix of all running systems, how they communicate one with each other and which technology they are using?

    2)      Can you show me a matrix of professional user groups, their requirements and systems that address those requirements?

    3)      Do you have mapping of all of your enterprise data, how data being grouped and by how data is being accessed?

    4)      When you start a project do you have blueprint, which you have to follow, for the type of the application you up to start with?

    5)      Is there a formal stage in the project life cycle were system architecture is being checked against the enterprise architecture.

    6)      If you have any question or problem regarding architecture do you know whose job is to help you?

    7)      Is there a clear list of all technological tools and services that your system might use or you can use whether technology you want?

    8)      Do you have duplicate application or data?

    9)      Is there a clear development methodology in your enterprise?

    10)  Do you know of more then 10 technologies (development tools, operating systems, Databases, ERP tools, etc’) used in your organization?

     

    9-10 : call me or leave me your contact details I WANT TO LEARN FROM YOU.

    7-8 : I guess you are running EA for a while.

    5-6 : you just start an enterprise architecture effort. Be aware from EA pitfalls so your effort will come to it end.

    1-5 : read about Enterprise architecture. You need to go through such a process.

     

  • If you want you can contact me using Skype.

    If you find Enterprise architecture, architecture or ASP.NET interesting and you would like to chat on those subjects with me you can find me on Skype under the name “nattygur”. I cant promise to talk to anyone, but I’ll be happy to do so if I’ll have time :-) .

  • Comments about my last post.

    I realized that some people miss interpret my post as a provocative one. I just want to clear that I just said my own Ideas so if some one want to treat them he welcome. That’s all, I just want to share with others what I found problematic.

     

    Another point that I want to clear is that my posts are JUST from Enterprise point of view. All those ideas represent enterprise needs and not every ASP.NET user.

     

    Here is a link to Dion Hinchcliffe blog who criticizes me, and my replay.

    http://hinchcliffe.org/archive/2005/01/23/158.aspx

  • If you'd been ASP.NET group architect what are the top 5 changes that you would have done.

    I've been asked this question more then once so I decide to take the challenge. I listed the changed by the level of importance (from my point of view).

     

    1)      NVC 2 as internal implementation of ASP.NET. MVC 2 is pretty common in other technologies, and not for nothing! If someone uses that pattern he probably found it more easy to work with and as major factor that helps system maintains. Implementing IHttpModule broke some of the Page abilities such as PostBack and View State. But you can achieve MVC 2 without harming Page abilities by using Application events. I really can't see way ASP.NET team didn’t implement MVC 2 infrastructure inside the code. They can always add config entry to disable it.

    2)      I don’t know if they design ASP.NET this way but I really like the Microkernel implementation of ASP.NET. I can find there kernel, internal services as HttpModules and external services as HttpModules. But if they have gone toward adaptive systems why they didn't implement Reflection and let us add our own events to the application and page events. That might be more useful then pile of events compiled in code.

    3)      Container, light container or even very light container. I think that there is lot of power in containers. Implementation of IOC and AOP might help those software infrastructure guys in enterprises to supply easily services to their co-workers: the developers. I even heard couple of MS folks argue that ASP.NET is application server. Application server without Container…. As far as I know MBF is going to save us with some level of container, let's wait and see.

    4)      Enable Post back to return just needed data to the client and enforce the changes in client side on given HTML control automatically. Most of the time that we use post back is just for update certain control as a result of changes in another control. So why we need to send all the HTML back from the server to the client, even if the HTML contain tens of Listbox that aren't going to change at all? Post back might be design in such a way that with little changes in the server side code and client side __dopostback method, the doPostBack can send request to the server and receive back just the needed HTML for given control. Then the __dopostback can update the given HTML control content and that's all. Probably much less data goes on the net this way and less tasks to be done on the server side.

    5)      Pluggable – It common those days that by given Interface I can write my own implementation of given service and by update certain configuration file the system will call my own implementation instead of the default one. Now, why can't I do that with Session, cache, and security modules? I know that Session object will be pluggable in 2005 but what about the others?

     

    That's the 5 that think are the most important and naturally there are much more. But, don’t take me too serious. After all ASP.NET team found me not technical enough :-)

    Posted Jan 23 2005, 11:35 AM by nattYGUR with 3 comment(s)
    Filed under:
  • Nice analogy between Architecture and Music.

    First of all, all the rights goes to Leonard Fehskens from HP. At least I heard him for the first time making this analogy , and I really like it.

     

    Architecture

    Music

    Architectural methodology

    Music theory

    The architect

    The composer

    The architecture

    The musical score

    The project/program manager

    The conductor

    The implementers

    The musicians

    The project

    The performance

    The users

    The audience

    The sponsor

    The impresario

     

     

     

     

  • My Hebrew interview.

    Roy just upload the interview (hebrew version). you can find it on his website

    http://www.teamagile.com/mainpages/Interviews.html

    I'll be happy to hear any feedback ...

  • Did you take in account grid computing while working on your enterprise architecture?

    It’s pretty obvious that grid computing is one of the technologies that enterprises will use in order to solve CPU and RAM heavy consuming needs. the thing is that if your technical architecture include basic elements that support grid computing you might find yourself with bunch of systems that need re-designing and re-writing to make them grid computing enable.

     

    Actually you need to follow RM-ODP (Reference Model for Open Distributed Processing http://www.dstc.edu.au/Research/Projects/ODP/ref_model.html ) transparency regulations, and you’ll be ready to move to grid computing. there still lots of work to be done, but you don’t need to re-design your systems.

     

    Those transparencies include:

     

    1. Access – Transparency of data and information reacquired to interoperate with other system objects within the parent system or with other objects and components in interactive systems.  
    1. Failure – Transparency of failures and exceptions within the system and transparency of the way to track them and recover from them.
    1. Location – Transparency of pointers, aliases and physical locations of the system components and interfaces used to connect between inner and outer components.
    1. Migration – Transparency of platform changes and migrates for system-objects which will enable fluency in accessing specific objects within theirs new platform or location.
    1. Relocation – Transparency of the regulated host relocations (e.g. storage clusters) of system entities to enable load-balancing of the application system.
    1. Replication – Transparency of duplication procedures of data and information within the system. (Databases, State controls)
    1. Persistence - Transparency of consistence to enable redundancy of objects and entities in cases of inaccessibility.
    1. Transaction – Transparency of the intermediations and transactions between the system data components. (e.g. XML schemes)

     

     

     

  • My mistakes…

     

    Yesterday I’ve being interviewed by Roy Osherove as part of his initiative to  interview and publish figures (http://teamagile.com/mainpages/Interviews.html) . it was 2 hours of interesting conversation that mainly touch enterprise architecture and little bit on system architecture. One nice question that Roy ask me was to list my mistakes….

     

    Nice challenge that you can all hear when Roy will publish the Interview. Well there are two major mistakes that I’ve learned:

    1)      I call it “First interpersonal relationship then technology”. When I was younger I thought that I can change things by myself. That way of thinking lead me from time to time to be rude to people that not follow my ides. Well, I was wrong and I learn it the hard way. Now I now that you can’t win the battle yourself, you need others with you. In order to join others you need most of the time to hold yourself and to get time to help others see their mistake instead of argue with them.

    2)      Don’t be look or in love with certain technology. Once I was Microsoft fanatic. It was Microsoft way or the highway. But I learn that it a mistake! You should listen and learn from every technology that you know, because each and every one of them has something to offer that you might take advantage of.

     

    That the major one while Roy will finish his work I’ll be happy to publish the link.

     

  • My Architecture and ASP.NET US tour.

    My East coast tour will take place from 5.19 to 5.26.

    5/19-21 and 5/25-26 - New York and Boston area.

    5/22-24 - Florida.

    you can read more details on the tour content at: http://weblogs.asp.net/ngur/articles/397570.aspx.

    If you're interesting contact me through the web or Roni at +972-50-7495474.

    --------------------------------------------------------------------------------------------------------------------

    I’ll make the tour in may-June. By now I’ll be in east coast at the last two weeks of may and in the west cost in the 3 first weeks of June. I’ve already got booked presentation about:

     

    1)      ASP.NET (1.1 – 2.0) Internals.

    2)      Architectural Patterns, how I can use them with .NET.

    3)      Enterprise Architecture – Lessons learned by now.

     

    I also have to offer one day workshop on developing Enterprise software infrastructure for ASP.NET systems. This includes but not limit to MVC 2 pattern without harming ASP.NET work, Manage extensions, light containers, naming server, etc’. It’s a 10 hour workshop.

     

    If you want, or you know someone how is interest in such activities please contact me via my blog.

More Posts Next page »