CodeIsGo.com

State transfer is fundamental to online applications. Web apps are architected around the network, with the separation of front-end from back-end and protocols like AJAX and REST. However, newer protocols like GraphQL and frameworks like Remix are increasingly abstracting state transfer away from application code. By James Arthur.

Local-first software is a new paradigm that fully abstracts state transfer out of the application domain. It’s the endgame for the evolution of state transfer and the vision we’re building towards with ElectricSQL.

Source: https://electric-sql.com/blog/2022/12/16/evolution-state-transfer

Further explained are:

• Forms to GraphQL
• Invention of AJAX
• Standardising on REST
• Enter GraphQL
• Local-first
• Optimal placement and movement of data

With local-first, developers code directly against a local, embedded database. Reads and writes are instant. Users can still share data and collaborate but the state transfer happens in the background, with reads and writes made against the local database and then synced in the background to the server. Web development has been progressing through an evolution of state transfer from manual, imperative data transfer towards automated, declarative systems. Hybrid local-first architecture is the natural endgame for this progression. Nice read!

DTO is probably the most straightforward pattern in object-oriented programming. What could be the motives for using DTOs in our applications? By Andrey Belyaev.

In this guide you will find information about:

• Introduction: what is DTO?
• Where do we need DTOs?
• DTOs for API layer
• Entities vs. DTOs on the business layer
• No-DTO approach
• How to map an entity to DTO?
• POJOs and Hibernate
• POJOs and mappers
• Spring Data JPA Projections

It is hard to avoid DTOs in modern business applications. The most common reason to use them – stabilize the application’s external API and hide some information from the data transferred via this API. Nice one!

At its core, the JAMstack is a web development approach that focuses on using client-side JavaScript, reusable APIs, and prebuilt Markup to create web applications. This architecture allows for faster and more secure web development by using prebuilt and pre-rendered pages, which are then delivered to the user via a content delivery network (CDN). By Martin.

The article deals with:

• What is JAMstack?
• What does JAMstack mean?
• Why should you start using JAMstack?
• SEO - Google favors JAM
• Popular frameworks

In short, the JAMstack is a powerful and efficient web development architecture that is ideal for frontend developers looking to build modern, fast, and secure web applications. With its focus on client-side JavaScript, reusable APIs, and prebuilt Markup, the JAMstack offers a range of benefits that make it an attractive option for frontend developers looking to create engaging and dynamic user experiences. Good read!

When evaluating a Kotlin Multiplatform solution, it was very important to our team that we understand how we could build a CI/CD pipeline for the project. It needed to be easy for our team to push changes and build a new version of the project. By Nate Ebel, Android Engineer.

Both our iOS and Android applications use GitHub Actions for our CI needs. So, in this post, we’ll walkthrough how to setup a GitHub Actions workflow for building a Kotlin Multiplatform Mobile project.

The article covers:

• Creating a GitHub actions workflow for Kotlin Multiplatform Mobile
• Setting up our workflow environment
• Configuring a job to build a Kotlin Multiplatform Mobile Project
• Checking out Kotlin Multiplatform and Swift package repos
• Setting up Java and Xcode tooling
• Extracting project version for Git tagging
• Building the artifacts
• Publishing the JVM artifacts
• Reviewing a PR workflow solution

… and more.

These workflows have worked well for us in the past 1.5 years. Authors publishing model for their Swift Package is evolving, but the workflow itself has worked great. Nice one!

The current influx of data — structured, semi-structured, and unstructured — being driven by an array of data sources is fueling opportunities to leverage machine learning to extract insights and accelerate innovations that can transform businesses and industries. As these data volumes continue to rise, companies are struggling with the complicated task of managing this data and figuring out how to harness it for analytics and AI. By Vedant Jain, Denny Lee.

The article explains:

• What is Delta Lake?
• What is Amazon SageMaker Studio?
• Integrate SageMaker Studio with Delta Lake
• The benefits of connecting SageMaker Studio and Delta Lake

