Skip to main content

Patterns Knowledge

Anti Pattern:

Its a pattern which we repeatedly do and which brings negative results.

Architecture by implication: Systems lacking a clear and document architecture.

Cover Your Assets: Continuing to document and present alternatives, without ever making an architectural decision.

Witches Brew: Architectures made by groups resulting in a mix of ideas and lack a clear vision.

Gold Plating: Continuing to define an architecture well pass the time which results in no benefits to the architecture.

Vendor King: A product dependent architectures leading to a loss of control of architecture and development costs

Big Bang Architecture: Designing the entire architecture at the beginning of the project when you know the least about the system.


  1. Merkur 15c Safety Razor - Barber Pole - Deccasino
    Merkur 15C Safety Razor - Merkur aprcasino - 15C for Barber Pole is the perfect introduction to the deccasino Merkur Safety Razor.

  2. You can see all major points} within the table under, including how 카지노 사이트 many of} factors you need to|you should|you have to} reach every level. Remember that withdrawals can only be made to the account and fee strategies you used for your unique deposit. In different words, you can’t withdraw cash to any account you need.


Post a Comment

Popular posts from this blog

Some good links -- Client side performance tips -- New exciting Framework, Must read. -- Very good resource to see various javaee projects and explore enterprise architecture and design concepts. -- Lots of interesting open source projects by eclipse -- the main project for supporting more dynamic languages to jvm. -- EcmaScript parser and -- Good place to learn patterns -- This will validate your website css and js -- An example of SHA1 collision attack.

@MappedSuperclass vs. @Inheritance

MappedSuperClass must be used to inherit properties, associations, and methods. Entity inheritance must be used when you have an entity, and several sub-entities. You can tell if you need one or the other by answering this questions: is there some other entity in the model which could have an association with the base class? If yes, then the base class is in fact an entity, and you should use entity inheritance. If no, then the base class is in fact a class that contains attributes and methods that are common to several unrelated entities, and you should use a mapped superclass. For example: You can have several kinds of messages: SMS messages, email messages, or phone messages. And a person has a list of messages. You can also have a reminder linked to a message, regardless of the kind of message. In this case, Message is clearly an entity, and entity inheritance must be used. All your domain objects could have a creation date, modification date and ID, and you could thus

Hashmap Keyset and EntrySet difference.

If you're concerned about performance when iterating through your hash map, I suggest you have a look at  LinkedHashMap . From the docs: Iteration over the collection-views of a LinkedHashMap requires time proportional to the size of the map, regardless of its capacity. Iteration over a HashMap is likely to be more expensive, requiring time proportional to its capacity. HashMap.entrySet() The source-code for this implementation is available. The implementation basically just returns a new  HashMap.EntrySet . A class which looks like this: private final class EntrySet extends AbstractSet < Map . Entry < K , V >> { public Iterator < Map . Entry < K , V >> iterator () { return newEntryIterator (); // returns a HashIterator... } // ... } and a  HashIterator  looks like private abstract class HashIterator < E > implements Iterator < E > { Entry < K , V > next ; // next entry to ret