Two App Servers One DB

Hi All,

We are getting ready to launch a new version of our SAAS platform, the
current version is Railo (Railo 4.1.3.003 final) and the new version is
Lucee (4.5.3.020 final). We’d like to ramp users over from the old system
to the new system and utilize the same MySQL server database during the
process. Both use ORM, and the data models for both are identical.

Are there any caveats or concerns we should have about running both app
servers from the same db instance?

Thanks!

Seth

Make sure that they can’t create or update tables for one.

Mark Drew

  • Sent by typing with my thumbs.> On 1 Dec 2016, at 19:39, Seth Johnson <@Seth_Johnson> wrote:

Hi All,

We are getting ready to launch a new version of our SAAS platform, the current version is Railo (Railo 4.1.3.003 final) and the new version is Lucee (4.5.3.020 final). We’d like to ramp users over from the old system to the new system and utilize the same MySQL server database during the process. Both use ORM, and the data models for both are identical.

Are there any caveats or concerns we should have about running both app servers from the same db instance?

Thanks!

Seth


You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAE8ZmaaC6eYh77da8pAgzQJibP3kGZ-rvk%2ByEHsQigHDCU3scQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Seth- It’s very common that people run multiple application servers off a
single database on the back end, it allows for scaling / load-balancing for
one.

I’m not sure what Mark is referring to specifically regarding updates, I
think his concern here could be with the ORM actually altering the schema.

There shouldn’t be a problem with updating the database from multiple
application servers, you get into complexity with that where you have
multiple database servers you want to keep in sync, in that scenario having
one write master and multiple read-only slaves can make sense but multiple
app servers should all be able to update the same back end database safely.

Great, thanks! Mainly I was concerned about the way the hbxml and
primary/foreign key relationships were generated Railo vs Lucee. I
s’pose it doesn’t matter as long as only one of the servers is attempting
to update the schema at any given time.

SethOn Fri, Dec 2, 2016 at 3:57 AM, Ivan McAvinchey <@Ivan_McAvinchey> wrote:

Seth- It’s very common that people run multiple application servers off a
single database on the back end, it allows for scaling / load-balancing for
one.

I’m not sure what Mark is referring to specifically regarding updates, I
think his concern here could be with the ORM actually altering the schema.

There shouldn’t be a problem with updating the database from multiple
application servers, you get into complexity with that where you have
multiple database servers you want to keep in sync, in that scenario having
one write master and multiple read-only slaves can make sense but multiple
app servers should all be able to update the same back end database safely.


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/lucee/11cc3b5f-ba89-46d7-b72e-4b67db337f43%40googlegroups.com
https://groups.google.com/d/msgid/lucee/11cc3b5f-ba89-46d7-b72e-4b67db337f43%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.