Best Approach to my Application, SQL or NOSQL?

Question

0.00/5 (No votes)

See more:

Hello Everyone I need your suggestions on what would be the best approach in creating my App.

I am using VB.net and its going to be online.

Main Features:

On Runtime, Creating multiple Panels with multiple Functions... Within every created Panel.. There is an Add Button where Every time I click Add Button, It is created and embed with a Function like drag and drop. And by the way.. the Panel I created on Runtime is a UserControl embed with a panel For a Customize design and Function.

So on at Runtime I am Creating UserControls with Functions.

For every Added Panels and buttons etc.. I always use Addhandler, Addressof

And I will be using a database like Phpmyadmin.

What would be the best way in Saving the Created Panels with its Functions.

SQL or NOSQL? or any ideas on what would be much better?

What I meant for SQL is - Is like I would save into the database the buttons and panels I created, save their .text, location, and other properties, Like in my database their is an Column for text, Location, Panel_ID, Button_ID, ParentContainerID etc.

What I meant for NOSQL is - Is like a serialization method to put the settings into a structure. Then save the structure as a binary object so I don't have to parse the individual properties. converts a structure to a byte array. Then save the byte array into the database.

Posted 17-Aug-13 4:21am

DAAH1

Updated 17-Aug-13 4:27am

André Kraak

v3

Add a Solution

Comments

RedDk 17-Aug-13 21:41pm

What tool are you using to create this vb.net app?

DAAH1 18-Aug-13 11:58am

visual studio 2012

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mehdi Gholam · Answer 1 · 2013-08-17T05:27:00

It depends is the general answer.

There are a number of different factors which will effect your decisions such as :
1) your abilities in programming and what you are good at.
2) the usage pattern for your users.
3) the volume of data.
4) the performance levels you need.
5) how you are deploying your application.
6) how you need to support your application.
7) how much time you have to get the application ready.

Generally I would recommend you stick to what you know and create your application as fast as possible. Serializing data structures can be done irrelevant to the storage engine you are using so you can store them in blobs in any RDBMs for example which is a good way to go in any case.

IF you have time and can make allowances then take a look at Key/Value stores which will probably work for 70% of any requirements, Document stores will probably cover 99% of most requirements also.