|
You are here |
glama.ai | ||
| | | | |
www.perrotta.dev
|
|
| | | | | JSON Schema is a powerful validation tool to enforce a given structure and/or data type in JSON and YAML files. Problem statement: Disallow aws.iam_role1, with the implicit goal of allowing aws.iamRole. Because naming and sticking to conventions is hard. Illustration: aws: iamRole: fooArn iam_role: barArn # <-- disallow | |
| | | | |
www.marcogomiero.com
|
|
| | | | | SERIES: Building a backend with Ktor Part 1: Structuring a Ktor project Part 2: How to persist Ktor logs Part 3: How to use an in-memory database for testing on Ktor Part 4: How to handle database migrations with Liquibase on Ktor Part 5: Generate API documentation from Swagger on Ktor Part 6: How to schedule jobs with Quartz on Ktor Part 7: Moving from mobile to backend development with Ktor When a backend project exposes some APIs, there should also be a place where the clients of those APIs can see an... | |
| | | | |
everttimberg.io
|
|
| | | | | Flask is a simple Python framework for creating web applications. It can be used to create API servers in a microservices architecture. When doing so, it is helpful to provide API documentation that ships with your service. This post outlines a technique for shipping OpenAPI v3 documentation from your service while co-locating the documentation with the API implementation. Keeping the documentation with the route definition ensures that it is easy to update, updates can be clearly identified during code ... | |
| | | | |
blog.scottlogic.com
|
|
| | | In most microservice architectures, there are many opportunities and temptations for sharing code. In this post I will give advice based on my experience on when it should be avoided and when code reuse is acceptable. The points will be illustrated with the help of an example Spring Boot project. | ||