Lessons from the data lake, part 1: Architectural decisions