I''m having hard time convincing my boss that a Rails app would be better than a php one, but the fact that in php changes you make at the code are seen as soon as you modify the code is pushing him towards php. In Rails (in production mode) you have to restart the server somehow if your model has changed (am I wrong?). Hot deploy is important in our app. What I don''t understand is: couldn''t I simply write an action that invalidates the cache of a part of the application (say a model)? And, what is exactly cached in production (except for caches I can configure, of course): only the schema of the db? What else?
> I''m having hard time convincing my boss that a Rails app would be > better than a php one, but the fact that in php changes you make at the > code are seen as soon as you modify the code is pushing him towards php. > In Rails (in production mode) you have to restart the server somehow if > your model has changed (am I wrong?).You want to make changes to live code on the server? Regardless of the language, that seems shockingly dangerous. What requirements are really forcing this? Rails caching doesn''t apply in the way you''re suggesting; caching stores rendered pages or fragments of pages. There''s no seperate caching of the business logic in model code.
I''m talking about columns caching (DB schema)> Rails caching doesn''t apply in the way you''re suggesting; > caching stores rendered pages or fragments of pages. There''s no seperate > caching of the business logic in model code.