diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..507e5ec
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,251 @@
+
+# Created by https://www.gitignore.io/api/node,windows,macos,linux,sublimetext,emacs,vim,visualstudiocode
+
+### Emacs ###
+# -*- mode: gitignore; -*-
+*~
+\#*\#
+/.emacs.desktop
+/.emacs.desktop.lock
+*.elc
+auto-save-list
+tramp
+.\#*
+
+# Org-mode
+.org-id-locations
+*_archive
+
+# flymake-mode
+*_flymake.*
+
+# eshell files
+/eshell/history
+/eshell/lastdir
+
+# elpa packages
+/elpa/
+
+# reftex files
+*.rel
+
+# AUCTeX auto folder
+/auto/
+
+# cask packages
+.cask/
+dist/
+
+# Flycheck
+flycheck_*.el
+
+# server auth directory
+/server/
+
+# projectiles files
+.projectile
+
+# directory configuration
+.dir-locals.el
+
+### Linux ###
+
+# temporary files which can be created if a process still has a handle open of a deleted file
+.fuse_hidden*
+
+# KDE directory preferences
+.directory
+
+# Linux trash folder which might appear on any partition or disk
+.Trash-*
+
+# .nfs files are created when an open file is removed but is still being accessed
+.nfs*
+
+### macOS ###
+# General
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# Icon must end with two \r
+Icon
+
+# Thumbnails
+._*
+
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+### Node ###
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# TypeScript v1 declaration files
+typings/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+
+# next.js build output
+.next
+
+# nuxt.js build output
+.nuxt
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless
+
+### SublimeText ###
+# Cache files for Sublime Text
+*.tmlanguage.cache
+*.tmPreferences.cache
+*.stTheme.cache
+
+# Workspace files are user-specific
+*.sublime-workspace
+
+# Project files should be checked into the repository, unless a significant
+# proportion of contributors will probably not be using Sublime Text
+# *.sublime-project
+
+# SFTP configuration file
+sftp-config.json
+
+# Package control specific files
+Package Control.last-run
+Package Control.ca-list
+Package Control.ca-bundle
+Package Control.system-ca-bundle
+Package Control.cache/
+Package Control.ca-certs/
+Package Control.merged-ca-bundle
+Package Control.user-ca-bundle
+oscrypto-ca-bundle.crt
+bh_unicode_properties.cache
+
+# Sublime-github package stores a github token in this file
+# https://packagecontrol.io/packages/sublime-github
+GitHub.sublime-settings
+
+### Vim ###
+# Swap
+[._]*.s[a-v][a-z]
+[._]*.sw[a-p]
+[._]s[a-rt-v][a-z]
+[._]ss[a-gi-z]
+[._]sw[a-p]
+
+# Session
+Session.vim
+
+# Temporary
+.netrwhist
+# Auto-generated tag files
+tags
+# Persistent undo
+[._]*.un~
+
+### VisualStudioCode ###
+.vscode/*
+!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+!.vscode/extensions.json
+
+### Windows ###
+# Windows thumbnail cache files
+Thumbs.db
+ehthumbs.db
+ehthumbs_vista.db
+
+# Dump file
+*.stackdump
+
+# Folder config file
+[Dd]esktop.ini
+
+# Recycle Bin used on file shares
+$RECYCLE.BIN/
+
+# Windows Installer files
+*.cab
+*.msi
+*.msix
+*.msm
+*.msp
+
+# Windows shortcuts
+*.lnk
+
+
+# End of https://www.gitignore.io/api/node,windows,macos,linux,sublimetext,emacs,vim,visualstudiocode
diff --git a/.idea/modules.xml b/.idea/modules.xml
new file mode 100644
index 0000000..7158840
--- /dev/null
+++ b/.idea/modules.xml
@@ -0,0 +1,8 @@
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/.idea/slides-marp-master.iml b/.idea/slides-marp-master.iml
new file mode 100644
index 0000000..c956989
--- /dev/null
+++ b/.idea/slides-marp-master.iml
@@ -0,0 +1,8 @@
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/.idea/vcs.xml b/.idea/vcs.xml
new file mode 100644
index 0000000..94a25f7
--- /dev/null
+++ b/.idea/vcs.xml
@@ -0,0 +1,6 @@
+
+
+
+
+
+
\ No newline at end of file
diff --git a/.idea/workspace.xml b/.idea/workspace.xml
new file mode 100644
index 0000000..e9e4499
--- /dev/null
+++ b/.idea/workspace.xml
@@ -0,0 +1,73 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 1626402788000
+
+
+ 1626402788000
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/.nvmrc b/.nvmrc
new file mode 100644
index 0000000..71b4c49
--- /dev/null
+++ b/.nvmrc
@@ -0,0 +1 @@
+12.18.2
diff --git a/.puppeteer.js b/.puppeteer.js
new file mode 100644
index 0000000..122c215
--- /dev/null
+++ b/.puppeteer.js
@@ -0,0 +1,2 @@
+// Output installed Chromium path by puppeteer
+console.log(require('puppeteer').executablePath())
diff --git a/PATTERNS.MD b/PATTERNS.MD
new file mode 100644
index 0000000..dc61bc3
--- /dev/null
+++ b/PATTERNS.MD
@@ -0,0 +1,229 @@
+---
+marp: true
+title: Design Principles and Patterns
+description: Design Principles and Patterns PaaC
+theme: gaia
+size: 16:9
+paginate: true
+_paginate: false
+header: ":copyright: OSS"
+footer: "PaaC Rocks :heart:"
+---
+
+
+
+
+# Design Principles & Patterns
+
+
+##### Dean.Jain - Staff Engineer @Amex
+
+
+
+---
+
+
+
+
+#### Agenda
+- Intro : What
+- History : When
+- Types : What All
+- Details : How and Why
+- Discussion Q/A ?
+
+
+
+
+---
+##### Software development is a learning process; working code is a side effect!
+
+
+# Key Design Principles :key:
+
+- (**KISS**) Keep It Simple Stupid :kiss: -> Do The **Simplest** Thing That Could Possibly Work
+- **YAGNI** :do_not_litter: -> You Arent Gonna Need It
+- **DRY** :repeat: -> Dont Repeat Yourself (Single Source of Truth)
+- **Code For The Maintainer** :green_book: -> Always code and comment in such a way that if someone a few notches junior checks up the code, they will take pleasure in reading and learning from it.
+- **Avoid Premature Optimization** :sweat_drops: -> Make It Work Make It Right Make It Fast
+- **Minimise Coupling** :couple: -> Coupling between modules/components is their degree of mutual interdependence; Lower coupling is better. In other words, coupling is the probability that code unit "B" will "break" after an unknown change to code unit "A".
+- **Maximise Cohesion** :handshake: -> Cohesion of a single module/component is the degree to which its responsibilities form a meaningful unit; higher cohesion is better.
+
+
+---
+
+
+
+#### SOLID Principles: :rock:
+
+* **SRP** states that a class should have exactly one responsibility
+* **OCP** - class (or function) should be open for extension but closed for modification
+* **LSP** states that if type S inherits from type T then both T and S should be interchangeable in functions that expect T.
+* **ISP** says to avoid writing monstrous interfaces that burden classes with responsibilities they don't need or want.
+* **DIP** - Instead of writing code that refers to actual classes, you should instead write code that refers to interfaces or perhaps abstract classes
+
+
+
+
+
+##### Q: How to Apply Design Principles??
+---
+
+### What’s a design pattern?
+- Design patterns are typical **solutions to commonly occurring problems** in software design. **They are like pre-made blueprints** that you can customize to solve a recurring design problem in your code.
+- The pattern is not a specific piece of code, but **a general concept for solving a particular problem. You can follow the pattern details and implement a solution that suits the realities of your own program**.
+- Design patterns are a **toolkit of tried and tested solutions to common problems** in software design.
+
+---
+
+
+
+
+
+#### History:
+- The concept of patterns was first described by Christopher Alexander in A Pattern Language: Towns, Buildings, Construction.
+- Erich Gamma, John Vlissides, Ralph Johnson, and Richard Helm In 1994, they published Design Patterns: Elements of Reusable Object-Oriented Software, in which they applied the concept of design patterns to programming.
+- The book **featured 23 patterns** solving various problems of object-oriented design and became a best-seller very quickly. Due to its lengthy name, people started to call it **“the book by the gang of four”** which was soon shortened to simply **“the GoF book”**.
+- Many patterns followed...
+
+
+---
+
+### Classification of Patterns:
+1. **Creational** patterns provide object creation mechanisms that increase flexibility and reuse of existing code.
+
+2. **Structural** patterns explain how to assemble objects and classes into larger structures, while keeping the structures flexible and efficient.
+
+3. **Behavioral** patterns take care of effective communication / assignment of responsibilities (algo) between objects.
+
+---
+
+
+
+---
+
+
+
+---
+
+
+
+---
+
+
+
+
+
+
+
+## Creational - Factory Method:
+Method, Provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created.
+
+### Creational - Abstract Factory
+Object, a super-factory which creates other factories, is also called as factory of factories. lets you produce families of related objects without specifying their concrete classes.
+
+### Creational - Builder
+Construct complex objects step by step (step-by-step initialization of many fields and nested objects). The pattern allows to produce different types and representations of an object using the same construction code.
+
+### Creational - Prototype
+lets you copy existing objects without making your code dependent on their classes. declares a common interface for all objects that support cloning. This interface lets you clone an object without coupling your code to the class of that object.
+
+### Creational - Singleton
+lets you ensure that a class has only one instance, while providing a global access point to this instance.
+
+
+---
+
+### Structural - Adapter
+allows objects with incompatible interfaces to collaborate (XML -> JSON Adaptor)
+
+### Structural - Bridge
+lets you split a large class or a set of closely related classes into two separate hierarchies (abstraction and implementation) which can be developed independently of each other.
+
+### Structural - Composite
+lets you compose objects into tree structures and then work with these structures as if they were individual objects. Composite class holds a collection of smaller/individual objects.
+
+### Structural - Decorator
+lets you attach new behaviors to objects by placing these objects inside special wrapper objects that contain the old behaviors.
+
+### Structural - Facade
+provides a simplified interface to a library, a framework, or any other complex set of classes. Having a facade is handy when you need to integrate your app with a sophisticated library that has dozens of features, but you just need a tiny bit of its functionality.
+
+
+---
+
+### Structural - Flyweight
+lets you fit more objects into the available amount of RAM by sharing common parts (immutable) of state between multiple objects instead of keeping all of the data in each object.
+
+### Structural - Proxy
+lets you provide a substitute or placeholder for another object. A proxy controls access to the original object, allowing you to perform something either before or after the request gets through to the original object.
+
+---
+
+
+
+### Behavioral - Chain of Responsibility
+lets you pass requests along a chain of handlers. Upon receiving a request, each handler decides either to process the request or to pass it to the next handler in the chain.
+
+### Behavioral - Command
+turns a request into a stand-alone object that contains all information about the request. This transformation lets you pass requests as a method arguments, delay or queue a request’s execution, and support undoable operations.
+
+### Behavioral - Iterator
+lets you traverse elements of a collection without exposing its underlying representation (list, stack, tree, etc.), Iterators implement various traversal algorithms.
+
+### Behavioral - Mediator/Controller/Gateway
+lets you reduce chaotic dependencies between objects. The pattern restricts direct communications between the objects and forces them to collaborate only via a mediator/controller/gateway object.
+
+### Behavioral - Memento/Snapshot
+lets you save and restore the previous state of an object without revealing the details of its implementation (history of state).
+
+
+---
+
+
+
+### Behavioral - Observer/Event-Subscriber/Listener
+- lets you define a subscription mechanism to notify multiple objects about any events that happen to the object they’re observing.
+- The Observer pattern suggests that you add a subscription mechanism to the publisher class so individual objects can subscribe to or unsubscribe from a stream of events coming from that publisher.
+- this mechanism consists of 1) an array field for storing a list of references to subscriber objects and 2) several public methods which allow adding subscribers to and removing them from that list.
+
+### Behavioral - State
+lets an object alter its behavior when its internal state changes. It appears as if the object changed its class. extract all state-specific code into a set of distinct classes. As a result, you can add new states or change existing ones independently of each other, reducing the maintenance cost.
+
+### Behavioral - Strategy
+lets you define a family of algorithms, put each of them into a separate class, and make their objects interchangeable. take a class that does something specific in a lot of different ways and extract all of these algorithms into separate classes called strategies.
+
+### Behavioral - Template Method
+defines the skeleton of an algorithm in the superclass but lets subclasses override specific steps of the algorithm without changing its structure. break down an algorithm into a series of steps, turn these steps into methods, and put a series of calls to these methods inside a single template method. The steps may either be abstract, or have some default implementation. To use the algorithm, the client is supposed to provide its own subclass, implement all abstract steps, and override some of the optional ones if needed
+
+### Behavioral - Visitor
+lets you separate algorithms from the objects on which they operate. The Visitor pattern suggests that you place the new behavior into a separate class called visitor, instead of trying to integrate it into existing classes. The original object that had to perform the behavior is now passed to one of the visitor’s methods as an argument, providing the method access to all necessary data contained within the object.
+
+
+---
+
+
+
+- ### What do you guys think :ok_hand::blush:
+- ### Discussion :hand::unlock:
+- ### Questions :question::bulb:
+---
+
+
+
+##### Created by Dean Jain ([@dean.jain](https://github.com/deanjain))
+
+
+
+##### References:
+- https://refactoring.guru/design-patterns
+- https://foxlearn.com/design-patterns/what-are-design-patterns-431.html
+- https://en.wikipedia.org/wiki/Design_Patterns
+
+
+
+Powered by PaaC (Presentation as a Code) :heart::purple_heart::green_heart::blue_heart:
\ No newline at end of file
diff --git a/PATTERNS.html b/PATTERNS.html
new file mode 100644
index 0000000..1487a0f
--- /dev/null
+++ b/PATTERNS.html
@@ -0,0 +1,218 @@
+Design Principles and Patterns
This is presenter note. You can write down notes through HTML comment.
Scoped style
\ No newline at end of file
diff --git a/PITCHME.html b/PITCHME.html
new file mode 100644
index 0000000..b38dedf
--- /dev/null
+++ b/PITCHME.html
@@ -0,0 +1,139 @@
+Application Caching
This is presenter note. You can write down notes through HTML comment.
\ No newline at end of file
diff --git a/PITCHME.md b/PITCHME.md
new file mode 100644
index 0000000..b1fe7ca
--- /dev/null
+++ b/PITCHME.md
@@ -0,0 +1,109 @@
+---
+marp: true
+title: Application Caching
+description: Application Caching Presenation on Markdown
+theme: gaia
+size: 16:9
+paginate: true
+_paginate: false
+header: ":copyright: OSS"
+footer: "PaaC Rocks :blue_heart:"
+---
+
+
+
+# Application Caching
+
+Application Caching Presentation Using Markdown
+
+
+
+
+
+---
+
+
+#### Agenda
+- Introduction
+- Summary - The What
+- Features - What All
+- The How
+- The Why -> Pros and Cons
+- The When and where
+- Another How (to Get Started)
+- References (From Where)
+
+---
+
+#### Intro
+- Enable app layer in memory caching which can be used by any API / frameworks to cache data, and improve latency and load on DB
+
+- Integrate distributed embedded caching with our existing application with simple annotation in our spring applications
+---
+
+
+
+
+#### Features:
+- Easily integrate with JPA/Hibernate
+- Support for Relational DB / Joins
+- Support for TTL
+- Support for Cache - Aside strategy
+- Light weight and fits into small - pods
+- Minimal setup needed / Easy to use - learn
+- Distributed Caching - ideal case without a dedicated server
+
+---
+
+### Application Caching:
+There are two patterns of caching the data in application caching.
+
+1. ##### Caching Database Queries:
+- This is the most commonly used caching pattern. Whenever you query your database, your store the result dataset in the cache. Each result dataset will have a hashed version of the query as the cache key.
+- Every time you run the query, you first check if cache-key is already in the cache.
+- If it’s in the cache return it from there otherwise fetch the result from the database and store the result dataset in the cache for future queries.
+- The main issue with this pattern is the cache invalidation. It is hard to invalidate the cached result when you cache a complex query result. When one piece of data changes (for example, a table row) we need to invalidate all cached queries which include that row.
+
+
+
+---
+
+
+
+2. #### Caching Objects:
+- In objects caching pattern, you store the data as an object as you do in your application code (classes, instances, etc.).
+- Your class can assemble a dataset from your database and then you can store the instance of the class or the assembled dataset in the cache.
+- Some examples of objects that can be cached are User Sessions, Fully Rendered Web pages, Activity Streams, User Graph Data.
+
+---
+### Caching Update Strategy:
+
+1. Read-Through
+- In cache-aside, the application is responsible for fetching data from the data store and populating the cache. In read-through, this logic is usually supported by the library or stand-alone cache provider.
+- Unlike cache-aside, the data model in the read-through cache cannot be different than that of the database.
+- Read-through cache also works best for read-heavy workloads.
+- Read-through cache strategy is quite similar to cache-aside accept instead of managing both data store and the cache, delegates data store synchronization to the cache provider
+- Both cache-aside and read-through loads data lazily on the first read.
+
+
+---
+
+
+
+---
+
+
+
+- ### What do you guys think :ok_hand::blush:
+- ### Discussion :hand::unlock:
+- ### Questions :question::bulb:
+---
+
+
+
+##### Created by Dean Jain ([@dean.jain](https://github.com/deanjain))
+
+
+
+
+Powered by PaaC (Presentation as a Code) :heart::purple_heart::green_heart::blue_heart:
\ No newline at end of file
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..2301697
--- /dev/null
+++ b/README.md
@@ -0,0 +1,54 @@
+# PaaC - Presentation as a Code
+Presentation Using Markdown, Hosted on GitHub Pages :)
+
+### Creating presenations for your application and PaaC it like a geek, how codiful is that!
+
+Idea is to have the presentation built with simple mardown files and embed it within your repo, and demo it from same repo (github pages)!
+
+### Getting Started
+- Clone this Repo Template
+- Write your slide deck using [Marp](https://marpit.marp.app/) Markdown
+- Manage the content of slides in your own Git repo
+- Convert markdown to presentable html format using node/npx command
+- Commit html to git repo and enable github pages via settings tab
+- Blazingly fast delivery on your presentation via Github Pages
+- [Demo PaaC](./PITCHME.html)
+
+
+### PreReq
+- Install [Node.js 12+](https://nodejs.org/)
+- Clone this Repo (Template)
+
+### Preview deck
+
+[**Marp for VS Code**](https://marketplace.visualstudio.com/items?itemName=marp-team.marp-vscode) extension is the best partner for writing Marp slide deck with live preview.
+
+
+
+