-
Developer Book Syndrome
A colleague of mine once stated that creativity is rare in technical people I had my doubts at the time as I’m fairly creative and often build unorthodox solutions tailor made to the problem but the longer I’m in the industry the more I agree.
The biggest symptom of this is something I called book syndrome. This is where famous author xyz ( eg Lowly , Fowler etc etc ) writes a strategy in a book and people use it in completely in inappropriate circumstances. When challenged on the solution they use the authority of...
-
SOA 1 class per service Juval Lowy framework
I posted this a year ago....
I'm really against this make each class a separate service concept.
It reminds me of the Microkernel and especially workplace OS but worse.
The idea of microkernels was each service ( like memory) was an easily managed entity with carefully defined inputs and outputs which could be consumed.)
Workplace OS took this to limit and performance was so poor that no amount of optimization would help. So they had no choice but to scrap the project ( were talking $2B 10 years ago)
the bad thing is once such a design is made and implemented just like workplace OS...
-
POS or SOA Lite TODO
I think Service Orientation has gone the way of J2EE/ EJB and needs to be pulled back like was done with POJO.
I propose POS Plain old Services or POSA for Plain old services architecture.
Rules.
1) There is only one rule and that is KISS.
-
Is there a roll for OO in SOA
From Richard Turners blog
SO and OO are complementary technologies:
SO is how one thinks about building systems as a whole:
A System is a set of deployed services cooperating in a given task
Systems are built to change
Systems adapt to the introduction of new services after deployment.
...
-
Is SOA a Belief system and what does that mean for Team dynamics
Best SOA posts on the net ( and the comments)
http://blogs.msdn.com/richardt/archive/2005/12/13/503358.aspx
This is what I believe SO is ... it truly is a belief system and a way of thinking. It is not a prescriptive architectural process or methodology. It's not a template that you can apply that results in a service oriented system. It's where art meets science. It's where aesthetics meets engineering. It's the thing adds a human touch to the things we create. It's inside of me and it's inside of you....
james governor said:
i am with anil. a call for an epiphany is kind...
-
DTO pattern
http://msdn.microsoft.com/en-us/library/ms978717.aspx
http://martinfowler.com/eaaCatalog/dataTransferObject.html
I still think Martin Fowlers description is best
An object that carries data between processes in order to reduce the number of method calls.
While DTOs were designed for the above they provide key benefits to distributed systems
1.Performance
Typically Objects in OO have quite a chatty interface , this is good for design purposes as these communication mirror the relationships between the objects however the performance implications for distributed systems are significant and worse the worry about performance last mentality in software development makes a significant issue as these issues are VERY expensive to fix as the design from the start is...
-
Why do larger projects fail more often?
Since larger projects have more opportunity to learn ans share code why do they fail more ?
However the report does not show all good news. Time overruns have significantly increased to 82% from a low of 63% in the year 2000. In addition, this year's research shows only 52% of required features and functions make it to the released product. This compares with 67% in the year 2000.
-
OO with services
Are OO code and SOA diametrically opposed ? In a lot of ways this is true services tend to produce very anemic object models however this merely reduces reuse which is a myth in OO for the majority anyway .
However services have a unique but familiar problem . The contract of the service is critical it needs to be designed for
- The ease of use of the client
- For performance ( ie chunky calls , many small calls can bring many services down to its needs)
- To be upgradeable and allow backward compatibility.
- Compatible with an...
-
How to write a good service contracts
... not hand craft wsdl
Custom messages reduce churn and change in the contract
Lets say you have this datacontract
[DataContract]
public class WorkEntry
{
[DataMember]
public DateTime StartTime;
[DataMember]
public TimeSpan Duration;
[DataMember]
public string User;
[DataMember]
public string CostCentre;
[DataMember]
string Comments;
}
What can go wrong here ? Using public fields is good , its tight and if you need to do custom things you can refactor it easily. I think there is nothing really wrong here however if this is a business object also i would be concerned.
The big gotcha maybe DateTime , lets say you have some other systems in your company that use Java . Now Java systems...
-
Post by Frans Bouma
Loved this post so had to emphasize and post it.
"That's not the case. A framework user doesn't give a **** about how many different patterns the framework is using and how great and awesome it's internally and how it will ultimately evolve in the bringer of world peace. A framework user is interested in whether the framework takes care of things the framework user can't afford to spend time on. After all, the framework user can't afford to spend time paid by the customer on plumbing, on writing infrastructure code. The framework user is paid to write code directly...
-
Architecting for the team
One of the major differences between the oft and bad used example of building Architecture and Software architecture is people. When you build a building people know how to pour the concrete and a few specialized roles are imported electricians etc but with software we are expected to know all. If you have been writing Windows Forms apps for years if the new project is a web app it is expected that you know write a web application , the only exception seems to be with languages people seem to except a C# programmer cant write VB or Java -...