Usu

I have a few questions, though:

1. How does this work with mobile apps / single page applications APIs? I'm worried this would block legitimate users

2. Is it possible to enable/disable this feature on URLs patterns using page rules? I'm not seeing the option right now

3. Do blocked requests end up in the firewall logs? If so, how do we filter for it? Specific rule id?

4. Is there a way to enable it in log mode in order to evaluate the impact it would have?

We are a team of really smart people working in a very well funded startup trying to disrupt insurance in Italy by using technology as our main competitive advantage. We employ a micro service architecture (10s of them are in production atm), Docker and AWS.

Most of our micro services are written in Elixir, we also have some Ruby, Haskell, Python, Go and Rust in production besides a legacy Symfony 2 application, while on the front end side we are mainly using Elm.

We have a lot of automation in place, we run a pretty comprehensive test suite on Drone CI at every push and every developer can spin up QA environments that mirror our entire stack for a given feature branch (this is made possible by having all of our infrastructure managed through CloudFormation templates). All of this allows us to confidently deploy to production multiple times per day.

Our stack:

  AWS (a lot of services), CloudFlare
  OS: Amazon Linux
  EC2 instance number: from ~30 to ~100: we scale automatically a lot of times during the day and treat our infrastructure as immutable
  Infrastructure: CloudFormation + scripts
  CD: Drone CI, Docker (dev -> qa -> staging -> production)
  Container orchestration: AWS ECS
  DB: Aurora MySQL and PostgreSQL, Redshift, ElastiCache Redis, DynamoDB
  Monitoring: ELK, DataDog, New Relic, CloudWatch
  Team organization: small cross functional agile teams (every team has at least one person for all of these roles: backend engineer, frontend engineer, web designer, qa engineer, devops engineer)
  Backend languages: Elixir, PHP (we're phasing it out long term), Haskell, Python, Rust, Ruby, Go
  Frontend languages: Elm, Javascript

  Micro service oriented architecture
  Functional reactive programming
  Event sourcing (CQRS)
  Actor model
  Agile (Scrum)
  Domain-driven Design (DDD)

We are a team of really smart people working in a very well funded startup trying to disrupt insurance in Italy by using technology as our main competitive advantage. We employ a micro service architecture (10s of them are in production atm), Docker and AWS.

Most of our micro services are written in Elixir, we also have some Ruby, Haskell, Python and Rust in production besides a legacy Symfony 2 application, while on the front end side we are mainly using Elm.

We have a lot of automation in place, we run a pretty comprehensive test suite on Drone CI at every push and every developer can spin up QA environments that mirror our entire stack for a given feature branch (this is made possible by having all of our infrastructure managed through CloudFormation templates). All of this allows us to confidently deploy to production multiple times per day.

Our stack:

  AWS (a lot of services), CloudFlare
  OS: Amazon Linux
  EC2 instance number: from ~30 to ~100: we scale automatically a lot of times during the day and treat our infrastructure as immutable
  Infrastructure: CloudFormation + scripts
  CD: Drone CI, Docker (dev -> qa -> staging -> production)
  Container orchestration: AWS ECS
  DB: Aurora MySQL and PostgreSQL, Redshift, ElastiCache Redis, DynamoDB
  Monitoring: ELK, DataDog, New Relic, CloudWatch
  Team organization: small cross functional agile teams (every team has at least one person for all of these roles: backend engineer, frontend engineer, web designer, qa engineer, devops engineer)
  Backend languages: Elixir, PHP (we're phasing it out long term), Haskell, Python, Rust, Ruby
  Frontend languages: Elm, Javascript

We're a team of really smart people working in a very well funded startup trying to disrupt insurance in Italy by using technology as our main competitive advantage.

We employ a micro service architecture (10s of them are in production atm), Docker and AWS.

Most of our micro services are written in Elixir (our language of choice for all the new stuff), we also have some Ruby, Haskell, Python and Rust in production besides a legacy Symfony 2 application.

On the front end side we're mainly using Elm.

We have a lot of automation in place, we run a pretty comprehensive test suite on Drone CI at every push and every developer can spin up QA environments that mirror our entire stack for a given feature branch (this is made possible by having all of our infrastructure managed through CloudFormation templates).

All of this allows us to confidently deploy to production multiple times per day.

Our stack:

  AWS (a lot of services), CloudFlare
  OS: Amazon Linux
  EC2 instance number: from ~30 to ~100: we scale automatically a lot of times during the day and treat our infrastructure as immutable
  Infrastructure: CloudFormation + scripts
  CD: Drone CI, Docker (dev -> qa -> staging -> production)
  Container orchestration: AWS ECS
  DB: Aurora MySQL and PostgreSQL, Redshift, ElastiCache Redis, DynamoDB
  Monitoring: ELK, DataDog, New Relic, CloudWatch
  Team organization: small cross functional agile teams (every team has at least one person for all of these roles: backend engineer, frontend engineer, web designer, qa engineer, devops engineer)
  Backend languages: Elixir, PHP (we're phasing it out long term), Haskell, Python, Rust, Ruby
  Frontend languages: Elm, Javascript

I created it because I was annoyed with the lack of notifications provided by GitHub for some events like new people following you or starring/forking your projects. A lot of people are now using it and that makes me happy even though I'm losing money by keeping it online.