Skip to main content

The post-office & the postman

If we were to talk about old messaging system where there exist post-office, postman & mailbox. each component had its own functionality that we looked for when trying to visualize how those component where to interact in a computerized version.

Simple scenario:
  1. Mail is added in mail box
  2. Postman arrive pick mails from his area mailboxes and take them to the post-office.
  3. Post-office organize mails by areas.
    1. Postman takes mails related to his area "distribute it in mailboxes".
    2. A person can go to post-office and  pick his own mail "in case of failure or wishes for early delivery".

Mapping in a computerized version:
  • Scenario: Observer design pattern which can use push or pull scenario, to inform those whom are registered for an event about its occurrence.
  • Component:
    • Post-Office = Message-Broker
    • Post-Office-Box = Message-Storage-Validity
    • Mailbox = Topic/Queue
    • Postman !!! where's the postman ?
Apache kafka act as a message broker which decouple message processing from publisher, also it can buffer unprocessed message, it follow pull data scenario "Consumer pull data". below is kafka capabilities:
  • publish / subscribe: act as a messaging system Topic / Queue.
  • Store stream: act as a storage system that can keep data for 2 day "configurable".
  • Process stream: act as a decorator design pattern.
Apache flume act as the post-man, which will deliver the event from a point to another, it follow push data scenario, below is flume capabilities:
  • deliver data from a point "source" to another "sink" (can be configured to push data to a port).
  • Modify or drop events in the flow "act as a decorator".
  • can store data in a partitions ( /dataDir/year=%y/  ).

Comments

Post a Comment

Popular posts from this blog

Not all Ps sting

  If someone meant to say Ps and pronounce it Bees. would this confuse you :). Ps is for the P that is the start of Properties and Practice Each application should have some properties and follow certain practices. Properties: Scalable, Scale = Increase workload (horizontally scaling) Statless, no state should be shared among different application instances,  Concurrency, concurrent processing = Threads. Loosely coupled, decompose the system into modules, each has minimal dependencies on each other "modularization", encapsulating code that changes together "High cohesion".  API first, Interfaces, implementation can be changed without affecting other application. favor distribution of work across different teams.  Backing Services, "DB, SMTP, FTP ..." , treating them as attached resources, meaning they can easily be changed. Manageable, changing the internal state and O/P via external I/P,  Also regarding updating the application up while keeping the overal
Post a Comment
Read more

String literal pool

I'm used to use String .format() when constructing a SQL statement, and a friend I knew likes to concatenate saying :"it's more readable to me". So String Objects are immutable, meaning that once they are created, they can't be altered. Concatenating 2 strings doesn't modify either Strings instead, it creates a new String "old ones are added to the string pool". String literals always have a reference to them in String Literal Pool, therefore not eligible for garbage collection. to concatenate use StringBuffer (Synchronized) or StringBuilder (not Synchronized) As both uses an internal array "so that new String Objects are not created". String literal Pool : String are stored in pool and before creating a new string  literals, compiler checks if such string already defined "used to optimize and save space". String literals : a sequence of characters between quotation marks. 
2 comments
Read more