Cards for Analyzing and Reflecting on Doomed Software

Infos about the logging and metrics process in cloud foundry deployments; covers exposition of prometheus style metrics endpoints.

Check your application architecture and keep it consistent

Document, constraint and verify application architecture

toolchain for generate software architecture documentation based on arc42 und asciidoc

Format for ADRs

A model (developed by Leonard Richardson) that breaks down the principal elements of a REST approach into three steps. These introduce resources, http verbs, and hypermedia controls.

It's clear that microservices are the current hot architectural pattern, covered extensively on blogs, in the tech news at software conferences. Several times a week, InfoQ has a news item, podcast or presentation mentioning microservices.

But is it all just hype and a pattern useful at startups working on greenfield applications? And is the dreaded monolith, the antithesis of a microservices architecture, really dying a slow death, barely limping along until a complete replacement is built?

The reality looks closer to the compromises that any software architect will recognize. Both architectures come with pros and cons, and it is important to understand all the trade-offs before deciding that the monolith has to go, and microservices are the answer. A common theme is managing complexity, and successful solutions (with either architecture) strongly embrace concepts of Domain-Driven Design.

This eMag includes articles written by experts who have implemented successful, maintainable systems across the spectrum of microservices to monoliths.

Cover
Download now Email it to me

Code is easy, State is hard. Learning how to deal with your monolithic relational databases in a microservices structure is key to keeping pace in a quickly changing workplace. There are many approaches and in this book, author Edson Yanaga, takes you through nine different strategies for integrating data from your monolithic application to a microservice architecture.

In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps.

SSE Servlet example

HATEOAS (Hypermedia as the Engine of Application State) is a constraint of the REST application achitecture. A hypermedia-driven site provides information to navigate the site's REST interfaces dynamically by including hypermedia links with the responses. This capability differs from that of SOA-based systems and WSDL-driven interfaces. With SOA, servers and clients usually must access a fixed specification that might be staged somewhere else on the website, on another website, or perhaps distributed by email.

Explains and gives some references to the thread model of the OSB

Welcome to SOAPatterns.org, a site dedicated to the on-going development and expansion of the SOA design pattern catalog.

Fast jedes IT-Projekt überlegt aufs Neue, was bezüglich der Software- Architektur bedacht, entschieden und dokumentiert werden muss. Sparen Sie diesen Aufwand.

Dieses Template (bzw. das daraus erzeugte Dokument) gibt Ihnen eine standardisierte Gliederung für Software-Architekturbeschreibungen vor. Das aus diesem Template entstehende Dokument stellt die umfassende und vollständige Beschreibung der Architektur eines IT- Systems dar.
Umfassend und praxisnah

ARC42 bietet Ihnen ein praxisnahes Template, das Sie sofort einsetzen können. Sie finden darin eine vollständige, strukturierte und vernetzte Sammlung architekturrelevanter Themen, jeweils mit

* Inhalt (Was soll bedacht, entschieden und dokumentiert werden?)
* Motivation (Warum und für wen?)
* Form (Wie?)
* Beispielen (So kann es aussehen)
* Hintergründen

Zu diesen Themen zählen Architekturziele, Randbedingungen, verschiedene Sichten auf Ihr System, querschnittliche Aspekte und vieles mehr.