Last post Apr 20, 2006 04:30 PM by rfurdzik
Jan 12, 2006 04:12 AM|rfurdzik|LINK
I have a question. DNN or not DNN??? I am designing huge project, comparing to Ebay. I was considering DNN at first, however now I have my doubts. It seems I may need to develop my own framework. There are many cons and prons. Besides the obvious advantages
like (Friendly URL, Internationalization, Search Interface, Admin Tool, Ads Managemenent, Premium Services Management, Portal Creation via Wizard) there are few problems I see so far with DNN:
- It seems it is the perfect solution for Company websites or personal websites
- Seems very slow when you run it first time
- Many times unexpected bahaviour happens
- Because of the complexity of the code it is very difficult to track any problems
- Development of new Modules is fairly complex
- Support is limited
- Problems upgrading and setting it up
Is it worth for me to start from scratch or better to change DNN including removing some of unnecessary (from my point of view) code? It seems that changing and understanding of the code is not simple...
I wonder what your thoughts are? Are there any big sites like ebay using DNN?
Jan 13, 2006 10:18 AM|k4gdw|LINK
Jan 13, 2006 11:58 AM|brian_c|LINK
If you don't code an application yourself.. it will always be difficult to know it completely
Then you have upgrades... once you chance the core... upgrading is very difficult.
However, you get a pre-built framework... for free. You have a developer community and modules available to purchase.
Sometimes you get features you don't want but you want the bug fixes .. so you have to take it all. That is the big downfall vs designing and creating an application yourself.
What would be perfect although time consuming (but happens in real world) is if each bug fix or enhancement had documentation showing exactly what was changed. You could then updated your code (if modified) to include what you wanted.
Pros .. Cons ....
Jan 13, 2006 12:19 PM|sowens|LINK
Is it perfect? No. It is a solution for some people. It has pro's and con's and really depends on what your requirements are.
Welcome to .Net. Your server(s) will have some to do with this. If your Ebay like, then you will never see a recompile unless the server is down.
Testing is important. Even the core will have bugs.
It is very easy to track problems. You can step through the code and debug anything with source in DotNetNuke and Visual Studio. You can do it other ways to.
It is only as complex as you want to build after you understand what needs to happen from DNN's standpoint. You can hire outside
companies as well. It really is no harder than coding anything else in vb.net and in some cases it is much easier. You don't have to worry about BLL and DLL archi because it is kind of defined for you.
You will find support amazing sometimes and you will find that sometimes you will not get an answer. Or you can contract with a
company and get all the support you need. [:D]
I can't argue here. The more times you do it the less problems you have.
Jan 13, 2006 01:03 PM|rfurdzik|LINK
Thank you all for yoyur feedback? But the most important question:
Would you use it for big solution like for eexample Ebay? Are there any big websites like Ebay using DNN today?
Would it be difficult to implement portal creation in regular ASP.NET?
Jan 13, 2006 01:05 PM|rfurdzik|LINK
Jan 14, 2006 02:26 AM|nbc|LINK
Well... EBays is a very big site! Sever infrastructure etc are more likely to be your concerns if you get to that stage. There are very big DNN sites out there both corporate and government, but you may find that they are not advertised as such for various
You don't really need DNN developers as such - you need application developers who are comfortable with .Net. If you post some requirements here I'm sure a few will come forward.
Mar 27, 2006 06:01 PM|rfurdzik|LINK
- Seems that DNN is slower than regular .NET applications.
- Seems it would be more difficult to implement single sign on solution to multi portals
- Seems that DNN skinning is not as flexible as designing the site the way you want from scratch. Seems it takes long time to actually master skinning in DNN. Seems like everything must be in modules, so there is not a lot of flexibility with the layout...
- Seems it will be very difficult to implement new technologies like Atlas, I would like to have my interface created using new Atlas GUI.
Wonder what your thoughts are. Would it be good to design large Ecommerce solution using DNN, should I just use .NET 2.0 with all the new exciting features like Atlas, Master pages and Membership Provider?
Mar 28, 2006 03:43 AM|isomies|LINK
DNN is large and sophisticated, it's just standard .Net code, so it is no slower than any other comparable application.
You keep mentioning Ebay. They have thousands and thousands of cpu's in their architecture. I remember reading that their database servers each have 12 cpu's and they have several hundred of those running in parallel spread around in mulitple datacentres
in the US. Do a google for ebay infrastructure and you will see what I mean.
A large secure ecommerce system on a multimillion user scale would require custom development and probably be in the order of 10 man years to many, many times that in just cutting code aside from all the other issues involved.
Mar 30, 2006 12:54 AM|mwr|LINK
>If the connection was down long enough my site would shut down from lack of traffic<
Could you explain that a bit more; what does that really mean?
I you have several DNN portals running on one DNN implementation (top-level site and several child portals), is the traffic necessary to keep the site "running" based on each portal's traffic or on the traffic for the entire DNN implementation?
Mar 31, 2006 02:33 PM|rfurdzik|LINK
Apr 03, 2006 12:50 PM|delyk|LINK
DNN is a huge project. If you choose to write something like this yourself be prepared to spend 2+ years making an equivelant that frankly, probably won't be as good.
There is an incredible number of developers poring over the code finding bugs and adding new features/skins/modules constantly.
Performance and scalability is a secondary issue IMO because you can always optimize and fine tune the DNN codebase until you achieve the necessary performance.
Don't underestimate the magnitude of work and achievements in DNN.
Stuff as much RAM in your WebServer as you possibly can and run the database on a second box (with full RAM as well). RAM is cheap and will make a bigger performance incerase than anything you do in software.
Apr 03, 2006 05:10 PM|gsaunders|LINK
Apr 03, 2006 08:17 PM|rfurdzik|LINK
Thanks a lot, very helpful.
Apr 20, 2006 02:34 AM|raca|LINK
I have build a DNN based site with 10+ modules that are working together and have over 30 tables. I used code generation techniques to speed up the development. I find DNN development very predictable so code generation can save you a lots of time. You can
contact me at radoslav(remove)@everestkc.(remove)net to talk off-line
I also plan to make even bigger DNN based site as well
Apr 20, 2006 04:30 PM|rfurdzik|LINK
Sounds good, I think I will just do everything in .NET 2.0 from scratch. I have found out that things like Friendly URL for example is not that difficult to do after all... Seems more flexible this way... It took me longer to learn somebody else's code.
Do not take me wrong, I think DNN is a great product, I just think it may not be the best tool for what I need. I will probably use it to implement a portal for my company, where we can exchange documents and place some announcements. Seems DNN is very fit