AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix typos

Browse Source
This commit is contained in:
daniel.motzko
2021-06-30 13:54:36 +02:00
parent 0b81d0318c
commit 86e42178df
16 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
radar/2019-11-01/flamingo.md
View File

@@ -18,22 +18,22 @@ Flamingo is:
Go as simple, powerful and typesafe language is great to implement and scale serverside logic.
Flamingo has a clean architecture with clear dependencies in mind and offers a typical features and support for nowadays web applications:
* Powerful Templating Engines. E.g. support for Pug templates with reusable mixins and lightweight scripting.
* Powerful Templating Engines, e.g. support for Pug templates with reusable mixins and lightweight scripting.
* Configuration concepts using yml and support for multiple areas and contexts
* Powerful Dependency Injection
* A Module concept for building modular and pluggable applications
* Authentication concepts and security middleware
* Flexible routing with support for prefix routes and reverse routing
* Web Controller Support with: Request / Response / Form Handling etc
* Operational Readyness: Logging, (distributed) Tracing, Metrics and Healthchecks with seperate endpoint
* Operational Readyness: Logging, (distributed) Tracing, Metrics and Healthchecks with separate endpoint
* Localisation
* Commands
* Sessionhandling and Management
* Session Handling and Management
* GraphQL support and therefore support to build nice SPA and PWAs on top of it
* Resilience and Caching for external APIs calls.
Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes ["ports and adapters"](/methods-and-patterns/ports-and-adapters.html) architecture - so that you have a technology free (domain) model and any possible (and replaceable) persitence behind it.
Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes ["ports and adapters"](/methods-and-patterns/ports-and-adapters.html) architecture - so that you have a technology free (domain) model and any possible (and replaceable) persistence behind it.
That makes Flamingo useful to build microservices and applications - especially to build "frontends" or portals that require interaction with other (micro) services in a distributed architecture.
When sticking to the architectural recommendation you can build modular applications with replaceable adapters that gives you independed testability.
When sticking to the architectural recommendation you can build modular applications with replaceable adapters that gives you independent testability.
With **"Flamingo Commerce"** there is an additional active projects that offer rich and flexible features to build modern e-commerce applications.