CodeIsGo.com

Imagine you are building an inventory or an ecommerce website or a social media of your own, what are the two major things you will have to deal with? A. Database B. Search engine. By Haimantika Mitra.

This article deals with building a simple app where we search for movies, to achieve this we use:

• Meilisearch- for building the search and
• Appwrite - for the backend to store data and run functions to automate the search
• Prerequisites
• Creating an Appwrite function
• Configuring the Appwrite function
• Building the search app
• Fetching data from Appwrite to MeiliSearch

Appwrite is a self-hosted backend-as-a-service platform that provides developers with all the core APIs required to build any application. Appwrite provides you with a set of APIs, tools, and a management console UI to help you build your apps a lot faster and in a much more secure way. Meilisearch is a powerful, fast, open-source, easy to use and deploy search engine. Both searching and indexing are highly customizable. Features such as typo-tolerance, filters, and synonyms are provided out-of-the-box. Good read!

But it is somewhat agreed understanding that Architects in a technical team are very senior people who should know everything. This is not a complete truth and nor a lie. What architects are supposed to do (I believe) still varies from organisation to organisation. By Husyn for AWS Community Builders.

The core skill for this role I believe is critical thinking and decision making. For any problem statement different roles in software engineering domain will have different solutions based on their perspectives. An Architect is the one which should understand all such perspectives and take decision based on first principles.

The article walks you over:

• Types and kinds of architects
• First principles & decision making
• Soft skills
• Business vs tech
• Biases & preferences
• Writing
• Defining & naming
• Architects to follow
• Cloud architect

… and more. Any “good” cloud architect can’t be good in one area and be ignorant in other. They have to be a full package for the organisation. In terms of real-life example, AWS architects have a proper T shaped skillset. Yes there are specialised SAs, but even they understand basics of other domain. Interesting!

Working on a large-scale project and managing its codebase can be a big challenge for teams. Though micro-frontends have been in the picture for a while now, they are getting increasingly popular because of their unique features and usability. By Harsh Pate.

Micro-frontends are particularly helpful because multiple teams can work on individual modules of the same project without worrying about other modules. With micro-frontends, it doesn’t matter how many modules will be added to a current system.

In this article, we’ll cover the basics of what a micro-frontend is and how to implement it using Next.js. We’ll also discuss the advantages of using micro-frontends in your applications.

• Introduction to micro-frontends
• Implementing a micro-frontend with Next.js
  • Prerequisites
  • Setting up the micro-frontends
  • Execution and results
• Advantages of micro-frontends
  • Deployment and security
  • Scalability
  • Faster development
  • Easy testing

So how small is a micro-frontend? This is still unanswered. The bottom line is that you should split your project up so that the user experience won’t be disturbed. This process may be painful because it’ll likely include multiple whiteboard revisions. Godo read!

Our current centralized logging solution is Logz.io: Cloud Observability for Engineers and most of our application logs are sent there from the k8s cluster. In addition, we use the logging system’s alert mechanism to trigger and send alerts to various sources, including email, Slack channels, etc. By Uriah Ahrak.

When we have several dozens of Lambda functions, we need to solve the problem in a generic way to reduce the amount of work and migration required by the developers who work with FaaS technology on a daily basis.

The article has these main parts:

• Possible solutions
• How do we plug in the currently deployed Lambda functions?
• Deployment of logs consumer
• Deployment of logs extension
• Logging code-based Lambdas
• Logging via CloudWatch log streams

For the final solution, we chose to have a segregation between our code and the logging system specifics. We initiated a Kinesis Stream, which is a generic process that anyone with AWS SDK and appropriate AuthZ can access and send logs in a specific format. If you have Lambda functions/applications that don’t support Lambda extensions, and you don’t want to change the code of the application in order to send logs towards the Kinesis Stream, you can use the CloudWatch Logger Lambda, which is listening to CloudWatch logs streams and pushing these logs automatically to the Kinesis Stream. Good read!

In this blog, author wants to underscore the urgency around cybersecurity, how it’s evolving, and how companies can use technology to manage risk. By Darryl Willis.

A Microsoft sponsored Poneman Insitute study shows that 68 percent of senior management believe that IT and operational technology (OT) are critical to supporting strategic goals.¹ Business leaders realize that connecting everything from vehicles to power plants can offer unprecedented gains in scale and efficiency. However, digital transformation can be a balancing act of risk and reward. These expanding digital platforms can become targets for increasingly sophisticated attacks—with potentially disastrous impacts. Imagine what could happen if a cybercriminal gains access to an oil field or power grid?

The blog post also covers:

