Forums (Obsolete)

Member

alvaro - 5/25/2005 4:21:33 PM

three tiered architecture?

Hello,

I am evaluating Kentico as an alternative to speed up the development process for a new project.

I need to develop a customized CMS system for a customer that enforces a strict three tiered architecture. I wonder if I could use Kentico in such an environment, that is: an ASP.NET application hosted in an IIS in one server that consumes the Kentico API from another server which in turn uses a remote SQLServer for data storage. I would probably need to have control over the way the Kentico API accesses SQLServer (for example I can't afford to have the database login and password stored in clear text in a configuration file), and also to integrate the Kentico API with extended custom-build functionality developed by us. Do you think this is possible?

Thanks in advance for your time,
álvaro.-

Guest

admin - 6/8/2005 6:37:10 PM

Re: three tiered architecture?

Hi álvaro,

I'm very sorry for the delay in answering your message.

Kentico CMS is generally a three-tiered application, however, you can run Kentico CMS API (the business layer and database layer) only on the web server where the ASP.NET front-end is running.

Regarding your concern about password storage - you can use Windows authentication for connecting to the SQL Server as well or you can use your own custom storage for SQL password.

Should you need any details, please feel free to contact me.

Best Regards,

Member

wtijsma - 6/9/2005 1:31:29 PM

Re: three tiered architecture?

Hi Petr,

I'm sorry that I can't fully agree...

I asked the same question before we bought KenticoCMS, and after starting to develop with it, I feel this wasn't an entirely correct answer, but wasn't able to find a CMS that had the same set features AND was also an architectural beauty (for a reasonable price).

In KenticoCMS there's no layer separation between the business layer and the data layer. 3-Tier architecture would imply that it's completely database independent, and just by replacing the datalayer you could run it on every data source. But since much of the SQL code is generated in the business layer, this isn't possible, so I think that would make it a 2-tier application.

The API doesn't expose all functionality from the CMSDesk, because there's even SQL parameter generation and file moving/saving in the codebehind files of the ASPX, so this would make the CMSDesk a 1-tier application.

The whole KenticoCMS surely has some aspects of a multitiered application, but strictly taken it isn't. Neither would it be possible in the current setup, because couple SQL queries are coupled to the application 'objects' (document templates), which is pretty flexible but impossible to make database independent.

This definately doesn't mean I'm sorry that we have bought it, on the contrary, I've become pretty enthousiastic about KenticoCMS, as it has evolved a lot in the last year, and I'm also happy to see that most of my suggested features has been implemented without any additional costs and e-mail questions are usually answered within the next day.

Kentico has managed to implement great functionality only found in Enterprise-level content management systems in a transparent way, and I'm pretty happy to stick with them.

I wouldn't know a product that has equal features that even comes close to KenticoCMS, so if anyone here does, let me know ;-)


Member	wtijsma - 6/9/2005 1:52:26 PM Re: three tiered architecture? I do must say that I feel it's about time to start refactoring in the direction of a 3-tier application and integrating to more or less propagated .NET standards using the MS Enterprise Application Blocks (Provider Model, DAAB, Membership Management, Exception Management, Caching Framework).


Guest	admin - 6/9/2005 2:28:30 PM Re: three tiered architecture? OK, thank you for your suggestions! We will try to improve the architecture and code in the nearest versions.

Member

lucasrem - 7/15/2005 8:14:08 AM

Re: three tiered architecture?

hello peter, i heard about you, only good stuff, wiebe likes the Kentiko delevoping alot. is there a way wiebe and i can join this togetter, like a project, the three tiered architecture. This implantation was original my idea, but wieb never whanted to go for that untill now. iam not shure if that going to be a netindustry project or a stip project, please work this out with wiebe.

togetter we make great stuff

lucas rem
www.netindustry.nl


Guest	admin - 7/15/2005 8:29:28 AM Re: three tiered architecture? Well, we plan to change the architecture with move to ASP.NET 2.0. We will use some of the built-in features, interfaces and providers then. Best Regards,


Member	lucasrem - 7/19/2005 4:46:06 AM Re: three tiered architecture? thanks, thats great, hope wiebe will make the new controls in VisualStudio beta 2 soon.


Member	lucasrem - 7/15/2005 7:53:00 AM Re: three tiered architecture? I do too must say that I feel it's about time to start refactoring in the direction of a 3-tier application, this meens that i still was right and we can do this, the application layer is my thing;) togetter we make great things lucas rem www.netindustry.nl