DDevelopment & Design

Try to get TouK’s plume during 33rd Degree Conference

Developers ‘re counting down the days till the 33rd Degree Conference. This years edition takes place on 13-15 March in Warsaw. Feel invited to listen Piotr Burdyło’s talk Managing gang of chaotic software developers is complex.

TouK supports the conference for Java Masters already for the third time (so from the early beginning). This year we’ll have our own stand – it’s an additional opportunity to learn more about us. Also we’ll have a little contest for you. To take part, collect TouK’s feathers, just look out for them in the crowd…

— Previous article

Journal.IO 1.3 released

Next article —

<!--:pl-->TouK na targach pracy<!--:--><!--:en-->TouK at the job fair<!--:-->

You May Also Like
DDevelopment & Design

TouK na targach pracyTouK at the job fair

Zapraszamy na XI Targi Pracy i Praktyk dla Elektroników i Informatyków. Odwiedź nasze stoisko w dniach 4-5 marca w godz. 9:30-15:30. Politechnika Warszawska Pierwsze piętro budynku Wydziału Elektroniki i Techniki Informacyjnych Nowowiejska 15/19We invite you to 11th Job and Internship Fair for Electronic Engineers and IT Specialists. Come and visit our stand between 4-5 March 9:30 am and 15 :30 pm Warsaw University of Technology the first floor of the Electronics faculty building Nowowiejska 15/19
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?