yeah that should be fine. out of experience, when we started - we used standalone hbase! and then slowly migrated to distributed mode with a much more stable hbase version. and all this was done while we had beta customers along the way. If infrastructure costs are something you want to optimize on while you are developing the platform, then this is a good approach.
thanks On Sat, Feb 18, 2012 at 6:29 AM, Bing Li <[email protected]> wrote: > Dear all, > > I am a new user of HBase. I just finished reading the book, HBase the > Definitive Guide. > > I am implementing a new page sharing system. HBase is a good choice to > process big data for me. The issue is that I still need much effort to > program my system and I need to focus on the logic of my system. At this > time, is it fine that I just take care of the Java client APIs for the > pseudo distributed mode? I plan to complete my system first and then > consider Map/Reduce integration and some other management techniques. Any > possible problems to do so? > > Thanks so much! > > Best regards, > Bing >
