In Part I we looked at the advantages of building a data warehouse independent of cubes/a BI system and in Part II we looked at how to architect a data warehouse’s table schema. Today we are going to look at where to put your data warehouse tables.
Constellation’s independent “bill of rights” aims to serve as a base point during the vendor selection and contract negotiation process for SaaS apps — offering a best practices reference, checklist and key points for discussion.
GoSmarter is a JSon based Machine Learning System that, if given a Natural Language (NLP) Query, will return a list of recommended products. This Machine Learning also uses social networking capabilities to recommend products based on your friends.
This worksheet might help you when you're brainstorming the design of your Windows 8 app. It encourages the 3-tier navigation structure that’s common with these apps and helps you keep track of spacing conventions.
When architecting a data warehouse, you have two basic options: build a flat “reporting” table for each operation you are performing, or build with BI/cubes in mind and implement a “star” or “snowflake” schema.
In "Extending Neo4j" I showed you how to create an unmanaged extension to warm up the node and relationship caches. Let’s try doing something more interesting like exposing the A* (A Star) search algorithm through the REST API.