4 ms·

I'm the decision maker for the company in question - Authentise. It was a combination of cost and the fact that we need to support an in-datacenter install opti

I'm the decision maker for the company in question - Authentise. It was a combination of cost and the fact that we need to support an in-datacenter install option for our customers. RDS is really great if you need all of the failover and backup options it provides and you don't have the manpower to invest in it. That's how we got our services started. But, as our expertise and automation grew it ended up being a modest cost savings to handle our own backups and redundancies. Primarily, though, we just can't install RDS in someone else's datacenter on premises.

toomuchtodo 10y ago
Well done on not being married to AWS. Its usually a costly lesson for those who don't prepare for that earlier in their environment's lifecycle.
whyleyc 10y ago
Thanks for the background info, very helpful. How has on-prem install gone for you guys ? There was an article on HN yesterday suggesting it was a royal PITA (for ops and support), would be interesting to hear about your experience. Also FYI, your homepage has a 2015 copyright notice on it. No big deal, but thought you might like to know since it could put off particularly "nit picky" types of customer :)
- JimDabell 10y ago
  > Also FYI, your homepage has a 2015 copyright notice on it. No big deal, but thought you might like to know since it could put off particularly "nit picky" types of customer :) If that's when the work was created, then that's correct. Copyright notices aren't there to tell you what year it is today. They are there to tell you when the work was created. If they change it to 2016 when the work was really created in 2015, then that's an invalid copyright notice and equivalent to no notice at all.
  - kccqzy 10y ago
    Exactly. I've actually had a manager tell me to update a copyright notice from 2016 to 2015. These are the real nitpickers.
  - _Codemonkeyism 10y ago
    Heard this for the first time, so being really curious (I always have the most recent year in a range on my sites) What if the page is dynamically created on the fly? What copyright should I have? If page contains snippets/work created in different years?

toomuchtodo 10y ago

Well done on not being married to AWS. Its usually a costly lesson for those who don't prepare for that earlier in their environment's lifecycle.

whyleyc 10y ago

Thanks for the background info, very helpful. How has on-prem install gone for you guys ? There was an article on HN yesterday suggesting it was a royal PITA (for ops and support), would be interesting to hear about your experience. Also FYI, your homepage has a 2015 copyright notice on it. No big deal, but thought you might like to know since it could put off particularly "nit picky" types of customer :)

JimDabell 10y ago
> Also FYI, your homepage has a 2015 copyright notice on it. No big deal, but thought you might like to know since it could put off particularly "nit picky" types of customer :) If that's when the work was created, then that's correct. Copyright notices aren't there to tell you what year it is today. They are there to tell you when the work was created. If they change it to 2016 when the work was really created in 2015, then that's an invalid copyright notice and equivalent to no notice at all.
- kccqzy 10y ago
  Exactly. I've actually had a manager tell me to update a copyright notice from 2016 to 2015. These are the real nitpickers.
- _Codemonkeyism 10y ago
  Heard this for the first time, so being really curious (I always have the most recent year in a range on my sites) What if the page is dynamically created on the fly? What copyright should I have? If page contains snippets/work created in different years?