Ihor Plintuq’s Post

Simple and powerful. Check out S3’s new conditional write feature & how to use it. — 1. Naming Strategy Use a structured naming convention for objects, including the version number as part of the object key. For example, an order might be stored as ecommerce/tenantA/orders/12345/001.json. The `001` in the key represents the order's version. Every time the order is updated, a new object with an incremented version number (e.g., 12345:002.json) is created. 2. Using `If-None-Match` for Conditional Writes: Use the If-None-Match=”*” header when updating an order. This tells S3 to only proceed with the write operation if an object with the specified key (e.g. order123:002.json) does not exist. This prevents two processes from creating the same version number, ensuring each update creates a new, unique version. 3. Handling Conflicts: If the If-None-Match=”*” condition fails (resulting in a `412 Precondition Failed` response), it means another process has already created that version. The process can then reread the latest version, resolve the conflict, and retry the operation with the next version number.

What are logs? What are traces? Our latest blog post shares the key differences between logs and traces, helping you to optimize your software and implement system observability. Learn more— https://lnkd.in/gzK8cgGW

I was chatting with a customer recently about adding tenant screening services, and they asked how to make the API integration easier. Here's what I suggested: 1. Keep it simple to start: Focus on the most important info like credit score and where it comes from. You can always add more later. 2. Look for flexibility: Find providers that offer different levels of integration, from just getting basic scores to pulling in lots of detailed data. 3. Multiple formats: Make sure the API can give you data in different ways (like JSON or PDF) depending on what works best for you. 4. Easy-to-understand instructions: Good providers should give you example reports and clear API guides to help you along. 5. Help when you need it: Pick a company that offers support from their team and can walk you through the process. 6. Try before you buy: Ask for a test environment where you can play around with the API before fully committing. Remember, a good API provider should make it as easy as possible for you to get started, letting you begin with the basics and grow from there. This way, you're not overwhelmed at first, but you still have room to expand later on.CRS‎

Are prompts configuration or code? I would say code if the model output were deterministic, but it isn't. The creators of prompt management software seem to agree with the idea of prompts as configuration. On the other hand, we put SQL in the code, and the names of the fields we extract from third-party REST APIs are in the code, too. What about prompts? Where is the line between code and configuration in the case of things that are somewhat like code but not really code?

Struggling to see what is happening when your automated check suite is having a lot of failures? Here is an idea: Blast Zones. Run the checks in ever expanding coverage. This is also a good help if you have a gigantic E2E suite with lots of long scripts. If you have identified and labeled your scripts correctly, it would be easy to switch to a more focused checking based on changes made in the codebase. That way, if something blows up, the entire suite is not affected but you limit the area of the blast. If you have 20 checks telling about the same thing, its not very useful to run the 20 checks if one of them already told you the information you need. In the E2E world at the UI level, if you are suffering of a more upside down test pyramid, introduce business logic checks (API/Contract) below the UI and label those. That way you don't have mountains of debugging if the focused business logic checks are failing as you can stop checking the changes any further. Change based, focused, gradual conditional increase in exposure. Faster feedback, less resources used (machine power, time). In order to achieve this, you need to know what your tests are doing, don't let that slip or else you will own a boogeyman which no-one wants to touch. PS. If you don't trust your checks enough for them to be conditional, you have some work to do.

Simple software is fast. Simple software is beautiful. Simple software is powerful. Simple software is (almost) bug-free. With this tiny call stack OneM chain's execution engine processes 1.4 mln transactions per second.

Good notes on Api Gateway

Divide your business logic into two parts: - Business rules which are attribute-bounded and do not depend on other external software artifacts.. - Business rules that depend on other external software artifacts.. Then, - Put the first logic inside Entities and write Unit Tests for them, and - Put the second type of logic in Use Cases and write Integration Tests for them.. *Second type of logic can call first type of logic inside.. *External software artifact can be other Entity, Repository, other Use Case or external third party service..

Today's random thought: What is enterprise grade quality for a digital solution, compared to other type of software? 1. Can grow from a simple solution to a super complex solution fast without major refactoring 2. Can use consistent methlogy to realize variety of business requirements 3. Provide method to resolve common problems without go deep into source code, allow non-developer resources to scale the support capabilities 4. Can adapt to new tech standards without refactoring the business logic 5. Out of box suppot of security and compliance and can adopt to new compliance requirements without refactoring business logic 6. Allowing customize the solution in a upgrade-safe approach Do you agree?

Dive into the world of Infrastructure from Code (IfC)! Say goodbye to manual configuration and hello to a seamless integration between your application code and infrastructure. Learn about the different implementation methods and choose what works best for you. #TechTrends https://hubs.li/Q02w8dYr0