Re: RO vs kbmMW
- From: "Lauchlan M" <LMackinnonAT_NoSpam_ozemailDOTcomDOTau>
- Date: Wed, 30 Nov 2005 11:39:54 +1100
> I would like to setup the app using an n-tier approach.
> I have seen several threads in the past in regards to RO vs kbmMW.
> I have noticed that both products have made great advancements since I
last
> read the reviews and I would like to get updated recommendations from
> other users about each product and why you prefer your choice.
Hi
Firstly, I don't know what you're hoping to acheive, since very few if
anybody stay up to date with both products and can give you a current
comparison!
I have used both products and prefer RO/DA. The main reasons are that I like
the service builder and schema modeller (GUI tools for setting up and
managing your tiers) in RO and DA and prefer the implementation of services
in RO to in kbmmw, and that the learning curve in RO/DA paid bigger
dividends for me.
I should point out that I am a member of Team RO, so that says something
about my personal preferences.
In any case, my advice is download a free trial of each, try to build the
same simple test project(s) in each, ask questions on the newsgroups for
each product, and see what way your experiences stack up for you and your
development needs.
> -Price (concern, but not the deciding factor)
> -Support (developer / community)
> -Learning curve (Currently using DBISAM C/S installs)
> -Future proof? (Any news on what is ahead for each that would help on the
decision)
I wouldn't worry too much about price unless there are budget constraints.
The better development solution for you will probably save you many
man-hours and therefore $$.
Both have active and excellent user communities.
Both have learning curves. Probably both are much the same in this regard,
but I personally found that effort inveted in RO/DA tended to pay off better
for future projects or work than the same efforts invested in kbmmw. Also RO
have a dedicated staff member to improving documentation and articles.
Both have ongoing development and planning and are 'future proof' in that
sense. I do think though that the companies can be differentiated on their
business model: RemObjects is a company with a number of employees and a
team of core developers. If a developer is sick or on leave, the company and
support can carry on. As far as I know, kbmmw is still essentially a one man
project with a loose confederation of collaborators and business partners
supporting that effort.
> From your experience, is n-tier considered overkill in some instances and
what
> is the deciding factor that you make your decision to use/not use n-tier?
Once you get past the learning curve, it's not that much overkill and has
many benefits, such as security, improved managability of code moved on to
tiers in the server, easily supporting multiple DBs, etc.
HTH
Lauchlan Mackinnon [Team RO]
.
- Follow-Ups:
- Re: RO vs kbmMW
- From: Scott Martin
- Re: RO vs kbmMW
- From: John E. Wilfong
- Re: RO vs kbmMW
- References:
- RO vs kbmMW
- From: Scott Martin
- RO vs kbmMW
- Prev by Date: Re: RO vs kbmMW
- Next by Date: Re: Other remote control solutions?
- Previous by thread: RO vs kbmMW
- Next by thread: Re: RO vs kbmMW
- Index(es):
Relevant Pages
|
