5 ms·

Would be fascinated to see them take on big G. E: not that I support these guys in any way. Just curious what would happen -- and whether we might all learn so

Would be fascinated to see them take on big G. E: not that I support these guys in any way. Just curious what would happen -- and whether we might all learn something about DDoS mitigation from such an event.

nostrademons 12y ago
Google gets DDoSed all the time. You don't hear about it because, well, the DDoS SREs are very, very good at what they do.
- mjdesa 12y ago
  SREs?
  - deleted 12y ago
    [deleted]
  - detaro 12y ago
    Site Reliability Engineers
  - nostrademons 12y ago
    Site Reliability Engineer. It's a Google (+Facebook)-specific title that is sort of like a sysadmin or devops, but instead of keeping the system up, they write code that keeps the system up. They also have a different negotiating position vs. engineering than in many other companies, eg. SREs have veto power over many architectural decisions in the code, and it's more "we'll build the system that can stay upright with a minimum of pagerstorms" vs. "you build the system and throw it over the wall to us and then we'll keep it upright through our self-sacrificing heroism."
    - jsmthrowaway 12y ago
      Apple hires SREs who are actually sysadmins that occasionally code, complicating the title somewhat. This is not unique to them. nostrademons's explanation of SRE is the correct one, IMO. The architecture is key. Engineering has to be built to allow that. It has helped me in the past to say SREs are concerned more with the operation of a service than a group of machines offering a service; it's almost like a service operations developer. When a company thinks in terms of services and abstracts the machine away, i.e., containers, scheduling, Mesos, Omega/<unnamed>, intelligent CI/CD, service discovery, now you're getting into SRE territory instead of SA territory. The architecture involvement distinguishes SRE from devops for me. You should be able to trust SRE to build services, not just run engineering output. Teams that congeal out of Xooglers tend to preach SRE well, and there is the occasional company (Twitter and Foursquare come to mind) that applies the title and interacts with the team as intended.
    - Morgawr 12y ago
      For further reading, this is a good post: http://www.site-reliability-engineering.info/ http://www.site-reliability-engineering.info/
- yla92 12y ago
  In recent Google SREs AMA, they talked about how they mitigate DDoS attacks. http://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make/c82xd07 http://www.reddit.com/r/IAmA/comments/177267/we_are_the_goog... http://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make/c82tuld http://www.reddit.com/r/IAmA/comments/177267/we_are_the_goog...

nostrademons 12y ago

Google gets DDoSed all the time. You don't hear about it because, well, the DDoS SREs are very, very good at what they do.

mjdesa 12y ago
SREs?
- deleted 12y ago
  [deleted]
- detaro 12y ago
  Site Reliability Engineers
- nostrademons 12y ago
  Site Reliability Engineer. It's a Google (+Facebook)-specific title that is sort of like a sysadmin or devops, but instead of keeping the system up, they write code that keeps the system up. They also have a different negotiating position vs. engineering than in many other companies, eg. SREs have veto power over many architectural decisions in the code, and it's more "we'll build the system that can stay upright with a minimum of pagerstorms" vs. "you build the system and throw it over the wall to us and then we'll keep it upright through our self-sacrificing heroism."
  - jsmthrowaway 12y ago
    Apple hires SREs who are actually sysadmins that occasionally code, complicating the title somewhat. This is not unique to them. nostrademons's explanation of SRE is the correct one, IMO. The architecture is key. Engineering has to be built to allow that. It has helped me in the past to say SREs are concerned more with the operation of a service than a group of machines offering a service; it's almost like a service operations developer. When a company thinks in terms of services and abstracts the machine away, i.e., containers, scheduling, Mesos, Omega/<unnamed>, intelligent CI/CD, service discovery, now you're getting into SRE territory instead of SA territory. The architecture involvement distinguishes SRE from devops for me. You should be able to trust SRE to build services, not just run engineering output. Teams that congeal out of Xooglers tend to preach SRE well, and there is the occasional company (Twitter and Foursquare come to mind) that applies the title and interacts with the team as intended.
  - Morgawr 12y ago
    For further reading, this is a good post: http://www.site-reliability-engineering.info/ http://www.site-reliability-engineering.info/
yla92 12y ago
In recent Google SREs AMA, they talked about how they mitigate DDoS attacks. http://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make/c82xd07 http://www.reddit.com/r/IAmA/comments/177267/we_are_the_goog... http://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make/c82tuld http://www.reddit.com/r/IAmA/comments/177267/we_are_the_goog...