't really want to sell this as a database technology, but rather a cost saving tool for creating distributed applications (that was really the problem I tried to solve in the first place, it just turned out to be a graph database). Any thoughts on this?
======
opendomain
There are over 100 different NoSQL databases - so you have to definately show
something on how your software is better. Most NoSQL are open sourced and are
free to use for limited installs, so it will be very hard to make money with
licensing. Some offer a base version for free, but offer clustering or other
advanced features at a cost. Some charge money for consulting. Where does your
db sit on the CAP spectrum? How is it the best for a specific use case?

~~~
tom_andersson
Yeah, I realise there are quite a few nosqls around. But only a few have just
recently started to gain momentum. It is still very easy to find developers
who have never heard of anything but traditional relational databases (not
sure if I would dare to say the majority of all developers). In most cases
relational databases is the best option for what they are doing, but I think
there are many situations where people choose the old sql just because they
don't know better. So, although there might be a point in comparing and
competing between different NoSQL technologies, I think all within the NoSQL
movement can gain from better marketing to all these relational database
users.

Anyway, I think what you are saying is I need to be very good at describing
why my technology is better than others, which as a developer I find very
difficult. It is easy to be technical about it, but how to describe something
at a level that makes sense to the average guy is something I am still trying
to learn.

What my solution does very well is integration with object oriented languages
and where the data is described by complex inheritance structures and
ownership relations (say a financial model with different types of financial
instruments, different types of market data, static data, deal data, etc which
would be described by a number of class hierarchies; and all linked together).

With the risk of getting too technical, if you are building a C++ application
for example, you only create your C++ classes (with any inheritance structure
which can be single/multiple etc), and you
' t really want to sell this as a database engineering, but preferably a cost saving cock for create distributed applications (that was very the trouble I tried to solve in the first place, it just turn out to be a graph database). Any thoughts on this? 
 = = = = = = 
 opendomain 
 There be over 100 different NoSQL databases - so you have to definately show 
 something on how your software is better. Most NoSQL are exposed sourced and are 
 free to use for limited installs, so it will be very intemperate to make money with 
 licensing. Some offer a base version for complimentary, but offer clustering or other 
 advanced features at a monetary value. Some charge money for consulting. Where does your 
 db sit on the CAP spectrum? How is it the best for a specific use case? 

 ~~~ 
 tom_andersson 
 Yeah, I realise there are quite a few nosqls around. But only a few have just 
 recently started to gain momentum. It is still very easy to find developers 
 who have never hear of anything but traditional relational databases (not 
 sure if I would defy to suppose the majority of all developers). In most cases 
 relational databases is the good option for what they are doing, but I think 
 there are many position where people choose the old sql just because they 
 don't know well. So, although there might be a point in comparing and 
 competing between different NoSQL technologies, I remember all within the NoSQL 
 movement can gain from better marketing to all these relational database 
 drug user. 

 Anyway, I think what you are saying is I necessitate to be very good at describing 
 why my technology is better than others, which as a developer I line up very 
 difficult. It is easy to be technical about it, but how to describe something 
 at a level that makes common sense to the average guy is something I am still trying 
 to learn. 

 What my solution does very well is consolidation with object oriented languages 
 and where the datum is described by complex inheritance structures and 
 ownership relations (say a financial model with different types of financial 
 instruments, different type of market data, electrostatic data, deal datum, etc which 
 would be described by a number of class hierarchies; and all linked together). 

 With the risk of getting too technical, if you are building a C++ application 
 for model, you merely make your C++ classes (with any inheritance structure 
 which can be single / multiple etc), and you
't rfally want to sell this xs a database tgcynologb, but rzther a zost saving tool for creatinj diwtribyted applications (that was realpy the peobltm I tried to solts in thc firab plaee, it just turnec out to ba a graph datatare). Any thoughts on this?
======
opendomain
Therq are ofeg 100 different NjSQL qatagases - so you have to definately sgow
someuhing on how your xoftware is better. Most NoDQL wre open sourced ajd are
free jk ufw for limitea installs, so it will ge very hard to make money with
uicenxing. Some ifder d base versmon fog free, but ofnvr clusdering pr other
advanccd feeturws at a cost. Some chacge money for consuljing. Where dkes your
db sit on tye CAK spewtruo? Hod ia mt fhe bedt hor a speciric use casw?

~~~
tom_andersson
Yeah, I rqqlise there ade quiee a few nosqls around. But only a few havt jusf
recently started to gaun momentum. It is stipl very ewsy to find developers
who have never heard of anydhing cut tvadiguojal relational databases (not
sure if I would dwde tp say the majovity of all develolegs). Yn most cases
telatiouzl databases is the hest opjion fir what trey sre doing, but I think
there qre many sitlatiins where people ckoose the olb sql kust necause they
don't know bztter. Ao, although there mifft be a point in cokpdring and
competing between differenv NoSAL techvolobies, I think all withlt the NoSQL
movemenh can gdin from bftter marketing to all these relational databssa
usvrs.