• Getting fearless with cybersecurity
• Fortune 500 American utility secures OT network
• Leading global oilfield services firm protects critical processes

Microsoft Defender for IoT is now a critical component of the company’s security architecture. The solution brings operations and IT teams closer together and protects the interests of the organization and key stakeholders. Good read!

Red Hat Ansible Automation Platform 2 features an awesome new way to scale out your automation workloads: automation mesh. In this blog post, I want to focus on the technical implementation of automation mesh, what network ports it is using and how you can secure it. By Sean Cavanaugh.

We separated the control plane (which includes the webUI and API) from the execution plane (where an Ansible Playbook is executed) in Ansible Automation Platform 2. This allows you to choose where jobs run across execution nodes, so you can deliver and run automation closer to the devices that need it.

The article further discusses:

• How do I protect my automation mesh network?
• Using a Certificate Authority
• Network security considerations

The Ansible Automation Platform installer takes care of configuring all your automation infrastructure firewall ports. This means the firewall policies and rules on Red Hat Enterprise Linux 8 or 9 are automatically configured when you deploy automation mesh. Whether you are beginning your automation journey or are a seasoned veteran, there are a variety of resources to enhance your automation knowledge with links in the article. Good read!

Command Query Responsibility Segregation (CQRS) with Domain Driven Design is more and more popular recently. Its implementation in PHP, which will be the topic of the article, generates some new possibilities, making a process more efficient. For example, it gives you the opportunity to restore the whole system easily. By Michał Żądło.

Before I step to the CQRS and Event Sourcing implementation in PHP - I’ll try to briefly explain what is the general concept behind CQRS. In 1986, Bertrand Meyer came up with an idea of Command Query Separation (CQS). According to the concept - each method in the object in its current state must belong to only one category out of the following two: command - a method which changes an object’s state, query - a method which returns the data.

The article deals with:

• Using Command Query Responsibility Segregation (CQRS pattern)
• What is Event Sourcing and Event Store?
• Pros and cons of Event Sourcing
• What is Broadway and what components it gives us?
• Write Model implementation
• Read Model implementation
• The change in requirements
• Snapshots
• CQRS and event sourcing - summary

… and more. Author advises you to invest some time and try this solution to decide whether or not it’s useful for you. You should also brush up on related topics such as event log, domain model, data store, event driven architecture, event processing or temporal queries. Excellent read full of in depth details about event sourcing with links to further reading!

It’s common to use APIs when working with external data sources on some features in Angular. However, you may occasionally work on a feature in parallel without immediate access to the database or API. By Muhammad Amir.

There are several ways to mock the same results. We will discuss three such approaches in this blog:

• Using json-server
• Using Postman
• Mocking data with a simple JSON file

Postman, which used to be a simple browser extension, is now a full-fledged API development toolkit. You can download it separately and install it on your system. To run the mock servers in Postman, we need an account and a workspace. The workspace allows you to easily share the mock server and other APIs with team members.

It’s easy to get started with json-server, and a basic requirement is a simple JSON file with data. There are also JavaScript libraries like MirageJS or axios-mock-adapter for similar purposes. Good read!

Making use of the existing layer cache as frequently as possible is key to speeding up Docker image builds. The less work we have to redo across builds, the faster our builds will be. By Kyle Galbraith.

In this post, we will look at reducing the overall image size, to improve build time and reduce the amount of data transferred in each image. We will use a popular open-source project, dive, to help analyze a Docker image, stepping through each individual layer to see what files it adds to the image and how it impacts the total image size.

The article consists of the following parts:

• dive into a Docker image
• Reducing image size
• Make use of .dockerignore
• Use smaller base images
• Leverage multi-stage builds
• Smaller images where possible

A multi-stage build allows you to specify multiple FROM statements in a single Dockerfile, and each of them represents a new stage in a build. You can also copy files from one stage to another. Files not copied from an earlier stage are discarded in the final image, resulting in a smaller image size. Nice one!

If you want to build a public landing page with Angular and email signup you likely don’t want to expose any secret keys, and author will show you how with Netlify cloud functions. By Simon Grimm.

In this tutorial we will connect a simple Airtable table as some sort of backend to store emails to our Angular landing page. We do this with the help of Netlify where we will both host our application and also deploy a cloud function!

In this tutorial you will find detailed steps explained for the following:

• Creating an Airtable table
• Creating the Angular project
• Creating the Angular landing page
• Adding a Netlify Cloud Function to the Angular project
• Host our Angular app with Netlify
• Adding Tailwind
• Adding Meta tags
• Teardown

To make this even more secure you could also make the cloud function only callable from your domain, but by preventing access to your key you’ve already taken the most important step to building a landing page with Angular. Good read!