>From a 'small guy' perspective, I was looking for the following and didn't find anything -
* ACID compliance * demo application, hopefully using best practices. I see you're aiming for web dev, so I'd do something with ASP.NET MVC (old-school ASP.NET is very painful, and the crowd using ASP.NET MVC will be much more likely to champion your product if it is good). Using best practices is important - see the Oxite debacle. * screencasts - those 5 minute 'build a blog' screencasts for Ruby, Django etc. are one of the first things I look at to get a general overview. * performance comparisons - is this going to impact performance compared to something like SQL Server with an ORM like NHibernate, Entity Framework? * does it scale, if so how? Other things - * a LINQ provider for this would be great. * there is a general sense of 'the unknown' around object databases - this needs to be dealt with, not just by saying relational databases are legacy software. People assume there are reasons why they are not taking off compared to relational, and there is nothing on the site to say otherwise. * DB administrators are notoriously protective of their relational databases :) * easer is spelt easier; steriods is spelt steroids 2009/6/29 Jason_au80 <jlangena...@gmail.com>: > > I had a look at your website, and my initial thought is "Why would I > use this?". > > (Actually my initial thought after seeing the ASP.NET code was "Thank > god I use Ruby". But I digress). > > Your website talks about features, not benefits. What is the advantage > of using a direct object store, in place of a traditional ORM & > relational database? Does it reduce coding time? Improve performance? > Lower the hardware requirements for a web application? > > Why would an ASP.NET developer, who has spent all their time learning > ADO/Linq/SQL Server (or whatever is used in the Microsoft world these > days - Constrex is a pure-Ruby shop at the moment, so I'm talking > outside my area of expertise) now invest additional time in learning a > new object model and syntax to use in the web applications? If there's > no direct benefit, then why would they do it? > > The other aspect you need to address is that of risk: With SQL Server, > you know that it's a proven technology, used in production the world > over, and if you need to scale it to handle database table with 100 > million rows and more, it'll do so without blinking. But if someone > uses Eloquera for their project, how do they know that one year down > the track, they won't hit some performance or scalability or > reliability limit of Eloquera, which will require them to rewrite > their application code (from quite a low level too), and migrate all > their data across to a proven database? > > You need to assuage their fears - otherwise, the risk of using a new > technology can far outweigh the benefits to them. > > So, as a practical start, I'd write out two lists: how Eloquera > benefits people who use it, and how Eloquera reduces risks for people > who use it. Then use those lists as the basis of your marketing, > starting with updating your website. > > Cheers > > Jason > > P.S. I did eventually find some justification for Eloquera down the > bottom of your "company" page, and I question your assumptions that > relational databases are merely used for "legacy software". > > > On Jun 28, 8:46 pm, Dmytro <dmytro.bablin...@gmail.com> wrote: >> Hi Guys, >> >> I am one of two co-founders of Eloquera (www.eloquera.com), >> recently we have made available to public our pre-release version of >> the database... and now we are trying to determine our marketing >> roadmap. >> >> Banners on specialized websites and google CPC program proved to be >> inefficient. >> Shall we contact open source guys one by one? Shall we contact >> companies one by one? Shall we publish articles? Shall we advertise? >> >> I guess the best answer is - all of these. But our resources are >> extremely limited at the moment. >> >> We understood that the first of all we need a first customer, even if >> we do that application ourself and for free. >> >> We contacted several locals and overseas database and web development >> companies - but looks like they are fighting for their own survival >> and they don't really care about trying anything else. >> >> What other options can we try? >> >> Thank you, >> >> Dmytro > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Silicon Beach Australia mailing list. No lurkers! It is expected that you introduce yourself: http://groups.google.com/group/silicon-beach-australia/browse_thread/thread/99938a0fbc691eeb To post to this group, send email to silicon-beach-australia@googlegroups.com To unsubscribe from this group, send email to silicon-beach-australia+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en -~----------~----~----~----~------~----~------~--~---
