Nil Seri – Medium

Published in

·Nov 28

Firebase Web Push Notification With Go and Angular

Implementation of Firebase Web Push Notifications for Backend with Go and Frontend with Angular Push messages and notifications are two separate but complementary technologies. Push is the technology for sending messages from your server to users even when they’re not actively using your website. For off-site notifications, your server doesn’t…

Firebase

8 min read

Firebase

8 min read

Nov 26

Notify Users With the New Version of Your Angular App

Check for App Version Updates with Service Worker in Angular Receiving live updates Imagine an application such as an e-mail client which stays open for the whole working day. How do we publish a critical update in this situation? We cannot expect users to periodically refresh the page. Angular has provided us with…

Angular

9 min read

Angular

9 min read

Published in

Stackademic

·Nov 26

Cache Busting in Angular

Cache Busting and Lazy Loading preloadingStrategy What is Cache Busting? If you make an update to your site, since the cached version of the file is stored in your visitors’ browsers, they may be unable to see the changes made. This is due to the fact that a visitor’s browser will locally store a…

Angular

4 min read

Angular

4 min read

Nov 16

System Design Interview — Study Notes XII — Designing Data Intensive Applications Book Notes

Notes on Concepts & Components to be used in a System Design Interview Chapter 11 — Stream Processing To reduce the delay (as in batch processes), we can run the processing more frequently — processing a second’s worth of data at the end of every second — or even continuously, abandoning the fixed time slices…

System Design Interview

19 min read

System Design Interview

19 min read

Nov 15

System Design Interview — Study Notes XI — Designing Data Intensive Applications Book Notes

Notes on Concepts & Components to be used in a System Design Interview Chapter 9 — Consistency and Consensus Consistency Guarantees Inconsistencies occur no matter what replication method the database uses (single-leader, multi-leader, or leaderless replication). Most replicated databases provide at least eventual consistency. A better name for eventual consistency may be convergence — as we expect all replicas…

System Design Interview

20 min read

System Design Interview

20 min read

Nov 5

System Design Interview — Study Notes X — Designing Data Intensive Applications Book Notes

Notes on Concepts & Components to be used in a System Design Interview Chapter 8 — The Trouble with Distributed Systems Faults and Partial Failures partial failover — some parts of the system that are broken in some unpredictable way, even though other parts of the system are working fine. They are nondeterministic. Cloud Computing and Supercomputing high-performance computing (HPC) — for computationally intensive scientific computing…

System Design Interview

14 min read

System Design Interview

14 min read

Nov 5

System Design Interview — Study Notes IX— Designing Data Intensive Applications Book Notes

Notes on Concepts & Components to be used in a System Design Interview Chapter 7 — Transactions Transaction — a way for an application to group several reads and writes together into a logical unit. Either the entire transaction succeeds (commit) or it fails (abort, rollback). If it fails, the application can safely retry…

System Design Interview

20 min read

System Design Interview

20 min read

Nov 1

System Design Interview — Study Notes VIII — Designing Data Intensive Applications Book Notes

Notes on Concepts & Components to be used in a System Design Interview Chapter 6— Partitioning Sharding — or very large datasets, or very high query throughput; need to break the data up into partitions. Different partitions can be placed on different nodes in a shared-nothing cluster. …

System Design Interview

8 min read

System Design Interview

8 min read

Oct 31

System Design Interview — Study Notes VII — Designing Data Intensive Applications Book Notes

Notes on Concepts & Components to be used in a System Design Interview Chapter 5 — Replication Replication: keeping a copy of the same data on multiple machines that are connected via a network. - Data geographically close to users; to reduce latency - In case of failure; to increase availability - Scale out the number of…

System Design Interview

17 min read

System Design Interview

17 min read

Oct 29

System Design Interview — Study Notes VI — Designing Data Intensive Applications Book Notes

Notes on Concepts & Components to be used in a System Design Interview Part II — Distributed Data Scalability: data volume, read load, write load grows bigger than a single machine can handle — spread the load across multiple machines. …

System Design Interview

2 min read

System Design Interview

2 min read