Delta Lake is an open-source storage framework that enables building a Lakehouse architecture with compute engines, including Spark, PrestoDB, Flink, Trino, and Hive, and APIs for Scala, Java, Rust, Ruby, and Python. Delta Lake is a great option for storing data in the AWS Cloud because it reads and writes in open-source Apache Parquet file format. This format makes it easy to write connectors from engines that can process Parquet. Nice one!

The way we measure and optimize website speed is always changing. New web standards are introduced (and eventually widely supported), new tools are developed, and new metrics suggested. By Matt Zeunert.

This article takes a look at some of the ways that the web performance landscape changed in 2022:

• Priority hints
• No more OSCP requests in Chrome
• Interaction to Next Paint Metric
• Desktop core web vitals as a ranking factor
• Back/forward cache in Chrome
• View observed metrics in PageSpeed Insights
• HTTP/3 standardized
• Better data on what requests are render-blocking
• Chrome DevTools performance insights panel
• 103 early hints
• Full page prerendering in Chrome

… and more. A lot of new browser features have become available to improve website performance in the last year. We also have new tools to measure and improve site speed. Good read!

It’s not a secret that the Angular community has needed better tools to inspect the structure of Angular applications and profile their performance. Angular DevTools has been introduced for just that! By Nethmi Wijesinghe.

Source: https://www.syncfusion.com/blogs/post/debug-angular-apps-easily-using-angular-devtools.aspx

This article will go through Angular DevTools in detail and provide step-by-step guidance on making the best of it:

• Angular DevTools
• Getting started with Angular DevTools
• Debugging the application
• Look up a component or directive
• Profiling the application
• Understand the application’s execution

In this article, author discussed the features of Angular DevTools and how to use them. Even though it’s relatively new to the Angular community, DevTools eases your development process and brings transparency. Author encourages you to try it out. Nice one!

Older article about building neural networks from scratch. From the math behind them to step-by-step implementation coding samples in Python with Google Colab. By Pratik Shukla, Roberto Iriondo.

Source: https://pub.towardsai.net/building-neural-networks-from-scratch-with-python-code-and-math-in-detail-i-536fae5d7bbf

This tutorial explains (amongst others):

• What is a neural network?
• Applications of Artificial Neural Networks
• General structure of an Artificial Neural Network (ANN)
• What is a Perceptron?
• Where we can use Perceptrons?
• Neural Network implementation from scratch

… and more. Comprehensive list of resources for further reading is also including. Fabulous!

Digital services made for consumers are opening up new opportunities and vulnerabilities. With more employees bringing unmanaged devices to the office, business networks can be accessed by many more people. Plus, remote work means that an organization’s IT perimeter is no longer restricted within its walls. By Mihaela Marian.

In the article you will find information on:

• What is Continuous Adaptive Risk and Trust Assessment (CARTA)?
• Why is Role-Based Access Control (RBAC) inadequate?
• How CARTA works
• How CARTA relates to other risk assessments
• How to implement Continuous Adaptive Risk and Trust Assessment
• CARTA vs. Zero-Trust

CARTA continuously evaluates all users and devices and makes contextual access decisions. It has its roots in the Zero-Trust framework, which advocates the idea that no user or device can be trusted, even if they’re already on your network. Companies with zero trust security go to great lengths to ensure that only appropriate access is granted to critical assets. Good read!

The growing popularity of serverless architectures has led to an increased need for solutions to the modern challenges of microservice observability—one of the most critical components for running high-performing, secure, and resilient serverless applications By @DeveloperSteve.

In this article, we will:

• Explore the challenges that serverless architectures present to observability
• Suggest possible solutions
• Identify the hidden costs of these solutions
• Discuss ways to mitigate such expenses

In serverless environments, not only are you abstracted from the underlying infrastructure that runs your code, but the distributed, event-driven nature of serverless applications makes traditional approaches to monitoring and debugging ineffective. Serverless functions are often chained through asynchronous event sources such as AWS SNS, SQS, Kinesis, or DynamoDB, making tracing extremely difficult. Interesting read!