Data-Intensive Applications Series :: Chapter I – Reliable, scalable, and maintainable applications

Hi there,

Thank you for visiting my blog!

The purpose of this blog is to record my journey as I learn about Designing Data-Intensive Applications by Martin Kleppmann and to share the lessons I learned with you!

My plan is to read a chapter every weekend, write detailed notes (which will always be included with my blog), and share a summary of the most important takeaways with you!

The first chapter, Reliable, scalable, and maintainable applications is very informative! I love the way the author explains concepts for data systems and shares examples of how developers can design apps while considering nonfunctional requirements in the early stages of the Systems Development Life Cycle. My main takeaway from the 1st Chapter is: Even if your application is small, always consider reliability, scalability, and maintainability in your design. Your app will not survive without these principles.

Take a look at my notes for more details.

Happy to start this “data trip” with you!

designing-data-intensive-applicationsDownload

2 thoughts on “Data-Intensive Applications Series :: Chapter I – Reliable, scalable, and maintainable applications”

  1. Good luck with it, sound like a great idea to share and discuss knowledge (I will take a look at the look)

    In regard to reliability, scalability, and maintainability, you think is a good idea? Because sometimes we build things only to prove concept (POC, fast prototype, to pitch to some investors) and for this kind of application/system you think it is a good idea to invest a lot of time in this quality attribute? Because they are short life systems.

    Liked by 1 person

    Reply

    1. Hi @dfana,

      Thank you for your comment!

      Yes, it is always a good idea to build things considering the nonfunctional requirements (reliability, scalability, and maintainability) in your design. You don’t have to implement them for the prototype, but you have to add them in your design plan.

      Any new software application must aim to be successful, this means growing (number of users, downloads, clients, etc.) and adapting (new environment, markets, policies, etc.) with the time. Showing to the investors that you are considering the nonfunctional requirements in your design will make them think that you are sure that your product will be successful.

      Regards,

      Dani

      Like

      Reply

Leave a comment