Some simple questions that may need some thinking



In this blog post, I have put down some questions that are kind of random questions but they are important questions whenever you develop any software. The answers to these questions depend on the context and require a lot of experience and knowledge to make a good judgment.
  • Where should I store media images for my web application? 
    • Inside web application
    • On a web server 
    • In a database 
    • On a cloud 
  • Where should I write an application log messages?
    • In a local file 
    • Syslog
    • RDBMS
    • NoSQL database
  • Where should a client store authentication token?
    • Cookies
    • Local Storage
  • What kind of authentication mechanism should I use for my web application?
    • Stateless session tokens
    • Session Ids
  • What should be the format of log file messages?
    • Free text string format
    • Key-Value Pairs string format
    • JSON
  • What should I use for notifying a service for some action? 
    • A message queue
    • A table in a shared database
  • Can I use a single load balancer to handle the load of hundreds of application servers behind it?
  • For my new project which database is suitable?
    • RDBMS
    • NoSQL
  • Which load balancer should I use?
    • Apache
    • Nginx
    • HAProxy
    • Hardware-based
  • What is the difference between 
    • Fault tolerance
    • Availability
    • Reliability
  • I need to store my log files in a storage so that they can be analyzed later. Where should I store them? 
    • Hadoop
    • Cassandra
    • HBase
  • What framework should I use for decoupling my services from each other?
    • OSGI Framework
    • Micro Services
  • How do I decide if my REST API should take a request variable as
    • A path param
    • A query param
  • I want to keep my business logic loosely coupled with a particular component implementation. What pattern should I use?
    • Dependency Injection
    • Factory Pattern

Comments

Post a Comment

Popular posts from this blog

Apache Hadoop Ecosystem

Image
Hadoop HDFS - 2007 - A distributed file system for reliably storing huge amounts of unstructured, semi-structured and structured data in the form of files.  Hadoop MapReduce - 2007 - A distributed algorithm framework for the parallel processing of large datasets on HDFS filesystem. It runs on Hadoop cluster but also supports other database formats like Cassandra and HBase.  Cassandra - 2008 - A key-value pair NoSQL database, with column family data representation and asynchronous masterless replication.  HBase - 2008 - A key-value pair NoSQL database, with column family data representation, with master-slave replication. It uses HDFS as underlying storage.  Zookeeper - 2008 - A distributed coordination service for distributed applications. It is based on Paxos algorithm variant called Zab.  Pig - 2009 - Pig is a scripting interface over MapReduce for developers who prefer scripting interface over native Java MapReduce programming.  Hive ...
Read more

Big Data After The Internet

Image
Till 1995 most of the people did not know about the internet. It was hard to use, till the Netscape browser arrived and its famous IPO happened. The arrival of Netscape meant anyone could create material and anyone with a connection could view it. Internet's popularity resulted in mushrooming of websites like AOL, MSN, Yahoo, CNN, Napster and so many more. They  provided free information sharing services like emails, chats, photograph sharing, video sharing, blogging, news, weather, music, games etc. These sites were generating, collecting and sharing an enormous amount of data, for the people all over the globe. There were, of course, new generation e-commerce companies like Amazon and eBay that also contributed to the overall information available, but sharing of information was not at the core of their strategy.   Why this phenomenon of information sharing noteworthy? There are two good reasons:  The data on the Internet was freely available to everyone...
Read more