101 reputation
1
bio website neo4j.org
location Dresden, Germany
age 39
visits member for 2 years, 8 months
seen Apr 7 at 20:45

Michael Hunger has been passionate about soſtware development for a long time. He is particularly interested in the people who develop soſtware, soſtware craſtsmanship, programming languages, and improving code.

For the last two years he has been working with Neo Technology on the open source Neo4j graph database. As a developer evangelists he's having fun helping Neo4j users to be successful with their use-cases and projects. He is also the project lead of Spring Data Neo4j. Good relationships are everywhere in Michael’s life. His “real” life concerns his family and children, running his coffee shop and co-working-space "die-buchbar", living in the depths of a text-based multi-user dungeon, tinkering with and without Lego® and much more.

As a developer he loves to work with many aspects of programming languages, learning new things every day, participating in exciting and ambitious open source projects and writing and contributing to different programming related books. Michael is an active writer, speaker and conference organizer. If you want him to speak at your user group or conference, just drop him an email at michael at neo4j.org


Jun
29
awarded  Autobiographer
Nov
18
comment Is NoSQL a replacement for traditional SQL, or an addition?
Actually it means "Not Only SQL" and embraces polyglot persistence. See the article by Martin Fowler (martinfowler.com/bliki/PolyglotPersistence.html). And there is a range from NOSQL stores handling large amounts of simple data to NOSQL stores handling complex, rich data (skillsmatter.com/podcast/nosql/…)
Nov
18
comment Can NoSQL databases cause occasional data loss?
Neo4j is a NOSQL (graph) database that is actually ACID compliant. It comes with full transaction support and durable persistence. Neo4j also uses transaction-logs to secure write operations before applying them to the datastore. Disclaimer: I work for Neo Technology.
Nov
18
comment Amount of data per node in Neo4j
How big are your chunks in general? You should make sure to find a suitable string_block_size to keep the number of string blocks in the storage down to a reasonable level as well as not wasting too much space in only half-filled blocks. How will the data be used? Just rendered or also queried/processed otherwise? If you need to save space, compression + storage as byte array can be an option.