Skip to main content

Banana Monkey Jungle

Why functional over OO?

https://medium.com/@cscalfani/goodbye-object-oriented-programming-a59cda4c0e53

Inheritance

Banana Monkey Jungle
The diamond relationship
Fragile parent class
Categorical (Taxonomy) v. Containment (or Exclusive Ownership) Hierarchies

Encapsulation

Object passed by reference to an Object Constructor is not safe
Deep cloning
MC Hammer v. Immutability
Global Scope

Polymorphism


https://www.cs.utexas.edu/~mitra/csSummer2013/cs312/lectures/interfaces.html

Design by Behavior not Data

Comments

Popular posts from this blog

Microservices Design Patterns

functional decomposition or domain-driven design well-defined interfaces  explicitly published interface  single responsibility principle potentially polyglot http://blog.arungupta.me/microservice-design-patterns/ http://blog.arungupta.me/microservices-monoliths-noops/ https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/ three-tier architecture — presentation, application, data vs. 4 tier -- client, delivery, aggregation, services

JSON stores and Aggregation for system logs and audit trail. Stop logging with format strings!

This first article explains why you might want to store logs and BI data in a machine readable format. https://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/ The second two get at how you might do that and be able to transition/re-purpose your existing relational stores into a cloud based scalable framework.  http://docs.mongodb.org/ecosystem/tutorial/use-aggregation-framework-with-java-driver/ http://www.bityota.com/3-steps-to-analytics-on-mongodb/ Logging might present a relatively low profile target for schema-less implementation and give you a chance to expose your organization to an important technology for modern web development. With your foot in the door you might convince them to add usage auditing and before you know it you are doing up front analysis on usage in front of your next project.