Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
There is a conventional approach to learning a framework such as Flask: learn with a tutorial, then build something small, and gradually increase functionality. There are dozens to hundreds of such tutorials, and they are very helpful.
Here we offer a complementary approach, one that entirely reverses the script. Build a complete running project you can explore within a minute, then learn how to alter it, debug it - and then how to create it, literally in seconds.
It's not so hard to create a single endpoint API or a "Hello, World!" page. But what about creating a complete microservice: multiple endpoints with CRUD services, business logic enforcement, and a multi-page application? Well, that's a horse of an entirely different feather.
In this article, we'll show how to use open source technologies to:
Harsh, yes... but too often true. Certainly, Agile is a great start for business user collaboration to ensure requirements fit, but it depends on Working Software. This is exactly what automation provides: Working Software, Now. Here's how.
This article illustrates how Automation, coupled with an Agile Process, can dramatically improve time to market, and reduce requirements risk:
In this tutorial, we’ll show how to use ApiLogicServer to create, customize and run a Database based API. API Logic Server is an open-source Docker container. With the commands shown below, you get:
Create the sample project in a minute or two, as follows. With Docker started, enter these Terminal commands (Windows, use Powershell):
Is backend creation blocking your Mobile App Dev? Or strategic B2B/internal integration?
Imagine that you could...
Create a database API, instantly?
And declare logic, with spreadsheet-like rules?
Plus an instant Web App, to engage Business Users?
A very reasonable question asked in this article is:
How are rules different from SQL?
As engineers, we are always mindful of the need to minimize cost and time. Experience has taught us that while automation is valuable in reducing code, we must also preserve design flexibility and enable agile iterations. Let's break that down a bit, and then illustrate with an example.
Automation (Reduce Routine Code — Executable Specifications)To warrant the learning curve, automation must significantly reduce routine coding. 25% reduction in code is not compelling enough.
Here's how to create a basic web app for your database in 10 minutes. Let's explore the created app, and then the creation process.
As shown below, the apps are
RESTful APIs are at the heart of Digital Transformation and are required for mobile apps and integration. They are core to Business Agility. That's strategic.
But the conventional development process — create an ORM and design and code your APIs — is remarkably code-intensive and complex. And then there's the Business Logic — a substantial portion of any system — more code. Not agile.