2 ms·
The best part about these types of projects is also the worst: Anything that is java.io.Serializable can be used for keys/values This means you can immediately
by koolba 10y ago
The best part about these types of projects is also the worst: Anything that is java.io.Serializable can be used for keys/values
This means you can immediately save / load / stream your applications objects. Just tack on an "implements Serializable" to you class header (or "implements Externalizable" if you want to be fancy and do it yourself) and you're good to go. Plus with the native Map<?,?> interface writing code against it feels natural.
In practice this also means that you end up serializing arbitrary Java objects and get stuck in serialization/deserialization hell. Your data is stuck tied to a specific format, on a specific platform / language. It's somewhere between impractical and impossible to get it into an agnostic format usable by any other language so you're stuck in JDK land forever.
Anything that involves getting data into some other system or language requires you to also write a Java app to read (and possibly write back) your data.
Do yourself a favor and stick to something language agnostic for your data stores. You'll thank yourself many times over down the road.
- jankotek 10y agoHazelcast is not really an database. Data are 'persisted' in RAM.
- koolba 10y ago> Hazelcast is not really an database. Data are 'persisted' in RAM. I purposely didn't use the words "database" or "persisted". My comment applies even more so when data is persisted to durable storage (i.e. disk) but was meant to apply generally to any distributed data stores.
- deleted 10y ago[deleted]