openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #04495
Re: OpenERP CMS: How is server separation implemented?
Dear all,
Just wanna give my input here. First of all, this new feature is amazing
and will serve lot's of business use cases in various area (like event,
ecommerce, hiring stuff and more).
For lot's of people, this new feature is a revolution, and I'm strongly in
favor of it. But, let's keep our head cool. If you're not ruling a small
company, then:
* When you're facing hundreds of orders a days and thousands visitors,
you'll not succeed to have it all in one instance. Imagine, who will block
his operation because they have too much click on their front-end ? Fors
that reason (and security if you matter about), you'll prefer 2 servers.
* base_synchro is clearely not an option to separate 2 OpenERP servers.
It's has simply been abandoned by OpenERP for good reasons IMO (bad design,
to many troubles in real uses cases, no atomic transaction to inappropriate
to sync ERP datas).
* This included ecommerce is a great step forward and people will love it.
But other e-commerce platform (like Magento, Prestashop and lot's of
others) have years of experience and devs behind them. They provide lot's
of advance products, sales and scaling features that you will not found in
OpenERP E-commerce yet.
* In case you're running a important e-commerce solution, I think you will
definitely keep 2 tools and use a connector in-between (like
https://code.launchpad.net/openerp-connector)
For others purposes, like HR & recruitment, events publication and more,
this new feature is clearly a big advantage. It will also serve small
companies for their first e-commerce experience and that's great ! This is
also a first step in the direction of having one tools to rules front and
back end together. But I cannot reasonably imagine it's viable for middle
to large companies currently.
Those was my little though here. See the enormous progress, but keep an
objective view :)
Regards,
Joël
On Sun, Jan 19, 2014 at 12:55 AM, Graeme Gellatly <gdgellatly@xxxxxxxxx>wrote:
> In regards to base_synchro. Some weeks ago I totally refactored this
> module and ported to v7. There is an outstanding merge request in to
> server-env-tools on v7 branch which as yet has not been reviewed. So
> if you require this functionality then please test it and get it
> merged.
>
> It adds a new module, base_synchro_auto for automating
> synchronisation, automatic population of fields with boolean style
> selection of fields to sync. There is a third module which I am
> trying to work out how to make generic which is an initialisation and
> configuration module for existing databases which will match up all
> the existing matching records prior to syncing.
>
> It won't do translations AFAIK (although maybe syncing the
> ir_translations table does it, I don't know), but forms a good base
> upon which to extend.
>
> https://code.launchpad.net/~gdgellatly/server-env-tools/base-synchro-7.0/+merge/200127
>
> On Sun, Jan 19, 2014 at 3:24 AM, Mariano Ruiz <mrsarm@xxxxxxxxx> wrote:
> > Fabien says:
> >
> > 2/ deploy separatly the frontend and the backend (and use modules like
> > base_synchro to sync them)
> >
> >
> > But, the base_synchro module is not supported any more from the 6.1
> version.
> > We use this to sync two OpenERP 6.1 instance, and we found a lot of bug
> in
> > this module. A special error related for this discussion: the module not
> > sync translatable fields! only export the original value, without
> > translations.
> >
> > We report this, but the response was: "base_synchro" doesn't exist
> anymore
> > on trunk and in stable release 7.0, So this issue doesn't affect to
> trunk.
> >
> > So, we fix the module, but only tested in 6.1 version, maybe for 7.0 and
> > trunk version is not working, check the bug #1195801.
> >
> >
> > 2014/1/18 Fabien Pinckaers <fp@xxxxxxxxxxx>
> >>
> >>
> >> >
> >> >> As an example, we just did a quick prototype to illustrate my point.
> >> >> Check this video, a new way of doing quotations:
> >> >>
> >> >>
> https://drive.google.com/file/d/0B5BDHVRYo-q5SDZFcEJmTXFyNTA/edit?usp=sharing
> >> >
> >> > This is awesome. I imagine instead of sending a customer a quotation
> >> > with 100 pages, you can have a interactive webpage, including
> graphics,
> >> > videos, 3d-modells and all the stuff.
> >> >
> >> >> This is so cool. I bet it improves quotes success rate by at least
> 20%!
> >> >
> >> > If we have the first customer implementing this, i will ask him to do
> a
> >> > A/B-Testing to validate your numbers ;)
> >>
> >> We will use this for our own need within 4 weeks. So, I will be able to
> >> provide stats.
> >>
> >> >
> >> >> 2/ deploy separatly the frontend and the backend (and use modules
> like
> >> >> base_synchro to sync them)
> >> >
> >> > What is the branch on that, so that we can have a look in details?
> >>
> >> It s an official module since v6
> >>
> >>
> >> >
> >> >
> >> > Greetings
> >> >
> >> > Markus
> >> >
> >> >
> >> > --
> >> > Dipl.-Comp.-Math. Markus Schneider
> >> > Softwareentwickler
> >> >
> >> > initOS GmbH & Co. KG
> >> > An der Eisenbahn 1
> >> > 21224 Rosengarten
> >> >
> >> > Mobil: +49 (0)172 2303699
> >> > Phone: +49 (0)4105 5615613
> >> > Fax: +49 (0)4105 5615610
> >> >
> >> > Email: markus.schneider@xxxxxxxxxx
> >> > Web: http://www.initos.com
> >> >
> >> > Geschäftsführung:
> >> > Dipl. Wirt.-Inf. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
> >> > Haftende Gesellschafterin: initOS Verwaltungs GmbH
> >> >
> >> > Sitz der Gesellschaft: Rosengarten – Klecken
> >> > Amtsgericht Tostedt, HRA 201840
> >> > USt-IdNr: DE 275698169
> >> > Steuer-Nr: 15/205/21402
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~openerp-community
> >> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~openerp-community
> >> More help : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> > --
> > Mariano Ruiz
> > Software Architect & Web Developer
> > http://www.mrdev.com.ar
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openerp-community
> > Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openerp-community
> > More help : https://help.launchpad.net/ListHelp
> >
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
>
--
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS
*Joël Grand-Guillaume*
Division Manager
Business Solutions
+41 21 619 10 28
www.camptocamp.com
Follow ups
References