Let's start discussing how my 3rd day of #100daysofcode went. I focussed more on the system design concepts and a bit of cloud fundamentals.
- Strong vs Eventual Consistency: We talked about the CAP theorem on 1st day of this challenge, this is somehow relatable to that theorem. In the case of a distributed system having multiple data stores, you can either offer Strong Consistency (with high latency) or Eventual Consistency(with low latency). Let me explain what I’m trying to prove here. If the data of one system is modified there are two scenarios, i.e. Update the data in every datastore instantly to maintain consistency resulting in high latency at the update time, or update the data asynchronously resulting in low latency but the chance of returning stale data would be there. Therefore, Strong Consistency offers up-to-date data but at the cost of high latency. While Eventual consistency offers low latency but may reply to read requests with stale data since all nodes of the database may not have the updated data.
- REST vs RPC: Both of them are architectural styles in API design. RPCs allow users to call functions on remote servers as if they were local to their server. Whereas in REST we allow to fetch and modify data on the remote servers on requesting and sending data. In summary, RPC offers a more direct approach for function calls, while REST provides a standardized and web-friendly way to interact with remote data and resources. The choice depends on your specific needs for control, performance, and interoperability.
- AWS Lambda: Rohit Sharma was rewriting the record books with his phenomenal 264-run inning, leaving Sri Lankan bowlers speechless. Little did the world know, another kind of record-breaking was happening behind the scenes. AWS Lambda was launched on the very same day, November 13th, 2014, forever changing the cloud computing landscape with its serverless magic. Just like Rohit Sharma's batting that day, Lambda's impact has been nothing short of phenomenal, delivering on its promise like a six soaring over the boundary and disappearing into the crowd.?
I think that’s what made my 3rd Day of #100daysofcode. See ya on the 4th.
Let me know your suggestions as well and feel free to share any resources which can be helpful for my journey.