What Would Batman Do?

Yes Batman!

He’s vulnerable!

Batman is one of the most interesting superheroes because unlike spiderman, superman or the hulk; he as NO superpowers.

Zilch … Nada … Zero!

So, what keeps the guy going?

A ton of money? (It helps)

Yes, he has a lot of money but he is also at the highest risk of getting hurt (both as batman and as Bruce Wayne).

Batman uses stealth tactics for his arsenal of weapons and usually only comes out at night (where he can use the power  of his superior weapons in the dark). After all, one wrong move and the bad guys won’t even flinch. The worst of them being his arch enemy – The Joker – who is also extremely intelligent (and human).

If you were on a battlefield at night, then you would want night vision goggles – to have superior vision compared to your competition because you could see them much better than they would be able to see you. Wouldn’t you?

Of course you would!

Considering what we know about batman, lets ask batman to pick a Data Warehouse architecture for his company Wayne enterprises:

The criterion would probably look something like:

1. Automation – Batman is a geek. He likes tools and automation. So, a majority of processes should be “automatable”. The Data Vault fits here, but you could argue about a certain level of automation with other architectures as well (none as good as the DV though).

2. Traceability – If something didn’t work, he would want full traceability to quickly figure out what happened. Well, you can’t really beat the Data Vault on this one.

3. Expandability – Something you can enhance without sacrificing the core, so you can add layers on top and take advantage of an already stable base. It’s the Data Vault again because other architectures would simply break on the change of business rules. The impact on the DV would be the least, because the foundation isn’t affected.

Lets look at something more interesting:

4. Stealthiness – Batman loves stealth. He wants everything to be his secret. The Data Vault Data Warehouse can be your secret weapon for agile data warehousing. It’s completely hidden from the business users, and they can’t really figure out (and shouldn’t have to) how you can produce what they need – so quickly.

5. Scalability – There are many elements to scaling. However, the DV is the only architecture designed from the ground up to scale up (and down) in terms of data, processes as well as team size. Data Vault 2.0 extends this even more by enabling big data and NoSQL systems to be part of the solution and by using tactics like parametrized data integration loads for very fast development cycles.

I think batman would pick the Data Vault hands down.

Of course, he’d have to learn how to implement it correctly and who better to learn from than the chap who invented it? I think he could probably hook that up with Dan. You can too, right here:

[ Data Vault Implementation – SQL Track ]

Batman sure wouldn’t like to waste time on this because time is too precious.

I’ve been snooping around to see our competition (everyone else whom Dan has actually taught which results in second hand info) and I was surprised to see … they’re more expensive than us.

Holy mother of batman! … time to raise our prices Dan.

You can bet, I’ll be pushing him to.

Take Care,

Sanjay Pande

PS: Dan is knee deep in Data Vault 2.0 right now. Just like he gave us Data Vault (now 1.0), he’s working on something we can all use to make our projects better, faster, easier, predictable, scalable, agile etc etc etc. There’s more on that front coming soon. However, you’ll get a solid foundation with the Data Vault Implementation course here:

[ Data Vault Implementation – SQL Track