Comments by "Metalstorm" (@M3t4lstorm) on "Uncovering Stack Overflow's Shocking Architecture" video.

  1. SO is just a glorified forum, forums have been around for decades and are are mostly just CRUD operations. There is no real-time'iness about it, no huge amounts of data (think IoT, streaming, personalization/suggestions, etc). There doesn't seem to be any integrations with other large systems (CRMs, data warehouses, BI, ML, etc). They don't protentially lose large amounts of money if a number of users can't login/create a post. It's extremely read heavy, that's the easiest to design for. They are not dealing with financials/transactions/money, if something is out of date or data is slightly wrong it doesnt matter. SO still has downtime/maintenance basicslly every week or so, i wonder why...it's a sinple architecture because its a simple system.
    39
  2. You know performance isn't the number 1 priority of a microservice architecture right? Nor is a deciding factor if you should use MS or not
    3
  3.  @ihateidiots9484  Sounds more like a bad Dev team/system design.
    3
  4.  @ihateidiots9484  they are obviously doing it wrong if those are the kind of problems you are seeing. I am speaking from a lot of experience in this field.
    2
  5. Only a few? Literally 1000's of companies follow microservices (or at least try to). For large corps, sure legacy stuff might be monolithic, that's not because monolithic is better, it's just that changing an enterprise system once it's been in prod for many years to anything else is a massive amount of work. Anything in the last 5 years or so (of a decent scale) will more than likely be microservices (again, at least try to).
    1
  6.  @fxfighter  ye then you need to rack it, maintain hardware backups, redundant locations (different countries at least - currencies, tax, processes, laws, etc), pay someone to manage and maintain all of this security/vulnerabilities, networking, storage, patching, etc...infra engi easily 50k+ a year.
    1