Skip to content

Commit

Permalink
theory terms
Browse files Browse the repository at this point in the history
  • Loading branch information
@togakangaroo
togakangaroo committed Sep 14, 2018
1 parent a13c216 commit 03c9920
Showing 1 changed file with 12 additions and 12 deletions.
24 changes: 12 additions & 12 deletions terms.org
View file
Original file line number Diff line number Diff line change
Expand Up @@ -503,18 +503,18 @@ Look at [[https://glossarytech.com/terms/software_architecture/page2][Glossary T
| Loose coupling | Code design guideline that code should be grouped into components and that different components should not depend on each other directly. |
| high cohesion | Code design guideline that code should be grouped into components and that conceptually related code should be grouped together. |
| Convention over configuration | Style of code design when building a complex program where, rather than extensive configuration, the code makes reasonable assumptions and allows overrding these assumptions for minimal configuration. |
| ACID | |
| Consistency,Availability, Partitioning (CAP) Theorem | |
| Composition Over Inheritance | |
| Monad | |
| Extreme Programming | |
| Pure function (coding) | |
| Side-effects (coding) | |
| Embedded System | |
| Ecmascript | |
| Progressive Web Application (PWA) | |
| Single Page App (SPA) | |
| Ajax | |
| ACID | Acidity, Consistency, Isolation, Durability. Many databases ensure operations will always leave the database in a valid state; even when they fail. Some trade off aspects for other benefits, while suome supot all four. |
| CAP Theorem | Consistency, Availability, Partition Tolerance. The mathematical truth that a distributed system can never be all three: all queries return consistent data, be always online, and support distribution among many nodes. |
| Composition Over Inheritance | Code design guideline to whenever possible refactor common code to its own component referenced by simple variables or properties rather than using inheritance. |
| Monad | An academic term for a code structure that isolates side effects in a functional paradigm language. |
| Extreme Programming (XP) | A formulation of the agile software development process created by Kent Beck. In XP, beneficial practices like test driven development and pair programming are taken to the "extreme" and done 100% of the time. |
| Side-effects (coding) | A bit of code that when run, creates an effect other than just the function return. Can be output to a screen, write to a file, a network request, or just modifying a global variable. |
| Pure function / Side effects-free coding | A function that when run will return a value with no side effects. This is often encouraged to do as much as possible as pure functions are much easier to reason about and to optmize. |
| Embedded System | A system where the software is deployed along with the hardware and not intended for users to attempt to modify, or even install extensions or applications on. |
| Ecmascript | Official name of the Javascript language. "Javascript" is a trademark of the Oracle Corporation whereas the actual syntax is defined by the ECMA standards body. |
| Progressive Web Application (PWA) | Term for an application using a broad set of newer web browser features that aim to enable a website to behave more like an installed application, especially on mobile. |
| Ajax | Term for using javascript in a web browser to fetch data from a webserver using the XmlHttpRequest or fetch functions. |
| Single Page App (SPA) | Web application that - rather than the full page request and redraw lifecycle - heavily relies on the technnique of loading new data via Ajax and redrawing the page with javascript. |
| Javascript Object Notation (JSON) | |
| JSON Web Tokens (JWT) | |
| Server-Client | |
Expand Down

0 comments on commit 03c9920

Please sign in to comment.