DDevelopment & Design

Friday hackathon

Every month we have a Friday Hackathon, where we can code or create anything we want. That’s for the purpose of evaluating new technologies, doing crazy stuff or just having fun.

Beneath that we develop our skills and gain new experience.

Today we have 5 teams, that are doing following projects in various technologies:

  • Ping-pong scoring – we play ping pong a lot, so an app is a must! – Java (Dropwizard), Mongo
  • TouK’s library – we have dozens of books but currently we have a chaos who lends what – Clojure
  • ToukApi – access all internal data (about people, salaries, holidays, auth, projects people are in etc) through REST api – vert.x
  • ID / Drivers license recognition on Mobile – just shoot a photo of an ID and have all data and photo in a few seconds – Kotlin, Android
  • jaIde – I’m going for a sandwich – you can inform other employees that you go for a morning sandwich – that means – Mr Sandwich has just arrived at the kitchen – it’s like a snowball, the more people go for a sandwich the more confident you can be that there are actually sandwiches waiting :) – Swift/Scala/Java

At 4:30 PM we have hackathon summary. Let’s see what projects we will manage to accomplish…

 

rd

DSC_3057 DSC_3056

— Previous article

How to recover after Hibernate's OptimisticLockException

Next article —

Kotlin's extensions for each class

You May Also Like
DDevelopment & Design

Distributed scans with HBase

HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?