The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,860 other subscribers

Archive for the ‘Developing scalable systems’ Category

The Twelve-Factor App

Posted by jpluimers on 2024/11/21

Still relevant: [Wayback/Archive] The Twelve-Factor App and [Wayback/Archive] 12 Fractured Apps — Medium

Once Docker hit the scene the benefits of the 12 Factor App (12FA) really started to shine. For example, 12FA recommends that logging should be done to stdout and be treated as an event stream. Ever run the docker logs command? That’s 12FA in action!

Via

–jeroen

Posted in Back-End Development, Cloud Development, Communications Development, Conference Topics, Conferences, Deployment, Developing scalable systems, Development, DevOps, Distributed Computing, Event, Software Development | Leave a Comment »

Scaling, automatically and manually – The Isoblog.

Posted by jpluimers on 2019/01/31

You don’t want to reach the saturation line (Sättigung) on the right: if you do, things go down very fast.

TL;DR of TL;DR:

Reactive autoscaling sucks. Get out of it. Model your shit.

TL;DR:

A reactive scheme where you try automatically detect where the hockey sticks curve mens you are always too late as user experience is already down the drain: no matter the environment, the curve is always too steep to go unnoticed.

If you use loadav in your reactive scheme, you’re lost even more.

So you need a proactive scheme with models. Those models of course are based on prior monitoring of situations where things went bad combined with knowledge on how the system is likely to scale. Each time the system goes bad, refine your models.

Monitoring

I was really glad that Kristian followed up with [WayBack] Monitoring – the data you have and the data you want – The Isoblog.

According to Kristian, the first monitoring tier should be something like [WayBack] Prometheus – Monitoring system & time series database: An open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach.

I’m glad he mentioned that, as I’m a bit fed up with sites having Nagios and Zabbix. Way too cumbersome to setup, and either not far enough features, or the dashboards aren’t insightful enough.

–jeroen

Sources:

Percentile video:

Read the rest of this entry »

Posted in Developing scalable systems, Development, Software Development | Leave a Comment »