Articles about SaaS from iwebforyou: practical, plain-language guidance on websites, SaaS platforms and cloud for you.
This category brings together our articles on building SaaS platforms, written for people who commission or manage such a product. They cover three things we consider basic. First, development test first: write a failing test, then the code that passes it, then improve the code, so every feature has its check from the start, and every confirmed bug becomes a permanent test. Second, roles and permissions: they are written as a table before any code, based on three OWASP rules, least privilege, deny by default and a check on every request on the server. Third, the separation of customer data, where AWS describes three models: silo, pool and bridge. The model is chosen in the system design, before code is written. These articles are currently available in Greek.
3 articles
A SaaS platform keeps customer data separate with one of three AWS models. In silo, each customer has their own resources. In pool, customers share resources. In bridge, the two are combined. The model is chosen in the system design, before any code is written.
Read the articleThe roles and permissions of a SaaS are written before the code, as a table showing which role does what. The base is three OWASP rules: least privilege, deny by default and a check on every request at the server. The result is verified with tests.
Read the articleIn test-driven development (TDD), you first write a test that fails, then the code that passes it, and finally you improve the code. This way every feature of a SaaS platform has its check from the start. Most tests are small and fast, while a few check the whole in the browser.
Read the articleSend a project request, or check your current website for free. We read every message ourselves.