- Speed - How fast product responses to user actions.
- Instant Utility - Instantly be useful, people don't like lot of configurations. Populate the service with default data, let user get up and started in no time.
- Voice - Software has to have a personality, people have to feel they are consuming media.
- Less Is More - Simplicity is for startup and gives a platform to ultimately grow from their.
- Programmer - API's for others to use
- Personal - Customer should feel more personal or more ownership of the application, by putting more of their data, avatar or names, people should invest more time and energy
- RESTFul - clean urls
- SEO - Discoverable by google, social media etc
- Clean - Make very inviting, not too much of data on pages.
- Mobile, Social, Intelligent, Playful
According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl { @PersistenceContext(unitName="PolarPU") protected EntityManager entityManager; -- } public class BearDaoImpl { @PersistenceContext(unitName="BearPU") protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"> <!-- Database 1 --> <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL"> ...
Comments