4 ms·

Wow, that's pretty hardcore...borderline badass! Interesting thing is this stack was doable probably 13+ years ago, so I see your emphasis on stability. Anywa

Wow, that's pretty hardcore...borderline badass! Interesting thing is this stack was doable probably 13+ years ago, so I see your emphasis on stability. Anyway, it's similar to what I'm using and surprised to see it here. Biggest tweaks are that I'd consider Vue/Webpack if starting today and do believe PaaS to be far superior to on-prem/colo. Also, not big on Hibernate or too much abstraction at the data access layer.

setquk 9y ago
It's possibly a summary of my frustration with the last 20 years or so. I've never used vue/webpack so can't comment. I've been shot too many times by javascript framework churn over the years. I wrote a relatively small and powerful abstraction over DOM that doesn't hide it away, merely makes the hard things easy and less verbose and allows simple templates to be used. Hibernate is essential if you ask me. One of the problems I see a lot is relying on features of the underlying storage engine. This, while it has advantages, has more disadvantages such as coupling and vendor lock in. These have been significantly costly when you have to scale something commercial up like SQL Server.
mercer 9y ago
Could you elaborate on the PaaS? I've been avoiding it, but partly that's perhaps because I'm a control freak and not for any particularly good reason.
- unclebucknasty 9y ago
  Well, I should have probably distinguished between IaaS ans PaaS, but primarily intended to differentiate between either of these and the GP's advocacy of on-prem or colo. That is, I would advocate PaaS and IaaS over on-prem/colo, and how far you go towards PaaS is a matter of comfort. I do think that comes down to control though, and I actually can't think of a much better basis for the decision.
  - mercer 9y ago
    Ah, right. so a VPS or even a dedicated server would be considered IaaS?
    - unclebucknasty 9y ago
      Possibly. I think the line runs along how the resources are exposed. That is, if they are literally manageable as a service (e.g. via API or management console), then yeah. No expert on the terminology here, though. Just how I understand the term.

setquk 9y ago

It's possibly a summary of my frustration with the last 20 years or so. I've never used vue/webpack so can't comment. I've been shot too many times by javascript framework churn over the years. I wrote a relatively small and powerful abstraction over DOM that doesn't hide it away, merely makes the hard things easy and less verbose and allows simple templates to be used. Hibernate is essential if you ask me. One of the problems I see a lot is relying on features of the underlying storage engine. This, while it has advantages, has more disadvantages such as coupling and vendor lock in. These have been significantly costly when you have to scale something commercial up like SQL Server.

mercer 9y ago

Could you elaborate on the PaaS? I've been avoiding it, but partly that's perhaps because I'm a control freak and not for any particularly good reason.

unclebucknasty 9y ago
Well, I should have probably distinguished between IaaS ans PaaS, but primarily intended to differentiate between either of these and the GP's advocacy of on-prem or colo. That is, I would advocate PaaS and IaaS over on-prem/colo, and how far you go towards PaaS is a matter of comfort. I do think that comes down to control though, and I actually can't think of a much better basis for the decision.
- mercer 9y ago
  Ah, right. so a VPS or even a dedicated server would be considered IaaS?
  - unclebucknasty 9y ago
    Possibly. I think the line runs along how the resources are exposed. That is, if they are literally manageable as a service (e.g. via API or management console), then yeah. No expert on the terminology here, though. Just how I understand the term.