artima.com principles-wiki.net github.com	Principles of Programming and Software design
lostechies.com wikipedia.org wikipedia.org wikipedia.org wikipedia.org	SOLID, YAGNI, KISS, DRY
swskilltree.org github.com	Catalog of design patterns
wikipedia.org wikipedia.org	List of software Architecture Styles and patterns Three-tier Multilayered architecture Hierarchical pattern Model-view-controller Microkernel Blackboard pattern Sensor-controller-actuator Presentation–abstraction–control
c2.com stackoverflow.com	GangOfFour design patterns Examples of GoF design patterns in Java classes Creational (CategoryCreationalPatterns) AbstractFactoryPattern BuilderPattern FactoryMethodPattern PrototypePattern SingletonPattern Structural (CategoryStructuralPatterns) AdapterPattern BridgePattern CompositePattern DecoratorPattern FacadePattern FlyweightPattern ProxyPattern Behavioral (CategoryBehavioralPatterns) ChainOfResponsibilityPattern CommandPattern InterpreterPattern IteratorPattern MediatorPattern MementoPattern ObserverPattern StatePattern StrategyPattern TemplateMethodPattern VisitorPattern
theartofscalability.com	The Importance of Scalability: Monolithic Architecture Microservice Maturity Model The Scale Cube (XYZ-CAP) X-axis: Running multiple Copies of an application behind a load balancer Y-axis: Splits the Application into multiple, different service Z-axis: Used to scale databases, Data is Partitioned (a.k.a. sharded)
infoq.com hpts.ws	Scalability Best Practices: Lessons from eBay
aosabook.org	The Architecture of Open Source Applications
slideshare.net	Facebook architecture for 600M users
scaledagileframework.com	Non Functional Requirements (NFR)
javapractices.com	"The JavaBeans pattern has serious disadvantages" - Joshua Bloch
infoq.com microservices.io martinfowler.com arungupta.me arungupta.me	Microservices Architecture and its benefit over Monolith Applications Domain Driven Design: it addresses, Big Ball of Mud Spaghetti Code Pejorative Code Single Responsibility Principle Explicitly Published Interface Independently Deploy, Upgrade, Scale, Replace Potentially Heterogeneous/Polyglot Light-weight Communication Related patterns, The Monolithic architecture is an alternative to the microservices architecture The API Gateway pattern defines how clients access services in microservices architecture The Client-side Discovery to route requests for a client to an available service instance The Server-side Discovery to route requests for a client to an available service instance The Single Service Pattern per Host for deployment strategies The Multiple Services per Host Pattern for deployment strategies The Database per Service pattern describes how each service has its own database The Microservice chassis pattern says build microservices to handle cross-cutting concerns
martinfowler.com github.com	Serverless Architecture. Backend as a Service (BAAS) & Functions as a Service (FAAS) Google Functions Amazon Lambda Azure Functions
12factor.net	The Twelve-Factor is a methodology for building SAS apps Codebase: One codebase tracked in revision control, many deploys Dependencies: Explicitly declare and isolate dependencies Config: Store config in the environment Baking services: Explicitly declare and isolate dependencies Build, release, run: Strictly separate build and run stages Processes: Execute the app as one or more stateless processes Port binding:Export services via port binding Concurrency: Scale out via the process model Disposability: Maximize robustness with fast startup and graceful shutdown Dev/prod parity: Keep development, staging, and production as similar as possible Logs: Treat logs as event streams Admin processes: One codebase tracked in revision control, many deploys
wikipedia.org	Software Engineering Best Practices for Reliability, Efficiency, Performance and Security Application architecture best practices Coding best practices Complexity of algorithms Compliance with Object-Oriented and structured programming best practices Component or pattern re-use ratio Modules should be Loosely Coupled (fanout, intermediaries) Error & exception handling (for all layers – user interface, logic & data) Multi-layer design compliance Avoid patterns that will lead to unexpected behaviors Compliance with SQL programming best practices Security best practices System functions access, access control to programs Input Validation, SQL Injection, Cross-Site Scripting Manages transaction level data integrity and consistency Appropriate interactions with expensive and/or remote resources Data access performance and data management Memory, network and disk space management Enforce homogeneous naming conventions as per technology stack recommendation Avoidance of Dependency Hell like situations during build and setup
wikipedia.org	Cargo cult programming
reactivemanifesto.org	Reactive menifesto (RREM) Responsive Resilient Elastic Message Driven
c2.com c2.com c2.com c2.com	Software Engineering philosophy Conceptual Integrity Egoless Programming Only Say Things That Can Be Heard Amorphous Blob Of Human Insensitivity
wikipedia.org	ACID is a set of properties of database transactions Atomicity Consistency Isolation Durability
wikipedia.org	Uniform access principle (UAP) Bertrand Meyer formulated the Uniform Access Principle that states: "All services offered by a module should be available through a uniform notation, which does not betray whether they are implemented through storage or through computation." In Scala, caller of fred.age doesn’t know whether age is implemented through a field or a method
acm.org	Why Domain Specific Language required
github.com	Software architect road map
github.com	A curated list of code katas
e-zest.net	Java Monitor Pattern for Multi-Thread application Useful to implement more than one Mutexes in your code
stackoverflow.com github.com	"Enforce the Singleton Property With a Private Constructor or an Enumerator" - Joshua Bloch
javapractices.com	"The JavaBeans pattern has serious disadvantages" - Joshua Bloch
informit.com	"Prefer primitives to boxed primitives and watch out for unintentional autoboxing" - Joshua Bloch
blogspot.com blogspot.com	The Telescoping Constructor Anti-Pattern. Fix it with Builder Pattern
stackoverflow.com stackoverflow.com blogspot.com	Inheritance/Composition/Aggregation Composition stresses on mutual existence Aggregation does not require mutual existence
stackoverflow.com	Lexical/Static and Dynamic/Public scoping
stackoverflow.com	Statically typed and Dynamically typed languages
stackexchange.com haskell.org	Concurrency vs. Parallelism Asynchronous vs. Synchronous Non-blocking vs. Blocking Deadlock vs. Starvation vs. Live-lock
leguen.ca blogspot.com	Data Mapper Pattern Data Mapper Pattern vs Active Record Pattern
wikipedia.org	External sorting relates to class of sorting algorithms that can handle massive amounts of data
liquibase.org	Source control for data base
wordpress.org	Kimball and Inmon Data Warehouse Models
c2.com	Denormalization Is Ok
martinfowler.com github.com	Command Query Responsibility Segregation (CQRS) Design pattern and Axon framework
ezinearticles.com	OLTP: Systems which serve transactions with suppliers, partners and customers, as well as internal DSS : System which helps in understanding current state and taking facts based informed decisions
microsoft.com	Comparison of the Top Four Enterprise-Architecture Methodologies
github.com	How to design large-scale systems
stackoverflow.com	Difference between Fine and Coarse grained records
gktoday.in	Difference in Green Field Projects and Brownfield Projects
reactive-streams.org	Reactive Streams
sourcemaking.com	Simplified Design Patterns
medium.com	ISO/IEC 9126 Software engineering product quality standard
foldingburritos.com optimizely.com	Product Prioritization Techniques
hackernoon.com	Blue/Green Infrastructure Architecture
datawarehouse4u.info	Slowly Changing Dimensions (SCD)
choosealicense.com	Choosing a suitable open source license
github.com	Maturity Models
github.com	What is a Software Architect
techopedia.com zetta.net	Mean Time Between Repair (MTBR) and Mean Time to Data Loss (MTTDL)
github.com	Awesome Scalability Consistency Patterns Availability Patterns Back of the Envelope Calculations to quickly develop a Ballpark Figure
medium.com	An Approach to Application Modernization: Discovery and Assessment Phase
druva.com	Disaster Recovery Return Point Objective (RPO) designates the data that will be lost during network downtime Return Time Objective (RTO) is the time system takes to recover after business disruption Example: If the last data copy is from 18 hours ago, and RPO is 20 hours then we are good
amazon.com	AWS Prescriptive Guidance
amazon.com	AWS Security Baseline Playbook
martinfowler.com	Transitional Architecture: Software elements installed to ease the displacement of a legacy system by a modern system
matillion.com	Data Vault vs Star Schema vs Third Normal Form: Which Data Model to Use?
talend.com	Data Model Design and Best Practices
amazon.com	AWS Architectures: Kimball and Inmon approach
analyticsvidhya.com	A Guide to Data Modelling Techniques in Modern Data Warehouse (Normalization/ Denormalization/ Immon/ Kimball/ Data Vault)
legaltechnologyhub.com
blogspot.com	LIFESPAR cloud architecture principles
legaltechnologyhub.com	POC >> Pilot >> Full Project
bytebytego.com	Big Bang, Rolling deployment, Blue-Green Deployment, Canary Deployment, Feature Toggle
bytebytego.com	Four strategies: (a) pilot system, (b) immediate cutover, (c) Parallel cutover, and (d) phased cutover Once the pilot performs satisfactorily, migrate the remainder system in an immediate, phased, or parallel manner Immediate cutover offers low cost yet high risk Parallel cutover is a high cost strategy but features low risk Phased cutover offers a compromise in terms of medium cost and risk
blogspot.com	LIFESPAR cloud architecture principles