As a Software Engineer with 5+ years of experience, I know:
MySQL
PostgreSQL
SQLite
MongoDB
DynamoDB
Cassandra
LevelDB
RabbitMQ
Redis
Docker
Linux
Python
Bash
JS
HTML
CSS
As a Senior Software Engineer with 10+ years of experience, you should know:
MySQL
PostgreSQL
SQLite
MongoDB
DynamoDB
Cassandra
LevelDB
RabbitMQ
Kafka
Redis
Docker
K8S
Nix
Linux
C
Python
Bash
JS
HTML
CSS
JIRA
@Gviev@TheGridPost This one is more resource critical, no time to mistakes or recurring downtime as Businesses can loose millions of inflow and customers that will never come back, go and ask https://t.co/30d39qMhCL they'll explain to you what happens when your server keeps getting downtime
@Hussain_Joe@TosinOlugbenga - better for poor connection or low end device which helps reduce latency on slow network provider like Glo network.
- it fetches exactly what you need no redundancy
@Hussain_Joe@TosinOlugbenga Okay what I mean is for a Fullstack service with mobile app first approach, my best recommendation is to go with Graphql + Rest API for webhooks and other controllers that might go hard implementing using gql, my reason behind these are :
@Hussain_Joe@TosinOlugbenga With GQL you get
- fewer network requests (mobile apps usually needs data from multiple endpoints which leads to too many requests to get relational fields that are not directly tied to a schema etc..) gql solves this, one request gets all relations you need, you just select
@echo_vick Yeah very common, it's a latency issue from your network provider, same thing happens when your server tenant is hosted on an area or cloud with high latency for your provider, it won't open or some of your users using that provider won't be able to access your app
@hasantoxr It's Only a matter of time, don't build or rely your key feature around another enterprise infrastructure without a proper approach, tomorrow if telegram takes out that feature or blocks it endpoints you're fucked fr