-
Data contracts. Building universal data access proxy api
Data contracts usually requires us to build around them a universal data access proxy API for users to consume. API utilizing proper data contracts, negotiated with different teams, acts as a unified gateway providing the necesities. Allows access to data sources like databases, REST APIs, GraphQL endpoints or other file systems. One api to rule them all Steps to build data contracts for proxy api You could try and adopt a similar flow for creating such access points, even make a template in JIRa so You will know where to get proper data and how to acquire it… or maybe expose the library and just aprove properly looking merge requests……
-
Adr vs readme vs changelog
Adr, readme and changelog are the most valueable pieces of documentation that a project could? / should? maintain. They provide us with crucial, core informations we need to star and continue effective development. Let us look at them closely. Usually we can keep everything in plain text or better yet use a Markdown format. You can even try and use some linter, highlgihts for easier writing. ADR (Architectural Decision Record) ADR (Architectural Decision Record): Document that holds a single, significant architectural decision. Includes the context, options that were considered, chosen solution with consequences. Serves as a traceable rationale for future reference as well as new team members. Readme txt or…
-
The Golden Byte. Most valuable data
The Golden Byte. Most valuable data In data engineering, every byte has a cost but not all bytes are made to be equal ( read Animal Farm by George Orwell). We collect terabytes of data in the form of logs, metrics, cookies, text, pictorues and transactions. Yet only a small portion of this information is truly crucial and drives business outcomes. That fraction is what can call the Golden Byte, single most valuable unit of data that fuels strategic insight and decision-making. Data tiers architecture The Golden Byte embodies the essence of a gold layer in modern data architecture: raw ,curated , aggregated, and business-ready information. It is the outcome…
-
Know Your data. Cost per byte vs value per byte
Cost per byte vs. Value per byte: Rethinking Data Efficiency We are living in an era where nothing gets erased (just archived). Let us dwell on cost per byte vs value per byte of such data. Every byte you store, move, or process has a cost. We focus on cost saving. Data engineering isn’t just about hoarding everything, it’s a calculated risk about understanding whether those bytes are worth to store them. Pro hint – do not fall into the trap of ‘let us grab everything and think about it later’. It does make sense until you figure out what is what but then remember to delete it ? Oh…
-
Universal Principles of Design: Third Edition
Universal Principles of Design: Third Edition OverviewThe Universal Principles of Design, Updated and Expanded Third Edition is a comprehensive design reference book authored by William Lidwell, Kritina Holden, and Jill Butler.Original was released on February 7, 2023, the third edition expands its predecessors by 75 new entries, bringing the total to 200 principles, laws, and guidelines essential for effective design across various disciplines. It serves as a guide for anyone looking to enhance their understanding of design principles that can be applied universally in professional and private life. If You want to learn more for free go HERE !! https://principles.design/ Why should care ? Overall the book Universal Principles of Design: Third…
-
GraphQL approach to APIs
GraphQL is a query language and runtime for APIs that has transformed the way developers approach data retrieval and manipulation. Developed by Facebook in 2012 and open-sourced in 2015, GraphQL offers a more efficient and flexible alternative to traditional REST APIs. Its core principle is to allow clients to request precisely the data they need, no more and no less, which significantly reduces over-fetching and under-fetching of information. GraphQL provides a single endpoint where clients can send complex queries to fetch data from multiple sources in a single API call. One of its key strengths lies in its use of a strongly-typed schema that defines the structure of available data,…
-
AppSync in AWS cloud. Pros, cons and key considerations
AppSync in AWS cloud is a managed service that simplifies application development by providing a flexible API to securely access and combine data from various AWS (not only) sources. As businesses increasingly adopt cloud-based solutions, understanding the advantages and drawbacks of using AppSync in the AWS ecosystem can be helpfull. Follow up at GraphQL post. Pros and Cons of Using AppSync in AWS Cloud Pros Cons Realtime updates and synchronization Steep learning curve for developers new to AWS Built-in security features Potentially higher costs compared to alternatives Automatic scalability Limited plugins and ready-made solutions Integration with other AWS services Single-region solution (requires additional components for multi-region) Offline support Less control…
-
Locality of Behaviour
Locality of Behaviour is a great principle that should help with maintaining the code. This is the characteristic of the code that enables a developer to only read a small portion of code to understand its function. Without the need to skip, skim, read, jump all over multiple files. I love that rule cause it DOES MAKE SENSE. I can see many places where we would benefit from it but not always do it that way because of the ‘standard’. Which, in the end, nobody knows what it is anymore cause everyone is mixing patterns, antipatterns and the number one performance metric is how fast you can deliver… maybe i…
