high volume database choice for php [closed] - facebook

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am about to develop website using YII framework. But i am not quite sure about which database i should use.
Generally insertion and selection would be there in a website. Data would be come from different relational tables as i will have more than 50 filters so that user can see what ever database they want to see.
Here is the example of website. http://property.sulekha.com/
I want to design something like this.
which new concept i can use for the optimization, for better performance.
I have few concept in my mind which i am supposing to use.
1) MemCache
2) HipHop PHP
3) Doctorin ORM
I am just wondering how facebook search is working, are they using any advance tool for search??????

Facebook architecture is a fascinating one, and you shouldn't try to copy it, because you don't need it, and as we all know, premature optimization is the devil.
scaling issues are not something you prepare for, unless you're working for an enterprise and know first hand that you'll recieve huge amounts of traffic from day 1, like the new mega.
if you're talking about a large de-normalized table, which sounds so by applying up-to 50 filters, maybe you should consider a NoSQL solution, like mongoDB.
from what I know about facebook search, is that the servers are clustered, and are basically pointers to the "real" data, which means that alot of their data isn't a physical one, but as I said, unless you plan on sporting 1 billion users - that's over your head as of now.
good luck

Related

Should I go for document-based or graph database? (MongoDB vs Neo4j) [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am currently choosing a NOSQL database for the application which stores a lot of emails to given topics (=mailing lists). There is a huge number of emails for each of them. As an amateur in this area, I dont know if I should go for Document-based MongoDb or Graph oriented Neo4j. It is more like write once, read many type.
The facts for the Neo4j:
1. Emails are basically a graph. Each email is a node and one replies to the other (= an edge).
2. The graph can be really deep, one email can have many responds.
3. It may be needed to reorder some emails (to clean ordering if really needed) in graph.
The facts for the MongoDb:
1. Sometimes may user want to search for some parameter-based queries. For example all emails from the user X.
2. Emails can be quite big.
3. Documents looks much more simpler.
The fact I don't know where belong:
Sometimes it is good to search for the parents and check, where did email copied the text from (the specific text which email is replying to).
Can someone please help me?
EDIT: Anyway, I am also open to other nosql databases.
Maybe this blog post will help steer your decision: http://soloso.blogspot.com/2011/07/getting-enron-mail-database-into.html
Take note of the very bottom addendum area -- where #rit expanded on the original code and hosts a dump of the corpus on S3.
That ought to give you quite a bit to experiment with in the MongoDB environment.
Bryan

.NET CMS that handle complex surveys [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Our customer wants to migrate from DotNetNuke to another open source .NET CMS. I'm looking for something that will have the same advantages as DNN+Dynamic Forms/Registrations - ie. possibility to create complex surveys with events (showing one field based on response from another, auto-submit if specific answer occurs, events on survey submit like SQL query execution, HTTP POST or e-mail sending).
Right now there are thousands (around 50-100k) active users (each user logs in and has her/his personal data stored in DNN surveys), so this CMS should be capable of creating rather big solutions.
What are the options? Should we stick to DNN considering migration to a newer version? Are newer DNN versions worth the rework (we're currently running on 4.9.5). Are there any open source and free .NET CMS-es that are comparable to DNN in terms of survey creation, and are better option when we think of usability, performance, stability, etc. - basically all the fields where DNN more or less fails? We were thinking of trying out Umbraco - does it have a good survey module?
Any suggestions will be much appreciated.
Personally since you have such a platform already built on DNN I would strongly recommend looking at ways to upgrade your current system and stay with it. It will be very hard to find something else that will fit the bill most likely and the migration path will most likely not be smooth.
DNN upgrades can be a bit tedious, but they are not impossible as well as performance and stability are even better with the current versions. Usability is greatly improved with teh 6.x line as well.
Umbraco has a very nice form builder (http://umbraco.com/products/more-add-ons/contour.aspx) but you have to pay a tiny bit for it - I believe it's 99EUR.
We use it for quite simple surveys/contact us pages etc.
Out of the box it does allow for multi-page surveys (though I've never tried this) but it does not allow conditional questions.
That said it is very simple for users to set up new forms and surveys so I guess it depends how complex your surveys get.

First facebook-app: Hosting and Framework suggestions [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm planning to do my first facebook-app.
The core of the app would be to choose certain photos from your profile and show them to others users (of the same app). My background is more on the C++ side and low-level programming.
I want to know your suggestions for the following:
1- Which hosting do you suggest? I have read about google-app-engine and Heroku, however I am not sure which one fits best for a free plan until it grows to a significant number of users.
Heroku seems great for a beginner since they give you a sample code, but I am not sure about their databases and their scalability while being free. From here I understand that I have only 5 mb of databases for free which seems too little... right?.
And one more thing: I'm assuming is possible to show photos from others users directly from facebook without hosting it
2- Which framework and language do you suggest given the core of my app? It is not a sophisticated app, so I want to do it as fast as I can without many technical troubles.
Thanks in advance
I think Heroku is good choice for you. http://devcenter.heroku.com/articles/facebook

nosql databases - what are these good for? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Recently I watched some old Oredev presentation on NoSql databases. I learned a bit but I still don't know when these databases are typically used. When it's good to use one and when it's not? Before I start learning any it would be great to know if there will be any opportunity to use one. Do You have suggestions on what db to try first? I'm working in .NET, learning some Ruby.
I learned a bit but I still don't know
when these databases are typically
used. When it's good to use one and
when it's not?
I would recommend to read for example these:
What Should I Do? Choosing SQL, NoSQL or Both for Scalable Web Applications
35+ Use Cases For Choosing Your Next NoSQL Database
The NoSQL Ecosystem
Before I start learning any it would
be great to know if there will be any
opportunity to use one.
Opportunity knocks at the strangest times. It's not the time that matters but how you answer the door.
Do You have suggestions on what db to
try first?
If you have .NET background try to look at MongoDB or CouchDB. Answer to this question however may depend on what is your scenario or what is the nature of your problem where you want to apply NoSQL solution.
Here you can read something about:
The Big List of NoSQL Use Cases
I think that MongoDB is a good starting point.
Getting Started with MongoDB and C#

Flexibility of Yii [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I have come across a fair bit of information on CI being a really flexible framework. Does Yii also allow great flexibility? And the ability to pick and choose when to use it or your own php?
Flexibility is very subjective, so this question is a bit vague.
From my experience I can tell you that Yii is very very powerful, but in most cases when you want to go into really advanced territory you have to do things "Yii's way". If you do, you will find that the pieces of the puzzle click together really well and things go smoothly. If you don't (because presumably you haven't realized yet what "Yii's way" is), it's going to give you a hard time.
I am using YII since 2 years. I use it with combination with Zend AMF and create backend systems for Flash campaigns, create HTML5 webpages, simple pages, different competition pages and and find it usable for every case you need. The main advantage that it is really structured, logical and fast. So because of that I am spending my time on creating application logic, not on setting up environment, setting up all requests, pages, subpages etc., MVC model + ActiveRecord saves my time here.
I have been using Yii for a year now and find it very flexible. You can add your own methods to any model or write components outside models. You need to be familiar with the MVC structure, Object-oriented programming and for writing components, you need to know how to register the component in the config file and how to call it the Yii way.