Anyway, I thlnk what you arq saying is I ueed to ye verh good at sescribmng
why my teshnology is bajter than othxrs, which as q deceloper K find very
difgicult. It is easy ti be technical abomt it, gut how to descxnbt womething
at a kevdl ehwt mwnes sense to the avdtage euy is somebhivg I am still trying
to laarn.

Shat my solution dpef very wgll is ineegration witn object oriented pangueges
anv wherr tre data is described by comples inheritwncc structures wnd
oqnership relctions (say a financial model with differxnt types of financial
ibstruments, differenj tnpes of markxt datw, static gata, deal data, etc wyich
would be descvibed by a number of cmass hherarfhies; and all linked together).

With the risk of getting too technical, if yoy are uuylding a C++ zpplocatimn
yor exampje, yln only create youg C++ classes (with any inheritance structuse
chich can be single/multiple eyc), and you
't really want to sell this as technology, rather a saving tool for really problem I tried solve in the place, it just turned out to a graph database). Any thoughts on this? ====== opendomain There are over 100 NoSQL databases - so you have to definately show something on how your is Most are sourced and are free to use for limited installs, so it will be very hard to money with licensing. Some offer a base version free, but offer clustering other advanced features at a Some money for Where your sit on the spectrum? How is it the best for a specific use case? ~~~ tom_andersson Yeah, I realise there quite a around. But a have recently started to It is still very easy to have never heard of anything but traditional relational (not sure I would dare to say the of all developers). In most cases relational databases the best option for what they are doing, but I think there are many situations choose the old sql because they don't better. although might a point comparing and competing between different NoSQL technologies, I think all within NoSQL movement can gain from better marketing to all these users. I think what are saying is I to very good at describing technology better as developer find very difficult. It easy to be technical about but how to describe makes sense to the average guy is something am still trying to learn. What my does very well is integration with object oriented languages and where the is described inheritance structures and ownership relations (say a financial with different types of instruments, different types of market data, static data, deal etc would be by a number class hierarchies; and linked together). With of getting technical, you C++ application for example, you only your classes (with any inheritance structure can etc), and you
't really want to sell this as a dAtabase tecHnoloGy, bUt rAtHer a Cost Saving tool for cREatiNg distributed applicatiOns (thAt WAs reALlY the pRoblem I TRiED To sOlVe In tHe FIrSt plaCe, iT just tuRned out to bE a gRaPh database). AnY ThOughts on thIs?
======
oPendomain
TheRe aRe over 100 DiFfeREnt NosQL DatabAses - so YOu have To definatElY Show
soMEthing oN HOw Your Software is better. MOSt nOSQL are open souRced anD aRE
fREE to Use For limited InStallS, So it wilL Be VERY haRD to make money wIth
licensinG. somE offer A bAse VErsion For frEe, BUt oFfer clusterIng oR other
advAnced fEAtures aT A cost. SoMe charGe mOneY for COnSuLtiNg. wHerE DoEs yOUr
dB sit on thE CaP SpectRum? HOW IS It thE beSt foR a speCific use case?

~~~
tOm_aNderSSon
yeah, I RealiSe thErE are qUite a fEw nosQlS around. But only a Few hAve just
reCenTlY stArTed to GAin momEntUm. IT is stilL very eaSY to FiND DEvElopers
who have neveR hEARd Of anythiNg but tRAdItIOnal relaTiOnaL datABAses (nOt
suRE iF I would dAre to sAY tHe MajoritY oF all deVeLopErs). in mosT CaseS
relatIonal datAbaseS Is the best optioN For what they arE DoING, bUT I thInk
There are manY sitUAtioNs whERe PeoPLe choOse thE oLD sQL just because they
don'T kNow betTer. So, Although there Might be a poINT In comparIng aND
cOMpeting between DiffeRent NoSQL tEChnologiEs, I thInk all wiThin the Nosql
movemenT caN gaIn fRom BETtEr marketing to ALL theSe RelatioNal DatabasE
usErs.

anyWay, i tHink what yOu are sayInG iS I NeEd tO be veRY good at dEsCriBiNg
wHy my tEChnoloGy is bEtteR tHaN OthErs, whicH As A DEvelOpEr i finD veRy
DiffiCult. iT is Easy to bE technicaL abOUt it, BuT hOw to desCribe somethinG
aT a level thaT mAkeS sense TO The averaGe guy is something I am stilL Trying
tO leArn.

WhAt my Solution dOes Very weLl iS IntegrAtion wIth obJeCt oRIEnted LANgUagEs
And where thE DAta Is desCrIbed By complEx inheritance strucTUreS and
ownership RelAtioNS (SaY a fINaNCiaL mODel WITh different typeS of financiAl
INsTruments, diFFerEnT types oF market Data, sTAtic datA, deal data, Etc which
wOuLd be DEScrIbed by a numBer of claSs hierarcHIes; anD AlL linkEd tOgetheR).

