Asynchronous Server App Boilerplate Video Tutorial
If you ever wondered about how to enter the fast asynchronous world, where web servers and other responsive applications utilize hardware components to their maximum and sleep when no work is necessary, you are in the right place.
Asynchronous Server App Boilerplate (ASAB) was built exactly for the purpose of letting newcomers quickly enter the asynchronous programming with just a few lines of code. ASAB can then be used for building complex applications or foundations for other frameworks and base components.
Introduction
Presentation of the ASAB architecture together with basics of asynchronous programming in Python with asyncio library.
Hello world
How to build a few line long "Hello world" application.
Web server example
Web server application made easy with ASAB using aiohttp.
Publish-subscribe (PubSub) example
Publish-subscribe mechanism of events in the ASAB application.
Logging & Configuration
How to use hierarchy configuration and simple logging.
Modules & Services
ASAB is based on modules, services and their handlers to ensure loose coupling and independent microservices.
Other examples
ASAB provides many examples, which are part of the source code on GitHub: https://github.com/TeskaLabs/asab/
Most Recent Articles
You Might Be Interested in Reading These Articles
Software architect's point of view: Why use SeaCat
I've recently received an interesting question from one software architect: Why should he consider embedding SeaCat in his intended mobile application? This turned into a detailed discussion and I realised that not every benefit of SeaCat technology is apparent at first glance. Let me discuss the most common challenges of a software developer in the area of secure mobile communication and the way SeaCat helps to resolve them. The initial impulse for building SeaCat was actually out of frustration of repeating development challenges linked with implementation of secure mobile application communication. So let's talk about the most common challenges and how SeaCat address them.
Published on April 16, 2014
Building the Correlator #2: Window architecture
In the previous article, I described what the window correlator is good for, analyzing long series of data to gather security incidents and produce alerts. I also discussed the memory issue that comes with storing long series of data composed of events, which come to the application at a frequency of tens of thousands of events per second. The proposed solution is to store only relevant parts of the series, here called segments, in memory. Now, we'll take a look at the segments in more detail, so we know exactly what structures they are composed of.
Published on June 15, 2024
From State Machine to Stateless Microservice
In my last blog post, I wrote about implementing a state machine inside a microservice I call Remote Control that will automate deployments of our products and monitor the cluster. Here I would like to describe how all this was wrong and why I had to rewrite the code completely.
Published on February 15, 2023