Apache Kafka offers the operational simplicity of data engineers' dreams. A message broker that allows clients to publish and read streams of data — Kafka has an ecosystem of open-source components that, when combined together, help store, process, and integrate data streams with other parts of your system in a secure, reliable, and scalable manner.
This Refcard dives into select patterns and anti-patterns spanning across Kafka Client APIs, Kafka Connect, and Kafka Streams, covering topics such as reliable messaging, scalability, error handling, and more.
If you've worked with Backendless API for a while, you may occasionally run into a situation where the functionality you'd like to have isn't readily available. One such function is the programmatic management of your application's data tables. For instance, you may need to clear up all the data and recreate the table structure with specific columns on demand while developing your app. This article will show you how to do that and more.
The Backendless Console API
Backendless essentially has two APIs: the Client API and the Console API. The former is the one used by Backendless' Client SDKs and which is in effect in our REST SDK. The latter is the API that the Developers' Console is using, hence the name. Different providers may have different names for that one, such as Admin API or Management API, so be aware that the terms may sometimes be used interchangeably.