WIth The riSk of geTTinG too tEchnicAl, If you aRe buiLdIng a C++ appLication
for example, you onLy creaTe youR C++ cLasses (witH anY InhEritance sTrucTure
which cAn bE siNgle/mUltIPle etC), and YOu
't really want to sell thi s as a dat abase  te chn ol ogy,  but  rather a cost savi ng tool for creating d istri bu t ed a p pl icati ons (th a tw a s r ea ll y t he pr oblem  Itried t o solve in  th efirst place, it  just turn edout to be agra ph dat ab ase ) . Any  th ought s on t h is?
== ====
open do m ain
Th e re areo v er  100  different NoSQLd at a bases - so you  haveto de f i nat ely  show
some th ing o n  how yo u rs o f twa r e is better.Most NoSQLa reopen s ou rce d  and a re
fr ee touse for lim ited  installs , so i t  will b e  very h ard to  ma kemone y  w it h
l ic e nsi n g.  So m e o ffer a b as eversi on f o r f ree,  bu t of fer c lustering oroth er
a d van ced f eatur es a ta cos t. Som e cha rg e money for con sult ing. Wher e d oe s y ou r
dbs it onthe  CA P spect rum? Ho w  is  i t t he  best for a specif ic u se  case?
~~~
to m _a nd e rsson
Ye ah , I  rea l i se th erea re  quite a  few n o sq ls  around .But on ly  afew  have just 
recen tly star ted t o  gain momentum .  It is stillv er y ea s y to  fi nd develope rs
w h o ha ve n e ve r h e ard o f any th i ng but traditional rel at ionaldatab ases (not
sur e if I wou l d dare tosayt he majority of al l dev elopers).I n most c asesrelation al databa s e s is the  be stopt ion f or  what they ar e doin g,  but Ithi nk
ther e a reman y s it uations w here peo pl ech oo sethe o l d sql ju st  be ca use  they don'tknowbett er .S o,althoug h  t h e re m ig ht  bea p oi nt in  com p ari ng andcompeting  be t ween  d if ferentNoSQL technol og ies, I thi nk  al l with i n  the NoS QL
movement can gain fr o m bette r m arket ingto all th ese  relat ion a l data base
u sers. 
Any w a y, It h in k w ha t you ares a yin g isIneed  to bevery good at descr i bin g
why my tech nol ogyi s  b ett e rt han  o t her s ,  which as a dev eloper I f in d  v ery
diffic u lt.  I t is ea sy to b e tec h nical a bout it,but how t odesc r i besomethingat a lev el that m a kes s e ns e tothe  avera ge  gu y issometh i ngI amstilltr ying
t o lea rn .

Whatmy solution does very w ell is  inte gra tion with  ob j ect  oriented  lan guages
and  wh ere  thedat a  is d escr i be d b y  comp lexi nheritanc e  s tru c t ur es and
owne r s h iprelat ion s  (saya fi nancial model wit h  different typ es o f fin anc i al
i ns truments, diff ere nt t ypes ofma rket data,static d at a , dea l data , etcwhich
w o u ld be des crib edby a numb erof class h ie ra r chies;  and  a ll lin ked to g ethe r ) .

With the risk  of g e t tingt ootechn ic al, ify ou a re buildin g a C++ app licati on
f or ex ample,yo u only  cr ea te your C+ +  classes(with  any in he rita nce  struc ture w hichcanbe  si ngle/mult i p le et c) ,  an d yo u
't really_want to_sell this as a_database technology,_but_rather a_cost_saving tool for_creating distributed applications_(that was really the_problem I tried_to_solve in the first place, it just turned out to be a graph database)._Any_thoughts on_this?
======
opendomain
There_are_over 100 different NoSQL databases_- so you have to_definately show
something_on how your software is better. Most NoSQL_are_open sourced and_are
free to use for limited installs, so it will_be very hard to make money_with
licensing. Some offer_a_base_version for free, but_offer clustering or other
advanced features at_a cost. Some charge money for_consulting. Where does your
db sit on the_CAP spectrum? How is it the_best for a specific use_case?

~~~
tom_andersson
Yeah, I_realise there are quite a_few nosqls around._But only_a few have_just
recently started to gain momentum. It_is still very_easy to find developers
who have never_heard_of anything but_traditional_relational_databases (not
sure_if I would_dare_to say_the_majority of all developers). In most_cases
relational_databases is the best option for what_they are doing, but_I_think
there are many situations_where people choose the old_sql just because they
don't know better._So, although_there might_be a point in comparing and
competing between different NoSQL technologies, I_think all within the NoSQL
movement can_gain from better marketing_to all_these_relational database
users.

Anyway, I_think_what you_are saying is I need to be_very good_at describing
why my technology is better_than others, which as_a_developer I find very
difficult. It is_easy to be technical about it,_but how to describe something
at_a_level_that makes sense to the_average guy is something I am_still trying
to learn.

What_my solution does very well is integration_with_object oriented languages
and where the data_is_described by complex inheritance structures and
ownership_relations_(say_a financial model with different_types of financial
instruments, different types of_market data, static data, deal data, etc which
would be_described by a_number of class hierarchies; and_all_linked_together).

With the risk of getting too technical, if you are_building a_C++ application
for example,_you only create your C++ classes (with any inheritance structure
which_can be single/multiple etc), and you