I rarely see the classical three-tier architecture in the wild; I frequently see a different architecture.
I don't know this architecture's name. Do you?
The "three-tier architecture" has been the reference pattern for Internet services:
See Keycloak Documentation for more details.
| kubectl get po --all-namespaces | grep Evicted | awk '{print $2, "--namespace", $1}' | xargs kubectl delete pod | 
| #!/usr/bin/env python3 | |
| """ | |
| Import/Export tool for Consul Key-Value storage. | |
| If your server has ACL enabled, | |
| be sure to export CONSUL_HTTP_TOKEN env variable or use -t to provide a token | |
| Usage: | |
| Export KV storage decoding values | 
This extension was developed as part of the jsonapi module for Drupal.
The JSON API specification is agnostic about how a server implements filtering strategies. In fact, the spec says:
Note: JSON API is agnostic about the strategies supported by a server. The
filterquery parameter can be used as the basis for any number of filtering strategies.
| # Stop all containers | |
| docker stop `docker ps -qa` | |
| # Remove all containers | |
| docker rm `docker ps -qa` | |
| # Remove all images | |
| docker rmi -f `docker images -qa ` | |
| # Remove all volumes | 
Picking the right architecture = Picking the right battles + Managing trade-offs
| -- show running queries (pre 9.2) | |
| SELECT procpid, age(clock_timestamp(), query_start), usename, current_query | |
| FROM pg_stat_activity | |
| WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' | |
| ORDER BY query_start desc; | |
| -- show running queries (9.2) | |
| SELECT pid, age(clock_timestamp(), query_start), usename, query | |
| FROM pg_stat_activity | |
| WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' |