As an engineer at Lexis, I would like to share some helpful bits of my experience solving complex business intelligence problems. Recently, I was assigned a rather daunting task of extracting financial information from over half a million documents of financial reports from various companies. This task, though challenging, allowed me to delve deeper into the applications of the more recent AI advances, mainly through OpenAI embeddings and vector databases, for business intelligence problems. How, you ask? Let's take a journey through the process in my comprehensive case study.

## The problem

We were tasked to extract key-value pairs from inconsistent structure and text from business documents. Therefore, we couldn't quickly develop an algorithm to solve the problem and had to implement a solution to leverage the new advances in LLM. We used a cloud solution to train an AI model to extract the key-value pairs. However, it was still pretty challenging to deal with the sheer volume of documents, as not all documents held relevant information, and if we had to process each page, not only would it take more time, but it would be much more expensive. Manually sifting through these documents would be even more time-consuming and economically unviable. The solution? A classification program that combines OpenAI embeddings and ChromaDB vector databases, using Pytesseract for Optical Character Recognition (OCR). 

Before we delve into how these technologies helped me overcome the challenge, let's understand what vector embeddings and vector databases are. 

### Vector embeddings

In a high-dimensional space, vector embeddings are mathematical representations of objects, such as words or documents, capturing semantic meanings based on their context. These vectors provide a way for algorithms to understand the content and context of documents. 

### Vector databases

Vector databases, on the other hand, are databases designed to store and query these vector embeddings efficiently. They enable us to perform similarity search at scale, which is critical in tasks such as semantic search, relatedness search, or, in our example - classification. 

### Implementation

This is where OpenAI and ChromaDB came into the picture. OpenAI provides a powerful tool to generate embeddings for our documents, while ChromaDB allows us to store and query these embeddings efficiently. By leveraging the power of vector embeddings and vector databases, we can classify documents based on how close their vector representations are, which will help us identify relevant pages in a document.

First, I split the PDF documents into individual pages. For each page, I created a MySQL record, applied OCR using Pytesseract, and generated an embedding using OpenAI. Using ChromaDB, I queried the page embedding with the embeddings of already classified pages (that I organized personally) stored in the vector database. The result of the query would give me the most related page to the one I am querying, and I would classify it with the same type, storing the type back in the database.

This process enabled me to filter out irrelevant pages, leaving only the ones that needed further processing. This streamlined the process and reduced the cost by about 80% of the original estimate.

### A basic example

I will give you a simple example to showcase an implementation of a Python program that does a similar job. To implement this solution, you'll need to create a MySQL database that contains the information for each image and a ChromaDB vector database, which you will use to query the vector embeddings.

Here's a simple schema for the MySQL database:

```sql
CREATE TABLE documents (
    id BIGINT UNSIGNED PRIMARY KEY,
    name VARCHAR(255),
    file_path VARCHAR(255), # path of the document in the filesystem
);

CREATE TABLE document_pages (
    id BIGINT UNSIGNED PRIMARY KEY,
    document_id BIGINT UNSIGNED,
    type ENUM(‘invoice’, 'balance_sheet’, ‘income_sheet’, ‘none), # here we store the type of the image once we classify it
    file_path VARCHAR(255),
    FOREIGN KEY (document_id) REFERENCES documents(id)
);
```

We need to manually classify at least a couple hundred images and save them in a folder. The assigned type of each image should be contained in the name of the image, separated by a dash, for example: ```'[name]-invoice.jpg'``` or ```'[name]-none.jpg'```. Then, we will embed these images into a ChromaDB vector database using the following example:

```python
import chromadb
import glob
import os
import pytesseract as pt
from openai import OpenAI
import uuid

openai = OpenAI('your-api-key')

client = chromadb.PersistentClient(path="chromadb")

# create the classification chromadb collection
classification_collection = client.get_or_create_collection(name="classification_collection",  metadata={"hnsw:space": "cosine"})

classified_images = glob.glob("classified_images/*.jpg") # the location of the folder containing the manually classified images

for classified_image in classified_images:
    # get base name of image
    image_type = os.path.basename(classified_image).split(".")[0].split('-')[1]

    # get the ocr text
    ocr_text = pt.image_to_string(classified_image)

    embedding = openai.embeddings.create(
        input=ocr_text.lower(),
        model="text-embedding-ada-002"
    ).data[0].embedding

    # embed the image in the chromadb database
    classification_collection.add(
        embeddings=embedding,
        metadatas={'type': classified_image.type},
        ids = str(uuid.uuid4())
    )

```
After creating the classification database, you can use the following Python code to perform OCR, generate embeddings, and classify the pages of a given document page:

```python
from models import DocumentPage
import chromadb
import pytesseract as pt
from openai import OpenAI

openai = OpenAI('your-api-key')

client = chromadb.PersistentClient(path="chromadb")

# create the classification chromadb collection
classification_collection = client.get__collection(name="classification_collection")

for DocumentPage in DocumentPage.all():
    # get the ocr text
    ocr_text = pt.image_to_string(DocumentPage.file_path)

    embedding = openai.embeddings.create(
        input=ocr_text.lower(),
        model="text-embedding-ada-002"
    ).data[0].embedding

    # embed the image in the chromadb database
    query = classification_collection.query(
        query_embeddings=embedding,
        n_results=1
    )

    DocumentPage.type = query['metadatas'][0][0]['type']

    DocumentPage.save()
```

## Conclusion

This simple example should illustrate the process of classifying images using the latest trends in LLMs and vector databases. The synergy of OpenAI embeddings and ChromaDB vector databases has revolutionized our approach to document classification, making it more efficient and cost-effective. 

The article has given you a glimpse into the power of AI tools in business intelligence. As we continue to explore and experiment, we are excited about the endless possibilities that AI holds for us, and we will keep sharing our insights about how we can use them in real-world scenarios.


Uncover how OpenAI and ChromaDB revolutionized financial data extraction, streamlining document classification for efficiency.

Unleashing the Power of AI in Business Intelligence: Document Classification using OpenAI and ChromaDB

clutch-2022

DigitalOcean Announcement

Bilyal Mestanov

deployment-cover photo

pexels-photo-4974922

Clutch Top Developers 2024

Nikola

Milush-photo

Stefan Mitov

Radoslav

freelance vs agency

the manifest cover-phoot

cypress-cover photo

Deyan Denchev

AI-instruments-2

Mira

CTO & Co-Founder

Nikola Popov

PHP / LARAVEL / DATABASES / SASS

Milush Karadimov

Software Developer

Radoslav Kosev

QA Engineer

Full Stack Developer

CEO & Co-Founder

Mira Ereeva

Growth Manager

At Lexis Solutions, our commitment to excellence has once again been recognized on a national level. We are proud to announce that for the second consecutive year, we've been honored as one of the top web development companies in Bulgaria by Clutch, a renowned B2B ratings and reviews platform.

![clutch-2024](//images.ctfassets.net/5gydaotbo8jm/59RD0sg8aB4xAh7PhQjJkD/2625ed73950e5a7fc27cdd39364d76d8/top_clutch.co_web_developers_bulgaria_2024.png)

Clutch is widely respected in the industry for its rigorous vetting process, which ensures that only genuine, high-quality reviews make it onto their platform. Their evaluations are rooted in direct client feedback, giving potential customers a clear picture of what it’s like to work with a company like ours.

In their [2024 analysis](http://clutch.co/bg/developers), Clutch has once again highlighted Lexis Solutions as a standout in the Bulgarian development scene. This recognition stems from the consistent praise and high ratings we've received from our clients, a testament to the dedication and skill our team brings to every project.

> "*Earning this accolade two years in a row is an incredible honor for our team. It reinforces our mission to deliver top-tier services that truly make a difference for our clients. We are grateful to everyone who took the time to share their positive experiences on Clutch. This achievement is a shared success between Lexis Solutions and our clients, who inspire us to strive for excellence every day.*"
> 
> Deyan Denchev, Co-Founder of Lexis Solutions.

At Lexis Solutions, we believe that every project is an opportunity to grow and refine our craft. The feedback we receive from our clients not only drives our success but also helps us continually improve and adapt to the ever-changing digital landscape.

As we look forward to the challenges and opportunities 2024 will bring, we remain committed to delivering innovative solutions that meet the evolving needs of our clients. If you have an exciting project in mind, we would love to discuss how we can bring your vision to life.

Clutch's 2024 team article about Lexis Solutions.


Lexis Solutions is a Clutch Top Web Development Company in Bulgaria for 2024

Imagine having a brilliant business idea bubbling with potential, just waiting to become a reality. But there's a catch: you need a developer to make it happen. The problem is the world is brimming with freelancers and development companies, all claiming to be the key to your dreams.  

When it comes to outsourcing, the path ahead can be murky. Hiring a freelancer is a different ballgame than enlisting a software development agency. An agency boasts a powerhouse team of specialized experts with unique skill sets. On the other hand, a freelancer may offer cost savings and flexibility. So, what path should you take when faced with the dilemma of freelancer vs. [software development agency](https://www.lexis.solutions/services/react-native-development)? Your decision today holds the power to shape the future success of your project.

Sorting through these choices can feel overwhelming. But fear not! Let's embark on another of Lexis Solutions' journeys to demystify the selection process.

The agency vs. freelancer quandary may appear deceptively simple, yet its implications must be balanced. Making the correct choice between an agency and a freelancer can transform your final product, for better or worse. So, let's dive headfirst and explore the ideal fit for your project.

## Embrace the freedom

When it comes to freelance developers, they operate in a world of boundless possibilities, offering not just one but three unique modes of engagement. Picture this: they can sign temporary contracts, take freelance gigs, or work remotely full-time. However, like any endeavor, there are risks to be mindful of when collaborating with freelancers, particularly as they juggle multiple projects simultaneously.

### Cost efficiency

The allure of freelance development lies in its ability to provide exceptional value for your investment. Freelancers, armed with nothing more than a trusty computer and an endless supply of caffeine, keep their expenses low and, as a result, offer rates significantly lower than those of software agencies. But remember, cost efficiency doesn't necessarily mean your entire project will come at a reduced price when you hire a freelancer.

### Revel in unparalleled flexibility

Many freelancers embrace working beyond traditional hours and remain responsive to communication. Liberated from the constraints of others' schedules, they can often work with unmatched adaptability, leading to quicker project delivery.

### Harness specialization

Freelancers are masters of their craft, honing their expertise in specific domains. Before bringing a freelancer on board, it's essential to carefully examine their portfolio to understand their specialized skill set. While some freelancers may tout themselves as Jacks-of-all-trades, we all know that true mastery lies in specialization. You can unlock remarkable results by aligning your unique talents with your project's requirements.

### The bad points

While the realm of freelance developers offers enticing advantages, it's crucial to be aware of the potential drawbacks that lurk beneath the surface. Let's shed light on the cons associated with working with freelancers:

### Questionable work quality 

Not all freelancers prioritize the quality of their deliverables. Generic platforms like Upwork need more rigorous vetting processes for their listed freelancers. This means you may encounter individuals solely driven by quick cash, rushing through projects without paying attention to the level of craftsmanship. For such freelancers, reputational risks hold little importance, as they can easily create new accounts or work anonymously.
Heightened risks

Freelancers present inherent risks due to their solitary nature. Even if your chosen freelance developer is highly reliable, unforeseen circumstances can disrupt your project. Without a contingency plan, your project may come to a screeching halt. It's essential to consider the potential consequences and have measures to mitigate those risks.

### Organizational challenges

Working with freelancers can introduce complexities as they juggle multiple clients simultaneously. This increased workload can lead to errors and delays in your product's development. It's crucial to clearly understand your freelancer's capabilities and establish realistic deadlines to minimize the chances of misunderstandings or poor outcomes.

### Vanishing acts

All terms and conditions have been meticulously defined, payments have been made, and the project is ready to take off. Suddenly, your chosen developer disappears into thin air. It may sound like a nightmare, but it's a scenario that can occur if you engage with unreliable freelance platforms or individual contractors lacking the proper means to ensure timely and consistent delivery.

## The triumphs of an agency

A successful outsourcing business typically has a diverse team of experts, including web/mobile app developers, testers, product managers, content creators, designers, analysts, and more. When you hire a development agency, you gain access to a professional support system that can handle all your work efficiently. Their reliability and accountability ensure adherence to work processes and procedures while prioritizing security.
Seamless teamwork

An agency is a pre-established team that has spent years refining its development strategies. While freelancers may not guarantee cooperation, agency employees work together seamlessly daily, fostering unparalleled teamwork and collaboration. Their familiarity with each other's strengths, weaknesses, and work habits enables them to navigate significant challenges effortlessly. No matter how many freelancers you hire, they won't match the level of cooperation an agency guarantees.

When choosing the right IT vendor for your project, consider consulting with top-tier companies through platforms like [Vendorland.com](https://vendorland.com "The voice of the global tech industry through independent research"), which specializes in helping businesses uncover the ideal partners to consult, design, and develop their software needs.

### Extensive expertise

The primary reason agencies cover more ground is their larger workforce. Even the most talented individual can only possess limited knowledge, making an agency more valuable when your project requires diverse areas of expertise. Each employee can specialize in a specific development phase, eliminating the need to search for additional resources. Furthermore, agencies can provide long-term benefits like maintenance, marketing, feature enhancements, and other valuable services by overseeing your product from start to finish.

### Superior quality

Freelancers generally produce high-quality work, but agencies often adhere to even more rigorous quality standards. While freelancers may complete a project without consideration, agencies employ strict review and QA processes. Additionally, freelancers usually need more resources available to agencies for thorough testing. How many independent freelancers have multiple phones for testing purposes?

### Ongoing maintenance & support

Reputable agencies prioritize building long-term customer relationships and upselling additional services. As a result, they are always ready to offer maintenance services, bug fixes, functionality modifications, and other refinements to the products they create or maintain.

### Accurate development estimation

Since most vendors charge hourly, knowing the time required to implement specific functionality by hiring a top software development company can eliminate concerns about unpredictable expenses is crucial. They usually have a well-defined project estimation process, accurately determining the development time required for each feature. And hiring a software development company is an excellent choice for startups and large corporations seeking unique skills, specific timelines, and a reliable contractor committed to project completion.

## Unveiling potential pitfalls

### Beware of hidden costs

When outsourcing software development, be mindful of potential hidden costs. Read the contract the software development company offers. Pay attention to any fine print that may reveal unexpected expenses.

Furthermore, remember that cheaper sometimes doesn’t mean better, especially for complex projects like software development. Opting for offshore developers with lower hourly rates may seem enticing initially, but it could result in higher costs in the long run. Conversely, although some developers may appear expensive initially, they may complete the project more efficiently, ultimately reducing the total cost.

### Increased security and business risks

While reputable software development companies pose minimal risks, hiring the wrong talent can complicate matters. Since software often collects users' data, mishandling or data breaches can have severe consequences. Consider the case of Meta, which was fined $276 million for a data leak impacting millions of Facebook users. Such incidents can be catastrophic for startups and small to medium businesses operating on limited budgets. Additionally, developers are at risk of mishandling sensitive information or intellectual property related to your project.

### Quality control challenges

Failure to properly vet software development companies can lead to partnering with organizations driven primarily by profits rather than a commitment to quality. Conduct thorough due diligence to mitigate this risk by reviewing companies' portfolios and customer feedback.

### Potential for non-delivery

There is always a possibility that the software development company you hire may fail to deliver as promised. They may disappear after collecting upfront costs, struggle to meet your requirements or expectations, provide a flawed product, or become unresponsive. Signing a contract and carefully reviewing its terms beforehand is crucial to protect yourself. Choosing a software development company in a country with a reliable justice system can provide legal recourse if you encounter exploitation.

### Language barriers and cultural differences

Hiring software developers fluent in English and capable of seamless verbal and written communication is advisable. This minimizes the risk of miscommunication and misunderstandings that could negatively impact your working relationship and project outcomes. Additionally, your developers' location in a different time zone may affect decision-making speed and issue resolution. Consider nearshore or onshore developers if this is a concern. Furthermore, be mindful of cultural and political disparities that could hinder effective communication and software development progress, such as cultural differences in values, opinions, and holidays.

## The end of the debate

When hiring a freelancer or a software development agency for your project, opting for a software development agency is a compelling choice. The numerous advantages agencies offer, such as seamless teamwork, extensive expertise, superior quality, long-term maintenance and support, and accurate development estimation, make them a preferred option for many businesses.

But remember, ultimately, the ideal choice depends on your project's requirements, budget, timeline, and risk tolerance. Careful evaluation of the pros and cons, thorough vetting of potential candidates, and clear communication of expectations are essential for making an informed decision that aligns with your project's goals.


Will you tread the freelancer's path of freedom or join forces with the agency's expertise to bring your vision to life?

Decoding the Dilemma: Freelancer or Software Development Agency?

## Automation QA's tests before having programming knowledge

## More focus on test design and application understanding

In the world of automation QA, when we first start, and we don't know much about programming, we mainly concentrate on really understanding the application as if we were the customer. This helps us create tests that act just like a regular person using the software, making sure we check it thoroughly in all kinds of situations. Of course, even after we learn programming, our dedication to understanding the application remains. But here's the important part: knowing how to code helps us do an even better job. We can create more advanced tests and make our testing methods more precise and efficient. This way, we keep testing the application like a real user while using our coding skills to do our job correctly.

### Preference for user-friendly automation tools

Additionally, testers with limited programming skills often prefer to stick to user-friendly automation tools with more intuitive interfaces that would require a minimal amount of coding, allowing them to create automated tests more quickly. One advantage here is that they can begin without facing the challenges related to programming languages, which is quite a time saver and lets them dive more into their field in detail.

### Preference for simple testing apps that offer test scripts

QAs who test software without knowing how to program often rely on online testing tools that record and save actions. After a test is registered, it can usually be modified so it can change what you do during different steps and also change the expected result. Such tools copy your interactions and record them in a way that's repeatable and faster than manual work. Later, they can modify them as you please, or you can create your own from existing samples. While they don't write code, we still make the most of what's already available to test software effectively. It's good to note, though, that generally, such online testing tools don't go beyond testing websites only.

### Reliance on regular collaboration with programmers

Given their limited programming expertise, testers often must collaborate more closely with programmers for help. This collaboration becomes essential for addressing script issues and inconsistencies and also handling more advanced automation tasks. 

Working closely with developers can be a valuable learning experience. It ensures that even if you lack programming skills, with enough effort - you can meet development standards and nurture devskills over time. Not to mention that when you start performing your tasks individually - programmers on their own don't have to worry about finding time to fix what you write. They focus on their part, you focus on yours, and productivity increases immeasurably. 

## Benefits of having programming knowledge

### Enhanced test-building skills

Having programming skills equips an automation tester with the ability to build sophisticated and comprehensive test scripts. They can create test scenarios that cover a more comprehensive range of inputs and conditions, resulting in more thorough testing. Additionally, the possession of programming skills allows testers to design tests that are reusable and maintainable, reducing the effort and time in the long run.

### Better debugging process

One aspect of testing, where the benefits of possessing programming skills are sure to make quite an impact, is debugging. Why? Knowing how to read code, analyze your test script errors, and identify issues with your strength saves your time, saves the programmer's time, and last but not least - boosts self-confidence. When a test fails, a QA with the above-mentioned "powers" can trace through the code and successfully pinpoint the problem's root cause and fix it efficiently. Self-education in debugging proves to be quite a utility to master.

Better data handling and validation of the software's behavior
Proficiency in programming enables automation testers to handle and manipulate testing data more effectively. How exactly? For instance, they can create scripts that simulate various users and check if a system differentiates between a new user, a premium user, and an admin. Or let's say they have to test an e-commerce website during which every time a user adds three different products to the cart - the price should be calculated correctly. Possessing skills to perform complex data validations and ensuring that the software behaves as expected under other conditions is an absolute must if we're talking about the reliability of test results.

### More effective collaboration with developers

As we can imagine, programming skills can be the way to "bridge the gap" between an automation QA and the developer for natural reasons, from engaging in relevant product discussions to understanding the code and communicating testing requirements clearly. All these mutual activities signify a more explicit workflow that will result in improved collaboration and communication. And on its own, this will reflect positively on every aspect of the working process.

## How the perspective changes with programming knowledge

### Writing less code that would do more

Acquiring programming knowledge transforms an automation QA's approach to test script development. The QA no longer needs to write long and repetitive code for every single test scenario. Instead, the focus shifts to designing functions and test suites that are somewhat optimized and efficient. Also, this will highlight a level of programming "hygiene" (writing less code while achieving broader test coverage), making the automation process better in the big picture.

### Designing more reusable tests/code

Programming knowledge enables automation QAs to design tests and code that are highly reusable. They can create scripts, functions, constants, and custom commands that can be applied to various test scenarios. It is making the test maintenance easier by far. Such focus on the reusability of the tests accelerates the test development process and proves helpful with fast adaptation of eventual testing of new add-ons to the project.
How programming knowledge boosts the prowess of automation QA

### Enhanced test-building techniques

With some programming skills, we QAs can apply applicable practices to our tests. For example, learning a little bit of HTML, CSS, and DOM tree basics is a good start that can help us to choose better elements to interact with. This means that the more you master them, the more logical assertions, combined with the custom mentioned above commands and costs, you will create. Another example from Cypress is including a well-built beforeEach hook that has saved me from writing the same things for more than 100 tests when I can write it as a precondition only once.

### Test efficiency improves

I've discovered that the power of thinking beyond the basics puts a green flag in your garden. From personal experience, I can tell you that testing a payment system does not include only filling in a card number and clicking the submit button. It's also crucial to not forget to test that you won't be able to pay with a non-active card, an expired one, or an empty one. So far, my programming skills allow me to design and execute tests beyond the standard user flow, ensuring that the payment system is thoroughly and creatively tested. 

### Error handling and reporting improve

Testers with an understanding of programming language can handle errors in their code better. As I already started walking that road, I can confirm that knowing to read your own code is a time saver for both you and the developer. And effective error handling, together with clear error reporting, is essential. A responsible QA also understands the importance of reporting errors that appear in the console during testing, even if they're not immediately visible. As we gain knowledge of programming, we start "speaking the same languages" with developers, so we learn to include the proper terminology like "validation," "verification," etc. 

### Test framework flexibility improves

Knowing more about programming helps us save some time in another way as well. Let's say you have to test a sports betting app on Android and iPhone - the user interface might vary with login buttons, input fields, etc., but that doesn't mean it's a bug. So, instead of writing a long script for two separate tests - you can use coding to adapt the script automatically to the respective system being tested. I already applied it to my approach to work, and it aged pretty well, saving me lots of writing.

## Can we, automation QAs, survive without programming?

Programming skills in automation testing are not a must. But when you want to raise the bar and perform different complex scenarios with your testing tool, you simply need them. Of course, you can always stick to manual work for the more complex tasks. Still, if you put effort and brainwork into learning a little programming and reach a level where no scenario is beyond your expertise to write - that's when you win at testing. Think of programming for automation, like having your own beach house. You can still live without a beach house, but having it kind of changes the horizon, doesn't it? So I suggest you consider building your own!

The Lexis' overview of how an automation QA experiences the testing process without any programming capabilities, why they are essential to acquire, how they change the QA's perspective, and whether testers can make ends meet without them.

Programming in Аutomation: Why is it as Еssential as having a Compass in the Wilderness?

Step into the realm of AI innovations once again! Previously, Lexis Solutions introduced you to some of the top [AI-powered tools](https://www.lexis.solutions/blog/ai's-toolbox-the-instruments-driving-innovation-part-one) for videos, content, and images. In this second chapter, get ready to hit all the right notes with a collection of tools for producing the ultimate music, audio, and design masterpieces.

## Music

### AIVA

[AIVA](https://www.aiva.ai/) is the AI-powered composer that crafts unique soundtracks for your every need. Whether for a gaming adventure, a marketing masterpiece, or a special event, this musical prodigy will generate the perfect score. Select a predefined style or upload your sound to guide AIVA's creative flow. 

### Supertone

Get ready to be amazed by the audio alchemy of [Supertone](https://supertone.ai/), the innovative Korean studio that blends art and technology to create music, voices, and more! They're the masters of speech enhancement, song revival, and dubbing - and if you want to hear ABBA singing in Korean, they've got you covered.

### Magenta

[Magenta Studio](https://magenta.tensorflow.org/studio/) comprises a set of music plugins that are constructed upon Magenta's open-source tools and models. Leveraging advanced machine learning methods for musical composition, Magenta is accessible both as an independent application and as an integrated plugin for Ableton Live.

### Orb Producer Suite

Assisting producers in crafting melodies, basslines, and wavetable synthesizer sounds, [Orb Producer](https://www.orbplugins.com/orb-producer-suite/) employs cutting-edge technology to generate limitless musical patterns and loops. These serve as inspirational foundations for musicians to build their creative ideas upon.

### MuseNet

Under the ownership and operation of OpenAI, [MuseNet](https://openai.com/blog/musenet/) can produce songs featuring a diverse range of up to 10 instruments spanning across 15 distinct styles. While MuseNet offers a rich array of AI-generated music for enjoyment, it must provide the functionality to create original music independently.

## Audio

### Cleanvoice 

Introducing [Cleanvoic](https://cleanvoice.ai/)e, the AI-powered solution tailored to enhance your podcasts or audio recordings by eliminating filler sounds, stutters, and unwanted mouth noises. You can easily upload your audio, allow the AI to perform its cleaning magic, and obtain the refined outcome effortlessly. Experience the benefits firsthand with a complimentary 30-minute trial, allowing you to explore its functionality and witness its effectiveness.

### FakeYou

[FakeYou](https://fakeyou.com/) is a text-to-speech generator offering diverse options featuring hundreds of voices. You can effortlessly select any voice and have it articulate the text you input. Whether it's the voice of your favorite actor, singer, or even your cherished animated character, the choices are abundant. It's a creative and entertaining means to prank a friend playfully, wouldn't you agree? And the best part? It's free.

### LALAL.AI

[LALAL.AI](https://www.lalal.ai/) emerges as an advanced AI audio tool, harnessing the capabilities of machine learning algorithms to swiftly and accurately accomplish this task. This exceptional AI system empowers you to effectively extract voices or instruments from audio files while preserving the original quality. By offering a complimentary 10-minute trial period, you can experience its prowess firsthand. Furthermore, another 5 minutes can be unlocked by simply following them on Reddit.

### Uberduck

[Uberduck](https://www.uberduck.ai/)'s text-to-speech technology boasts an impressive selection of over 5,000 expressive voices at your disposal, ready to enhance your voiceovers. This platform goes further by enabling you to replicate your voice. Whether for entertainment – like creating singing or rapping voices – or for professional endeavors, Uberduck caters to both. It's a dynamic tool offering versatile applications, including the creative and the commercial. With subscription plans commencing at just $10 per month, it's an accessible gateway to a world of vocal possibilities.

## Design

### Design Beast

[Design Beast](https://www.designbeastapp.com/Dashboard/Account/Login) is a comprehensive AI-powered design platform that unites many design functionalities into a single hub. Encompassing the Mockup Engine, Logo Factory, Image Editor, Object Remover, Background Remover, and Pixel Perfect tools, this platform emerges as a valuable solution, particularly for those who may not have a design background. Its vast library of pre-designed templates caters to various applications, offering a user-friendly experience. With pricing starting at an affordable one-time payment of $67, Design Beast provides a cost-effective avenue into the world of versatile and professional designs.

### Beautiful.ai

[Beautiful.ai](https://www.beautiful.ai/) boasts an array of customizable templates, a vast selection of stock photos and videos, audio track uploads, and collaborative functionalities to enhance your workflow. Subscription plans commence at $12/month, while the option to purchase individual projects is also available at $45 per project.

### Uizard

[Uizard](https://uizard.io/) can convert screenshots into editable designs and can even automatically transform your sketches into polished designs. Whether your focus is crafting landing pages, designing apps, or creating wireframes, Uizard offers an intuitive and efficient solution with its time-saving features. Uizard's innovative functionality comprehensively addresses your design needs.

### Tome

[Tome](https://tome.app/) crafts incredible presentations as a seamless experience. Enter your prompts into the command bar, and watch as Tome creates mesmerizing slideshows. Whether you're turning strategy papers, creative briefs, websites, or extensive content into engaging presentations, Tome has you covered.

Welcome back to the AI-powered world with Lexis Solutions! 

Innovating with AI instruments - Part Two

For over three years, we have relied on DigitalOcean's cloud infrastructure to deploy a myriad of applications, whether for our valued customers or our internal operations. The platform's seamless scalability, reliability, and user-friendly interface have ensured smooth deployments and operations, cementing our trust in its capabilities.

## Introducing DigitalOcean's Partner Pod Program

The Partner Pod Program is DigitalOcean's latest initiative aimed at creating a more partner-centric ecosystem. Unlike traditional partner programs, the Partner Pod allows partners to choose the benefits they receive, ranging from discounts and credits to Market Development Funds. This new approach provides a flexible partnership framework, ensuring a mutually beneficial relationship between DigitalOcean and its partners.

## Mutual Benefits: A Win-Win Scenario

Our customers stand to gain significantly through our partnership with DigitalOcean's Partner Pod. They will have access to a suite of cloud products, technical support, and training, which are essential for navigating the digital landscape effortlessly. Moreover, the co-marketing opportunities and marketing development funds provided through the Partner Pod Program will enable us to enhance our service offerings further. This partnership also signifies our continued commitment to leveraging cutting-edge technology to efficiently solve our customers' digital challenges.

## Navigating the Future Together

With the road ahead promising a plethora of opportunities, our partnership with DigitalOcean's Partner Pod is a testament to our resolve to elevate our service delivery continually. The collective expertise, shared knowledge pool, and synergy between Lexis Solutions and DigitalOcean will undoubtedly foster innovation, drive growth, and ensure our customers remain a step ahead in the digital curve.

---

Our journey with DigitalOcean's Partner Pod has set the stage for a collaborative venture that transcends traditional partnerships. It's not just about business growth; it's about setting new benchmarks in digital excellence, exploring the uncharted, and ensuring our clientele always has a competitive edge in the digital realm.

We're thrilled to announce our new strategic partnership with DigitalOcean Partner Pod, marking a milestone in our journey toward delivering superior digital solutions.

Lexis Solutions Joins the DigitalOcean Partner Pod Program

## Why choose Cypress

### Testing capabilities

Cypress has a friendly user interface that provides simple, human-friendly syntax, which makes it great for both beginners and experts. You can simulate user interactions like clicking buttons and filling out forms, making it perfect for testing your web applications thoroughly.

### Consistent cross-browser testing

Another of Cypress' benefits is that it supports multiple browsers, ensuring your application works well for all your users, regardless of which browser they prefer. In testing, this is helpful to identify and fix browser-specific issues early on in the development process.

### Community and documentation

Cypress has a relatively big community and excellent documentation. The community actively contributes, meaning you can find answers to your questions and difficulties. At the same time, there are also plenty of tips and even pre-written code snippets that are easily findable. Additionally, many people and channels contribute to the community by posting tutorials about practically everything you search for. There is also a well-maintained documentation website that provides clear explanations for every code snippet and good general guidance, making it easy to begin using Cypress and 
stay aware of the situation.

### Setting up your testing environment

__Installation and setup__

The first step in setting up your testing environment with Cypress is installing it on your device. Before attempting that, [make sure to check your device is compliant with the requirements from the documentation.](https://docs.cypress.io/guides/getting-started/installing-cypress#System-requirements) After that, you can start making a designated folder and name it correctly, as this will be your project folder. Afterward, open the code editor you prefer (I recommend VS Code, so let's use it for reference) and open the folder in the editor. The next step is to open your terminal in VS Code and to install Cypress in the project folder itself with the ```npm install Cypress --save-dev command```, after which, as soon as the installation finishes, you will have several files generated on the left side. By default, your tests will be written in the ```spec.cy.js``` file, but you can always change that and set it per your preferences. So far, this is all you need, and you can begin putting the configurations for your project.

[provided with freely accessible code from the article in a public Github repo for your convenience](https://github.com/radoslav-kosev/Cypress-Article-Reference-Code/commit/38d69947eab0ce8121f250f402f56da2fc5159a5)

__Project configuration__

In this step, you need to set the best testing environment specifications for your project, which you can do from [here](https://docs.cypress.io/guides/references/configuration). That means setting a specific browser to test with particular parameters like height and width, and you can also set a base URL to be tested, which means that you can avoid it as a step in your tests. Of course, some of these steps are non-obligatory, so excluding the ones you cannot test without, it is entirely up to you to set whatever pre-conditions you prefer. Remember that the available documentation will also give you plenty of other recommendations. You should check it out [here](https://docs.cypress.io/guides/references/configuration) to get some ideas. 

__Integrating with your application__

By this, I mean that before testing whatever website you're about to test, ensure it's accessible on the web and exceptionally reachable by Cypress. If it has any access limitations or restrictions, this would potentially interrupt the testing process or prevent it from starting.
Writing your first test

__Creating test files__

So, you set your project specifications, and now you must decide where to write your tests. Naturally, the first step is creating a test file, usually in the __e2e__ folder. Also, if your test file has a longer name - you can connect it with dashes - for example, ```'edit-my-profile-page.cy.js.'``` __Always remember that the extension for your testing suite files is not just ```.js``` it's ```.cy.js```.

Clear and precise name given to test files becomes a crucial part of keeping project cleanliness in time, and proper naming pays off as the number of tests increases. This is particularly evident for above, let's say, 100 tests.

__Writing the tests__

Here is the step where the essence of our job takes place: we begin writing tests. We will proceed here by considering that we already have test specifications prepared and reported test cases; now, we must transform the written scenarios into difficulties. 

Here is a simple overview of how it looks:

```js
describe('Most basic Google tests', () => {
    it('Successfully opens Google url', () => {
        cy.visit('https://www.google.com')
        cy.url().should(‘eq’, ‘https://www.google.com’)
    })
})
```

You begin by using ```describe()``` to define your whole test suite. It's good to clarify that the test suite contains as many tests as you want. Still, it's strongly recommended that all of them are related to one application module and that they are located in different folders - for example, the folder __Authentication__ should only contain the file ```authentication.cy.js```, the folder __Navigation__ bar should only contain ```navigation-bar.cy.js``` and likewise for home page, etc. If you're working on a more extensive website that can potentially have login options from a third party like Facebook or Google - you can have several files in the ```authentication.cy.js``` - one file for login with credentials, let's call it ```standard-login.cy.js```, Google login file called google-login.cy.js and a Facebook login file called ```facebook-login.cy.js```, etc. Let's analyze the test, which is supposed to check that the Google URL opens successfully. 

```js
describe(Most basic Google tests, () => { ... })
```

We give our suit a proper name (which often overlaps with the test file name)

```js
it('Successfully opens google.com', () => { ... })
```

Here is where we give our test a proper name specifically related to what it should do. This means that if the idea is for the test to visit a website successfully, then we should specify the "successful" part __*especially*__. That way, we can differentiate between positive and negative test scenarios еasier and not mess up with test names. After all, every test is supposed to test something different from all others, so the uniqueness in the name is a must.

```js
cy.visit('https://www.google.com')
```

The ```cy.visit()``` command instructs Cypress to visit a specific URL. This step cannot be skipped in any way, whatever you test, because Cypress is designed to test websites. Before writing your first command, it is an excellent reminder to refer to the documentation. Constant checks will save time, prevent code inconsistencies, and boost effectiveness.

```js
cy.url().should('eq', 'https://www.google.com')
```

In all honesty, this is the last but crucial part of the test, which a beginner QA is likely to forget once or twice. The *__assertion part__* is where we instruct our Cypress to compare the URLs it visited specifically and to check if they are __the same__. If they are not, Cypress didn't successfully visit the URL we told it to visit, or we were redirected, and the assertion will fail. And so will the whole test, respectively. 

__Running and debugging__

After writing our test, we can return to the terminal and note that the ```npx cypress``` is open to run Cypress. After that, click __E2E Testing__ from the window:

![cypress-1](//images.ctfassets.net/5gydaotbo8jm/78jCJtLqSdGKdMA7DEbkcw/8d72ffac46fa93880ece79f17ee493c6/1.png)

After you do that, this window will open:

![cypress-2](//images.ctfassets.net/5gydaotbo8jm/5QifhEKMH6cEGNiaMrcf76/92ff64aebb9ca01678aebdfbe46f65ed/2.png)

__Click Start E2E testing on the browser we choose;__ I recommend Chrome. That will open a new window containing the specs page. From here, you should select __Create new spec__:

![cypress-3](//images.ctfassets.net/5gydaotbo8jm/Kljp0yIokAD7XIzM1JhBs/c2ce7e10485bced6956a24b469d278ca/3.png)

And then you will see this:

![cypress-4](//images.ctfassets.net/5gydaotbo8jm/4hby1Qc1NelwT9g8TOy9iJ/44eaf57266abdc998b3cfef066f3aad9/4.png)

Directly click on Create spec and here:

![cypress-5](//images.ctfassets.net/5gydaotbo8jm/1rgAeIcTUJ68s2epBlkQWO/d21b74f66981fb235a2a8a5c807e08b5/5.png)

__Okay, run the spec.__
This will generate your first test from Cypress, and you can observe how the program runs the tests. 

The test will pass because everything assigned by default is correctly written. However, when we write a test, and it fails, Cypress offers a little bit of info to identify and fix the problem, such as what exactly __did not happen as expected__ and on __which line of code__ in your file. So you can inspect the application's state and understand why a test didn't behave as expected. 

You can now go back to your code editor at ```spec.cy.js```, the file that contains one automatically generated test, which is situated in the __e2e__ folder in __Cypress__ (```cypress/e2e/spec.cy.js```).

From here on, we can edit our file name according to our test coverage and edit the test correctly, like, for example, changing the name of the test suite, the name of the test itself, and also the website in the trial from example.cypress.io to www.google.com, the commands, etc., so that we can simply perform our first exploratory testing and see how Cypress works.

### Cypress best practices

__Pinpoint the objects you interact with__

Make the best possible use of the page elements (header, footer, login modal, search results field, etc.) when building your selectors. It will help you make a logically correct test that's easy to read and maintain. 
Let's say you're writing a test where you have to open a login modal via a button in the site's header. The right approach, in this case, is to incorporate the footer in the selector. Its ID can do this, or if it doesn't have one - by its __tag name__ and __class__. Chances are that you won't be the single QA in your company. Someone will look at your test and read: you open this site, in this site, you go to the footer, and within the footer, you click on a button that opens a login modal - plain and simple. It is understandable to read. 

I would also suggest that if you have no prior knowledge - you go through a crash course in HTML and CSS; it will expand your general idea of how they are built because we QAs interact with them all the time. 

__Write compact tests__

Think of test writing as if you're packing a suitcase - you want to include only the essentials, not have the whole house stuff. A proper test doesn't need to include steps that don't particularly add any use. You don't need to instruct Cypress to open a modal that doesn't need to be opened, just like you won't take knives and forks when you go to a restaurant. A compact test means no unnecessary code writing, saving time as unnecessary steps will not be executed. It's also a good idea to have your code prettier because it's natural to become messy when writing tests. A prettifier comes in handy to tidy up the code once you finish writing. [Here's the one I use for Visual Studio Code.](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode)

__Write versatile tests__

Writing versatile tests, from my perspective, means several things - in this case, we're talking about Cypress, which is JS-based. Therefore, almost all functions and capabilities of JS can be applied to test writing (such as loops, functions, variables, etc.) despite Cypress itself having its syntax. As for how to maximize the effectiveness of the tool to the best degree - we can make use of custom commands, for example. Suppose you have ten tests containing identical first two or three steps. You can combine the respective steps in one test. For example:

```js
Cypress.Commands.add('login', () => {
 cy.get('#username-input-field').type('My username')
 cy.get('#password-input-field').type('My password')
 cy.get('#login-button').click()
})
```

Afterward, this command, which we named 'login,' we can apply like this:

```js
describe('Authentication', () => {
  it('Successful login into the system', () => {
      cy.visit('https://www.mywebsite.com')
      cy.login()
      cy.url().should(‘contain’, ‘/profile’)
  })
})
```

This saves us the effort of writing the same steps for many tests and keeps tests cleaner, and when you make changes to the code, you just change only one place. All commands should be stored in the commands.js file, after which you can import them into the test file with 

```js
import '../../support/commands'
```

Also, include __constants__ in your tests to avoid magic numbers. If they're to be used in one test suite only, you can write them in the test files you're working with. Here is an example of how a constant can look if it's stored and used in one test file:

```js
const inputField = '#input-field’
```

However, if your const is to be used in three different test suites (which means three different files, respectively) - then you should consider creating a separate file called ```constants.js``` and store them there with the export keyword:

```js
export const PASSWORD_INPUT_FIELD = '#password-input-field’'
```

After that, to apply it in your desired test suite file, you should import it at the beginning of the file this way:

```js
import { PASSWORD_INPUT_FIELD } from '../../support/constants'
```

### Conclusion

For anyone considering a testing tool for their automation journey, I can confidently say that Cypress is an excellent choice. I've enjoyed using Cypress for over a year, and I can attest to its remarkable user-friendliness and various capabilities. If you're about to embark on your automation testing adventure, I strongly encourage you to try Cypress!

A brief overview of why Cypress is a great choice for testing, including installation, project setup, and optimal testing.

Cypress insider: How to set your Testing Environment and run your First Test


## A quick overview of Docker and Kubernetes

Before deploying our app to EKS, let's first quickly go over what Docker and Kubernetes are and how they help us deploy our applications. 

## Docker

Containerization is a technology that allows you to package your application and its dependencies into a single, portable unit called a container. Docker is the most popular containerization platform; it will enable you to encapsulate an application and its dependencies into a self-sufficient container, ensuring that it runs consistently across different environments, from a developer's PC to a production server. Docker containers are lightweight, fast to start, and easy to share, making them the ideal building blocks for modern applications. Containers ensure that what you develop and test locally behaves the same way in any environment where Docker is installed, eliminating the "but it was working on my machine" problem. All this helps speed up the development process, simplifies the deployment, and improves the overall reliability of applications.

## Kubernetes

On the other hand, Kubernetes is an open-source container orchestration platform that automates container deployment, scaling, and management. With Kubernetes, you can define how your applications should run, ensuring high availability, fault tolerance, and efficient resource utilization. 

A Kubernetes cluster comprises two fundamental components: the control plane (master node) and multiple worker nodes. The control plane oversees essential cluster-wide tasks like scheduling, scaling, and maintaining the desired state. On the other hand, the worker nodes serve as the execution engines, hosting pods—the smallest deployable units within Kubernetes. Each pod may contain one or more containers, sharing network and storage resources for efficient communication.  

Some of the main features of Kubernetes include: 

* __Orchestration:__ Kubernetes automates the deployment, scaling, and management of containerized applications, reducing manual work.
* __Load Balancing:__ It offers built-in load balancing for distributing network traffic to containers.
* __Auto-Scaling:__ Kubernetes can automatically scale the number of containers (pods) based on CPU or other metrics to handle changing workloads.
* __Self-Healing:__ It constantly monitors the state of your applications and automatically replaces containers if they fail.
* __Rolling Updates:__ Kubernetes supports rolling updates, allowing you to update your application without downtime or service interruption.
* __Resource Management:__ You can define and control resource limits and requests for CPU and memory, ensuring efficient resource utilization.

## Prerequisites

Before continuing with this article, make sure you have the following:

* An AWS account
* Access to the EKS (Elastic Kubernetes Service) and ECR (Elastic Container Registry) services on AWS
* The AWS CLI tool, we'll be using it to interact with the AWS services
* `kubectl`, the Kubernetes CLI tool
* `eksctl`, a CLI tool that will simplify our work with Amazon EKS, abstracting away the complexity of the AWS CLI
* Docker installed on your machine. We'll use it to build our app image and push it to the container registry

## Deploying the app

### Initial project setup

For this example, we will deploy a simple express hello world app. This is the initial project structure that we'll be working with

```text
hello-world-app
├── package.json
├── package-lock.json
└── src
    └── index.js
```

If we run the app, it should start on port 3000.

```sh
$ node src/index.js
App running on port 3000
```

And a `GET http://localhost:3000` request should return "Hello World!"

```sh
$ curl http://localhost:3000                          
Hello World!
```

## Containerizing the application

Before deploying our application to Amazon EKS, we need to build a Docker image and push it to Amazon's container registry. This registry serves as the centralized repository from which EKS retrieves the image, enabling the execution of our application in the cluster.

### Building the Docker image

Let's create two new files in the root directory of our project: "Dockerfile" and ".dockerignore".

```text
hello-world-app
├── package.json
├── package-lock.json
└── src
    └── index.js
├── Dockerfile
└── .dockerignore
```
Dockerfile is a script used to create a Docker image. It contains a series of instructions that describe how the image should be built. Here's the content of our Dockerfile:

```dockerfile 
FROM node:16

WORKDIR /app

COPY package*.json ./

RUN npm install

COPY . .

EXPOSE 3000

CMD ["node", "src/index.js"]

```
__Let's break it down line by line:__

* `FROM node:16`: This instruction specifies the base image for building this Docker image. In this case, it starts with a Node.js version 16 base image, which already includes Node.js and npm, making it suitable for Node.js applications.
* `WORKDIR /app`: This instruction sets the working directory within the image to /app. This is where the rest of the commands will be executed.
* `COPY package*.json ./`: Here, the `COPY` instruction copies the package.json and package-lock.json files from the host (the directory where the Dockerfile is located) to the /app directory within the image. 
* `RUN npm install`: You can use `RUN` to run any command during the build process. In this case, we use npm to install the dependencies specified in the package.json file. 
* `COPY . .`: This instruction copies all the files and directories from the host into the /app directory in the image. 
* `EXPOSE 3000`: The `EXPOSE` instruction informs Docker that the container will listen on port 3000 when it runs. 
* `CMD ["node", "src/index.js"]`: The `CMD` instruction specifies the default command to run when a container based on this image is started. In this case, it runs the Node.js application by executing node src/index.js within the container, starting our app.

The .dockerignore file tells Docker what files should be ignored during the build. In this case, we can add node_modules so it doesn't get copied into the docker image. While not required, this helps us keep the image size small and improve the build time.

Now that we've created the Dockerfile, we can build the image using the `docker build` command:

```sh
$ docker build -t hello-world-app .
```

Using the `-t` flag, we've specified what we want to name our image. The dot at the end tells Docker to look for the Dockerfile in the current directory. If it's somewhere else, or you named your script file differently, you can use the `-f` flag to pass Docker the path to the file. Once the command has been executed, you can run `docker images` to get a list of available images. The output should look something like this:

```sh
REPOSITORY  	 TAG  		   IMAGE ID 	   CREATED  SIZE TAG
hello-world-app  ec5cdedc65fc  26 seconds ago  861MB    latest
```

### Pushing the image to ECR

Now that we've built the image, it's time to create a repository in ECR and push it there.

To create the repository, run the following command:

```sh
$ aws ecr create-repository --repository-name hello-world-app
```

You should see output similar to this:

```json
{
    "repository": {
        "repositoryArn": "arn:aws:ecr:eu-central-1:721145219880:repository/hello-world-app",
        "registryId": "721145219880",
        "repositoryName": "hello-world-app",
        "repositoryUri": "721145219880.dkr.ecr.eu-central-1.amazonaws.com/hello-world-app",
        "createdAt": "2023-10-05T13:26:15+03:00",
        "imageTagMutability": "MUTABLE",
        "imageScanningConfiguration": {
            "scanOnPush": false
        },
        "encryptionConfiguration": {
            "encryptionType": "AES256"
        }
    }
}
```

Take note of the `repositoryUri` value, which we'll use later to push our image to the repository and deploy it to the Kubernetes cluster. Still, before that, since this is a private repository, we need to authenticate Docker first. To do this, you can run the following command with your region and account ID:

```sh
$ aws ecr get-login-password --region [region] | docker login --username AWS --password-stdin [aws_account_id].dkr.ecr.[region].amazonaws.com
```

You will get a "Login Succeeded" message in the console if it succeeds.

Now that we've authenticated Docker, we can push our image to the repository. We must tag it with a specific value using the repositoryUri: `[repositoryUri]:[tag]`. The tag value here can be anything: an image version, "latest", or anything else that makes sense in your case. Then, you can run `docker push` with the same value you tagged the image with:

```sh
$ docker tag hello-world-app 721145219880.dkr.ecr.eu-central-1.amazonaws.com/hello-world-app:latest
```

```sh
$ docker push 721145219880.dkr.ecr.eu-central-1.amazonaws.com/hello-world-app:latest
```

Once the command executes, you can confirm that the image has been pushed to ECR by running:

```sh
$ aws ecr list-images --repository-name hello-world-app
```

```json
{
    "imageIds": [
        {
          "imageDigest": "sha256:511a3e2fef5790fca4ac7b03fec6dba0b5339c4acea8a74b7f1ea3fc16f5904f",
            "imageTag": "latest"
        }
    ]
}
```

With this, we've successfully built our image and pushed it to ECR. Now, it's time to deploy it to EKS.

## Deploying the app to EKS

First, we'll need to create a new cluster in EKS:

```sh
$ eksctl create cluster --name hello-world-app --region eu-central-1
```

Creating a new cluster might take a while. Once the command finishes executing, you should see in the terminal that it has created a new config file. In my case, it was at `~/.kube/config`. This file contains the credentials necessary for `kubectl` to access our cluster. 

We will create two new files to deploy the app to the Kubernetes cluster: `k8s/deployment.yaml` and `k8s/service.yaml`. 

```text
hello-world-app
├── k8s
	├── deployment.yaml
    └── service.yaml
├── package.json
├── package-lock.json
└── src
    └── index.js
├── Dockerfile
└── .dockerignore
```

The deployment.yaml file describes how the container should be run within the cluster. Here, we can specify the number of replicas, docker image, env variables, etc. On the other hand, the service.yaml file allows us to connect our app to a network. Let's examine the files' contents and explain them in more detail.

First the deployment.yaml file:

```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-world-deployment
spec:
  replicas: 2
  selector:
    matchLabels:
      app: hello-world
  template:
    metadata:
      labels:
        app: hello-world
    spec:
      containers:
      - name: hello-world-container
        image: 721145219880.dkr.ecr.eu-central-1.amazonaws.com/hello-world-app:latest
        ports:
        - containerPort: 3000
```

* The `apiVersion` and `kind` fields are used to specify the kind of Kubernetes resource that's being defined. In this case it's deployment, which is used for deploying containerized applications. Still, many other resource types exist, like ConfigMap for storage configurations or PersistanceVolume for storage.
* The `metadata` section contains metadata about the deployment. 
* The `spec` section contains information about the deployment itself:
    * `replicas` specifies the number of running instances of your application.
    * `selector` defines what selector we can use later on to identify pods managed by this deployment
    * `template` contains the template of the pods. Here, we've configured the container, for example, what image should be used and what port is exposed. Here, you can also set other things, such as env variables, CPU and memory limits, data volumes for the container, and so on.

	And here's the service.yaml file:

```yaml
apiVersion: v1
kind: Service
metadata:
  name: hello-world-service
spec:
  selector:
    app: hello-world
  ports:
    - protocol: TCP
      port: 80
      targetPort: 3000
  type: LoadBalancer
```

The service.yaml file will allow our deployment to connect to a network. In this case, the service will listen to port 80 and route the traffic to the container on port 3000.

One of the more important fields in this resource type is the type field, which decides who can access the app. There are four possible values:

* ClusterIP - the deployment won't be publicly accessible. It can only be accessed by other apps within the Kubernetes cluster.
* NodePort - this service type will open a port that we specify on all nodes in the cluster, making the deployment publicly available
* LoadBalancer - This is another way to expose the deployment to public access. Still, it only works if you use Kubernetes with a cloud provider that supports it (AWS, in our case). It will create a load balancer service to route the traffic to our pods.
* ExternalName - this will map our service to a DNS name. We can specify the name with the `spec.externalName` field.

And now, we're ready to deploy the app to the cluster by calling `kubectl apply` to apply the changes that we defined earlier to our cluster:

```sh
$ kubectl apply -f k8s/deployment.yaml 
deployment.apps/hello-world-deployment created
```

```sh
$ kubectl apply -f k8s/service.yaml   
service/hello-world-service created
```

Once this is done, we can check whether everything has been appropriately deployed by running:

```sh
$ kubectl get all

NAME  										READY 	STATUS  RESTARTS 	AGE
pod/hello-world-deployment-574fbf949b-5xcrf 1/1 	Running 0  			4m
pod/hello-world-deployment-574fbf949b-bfghm 1/1 	Running 0  			4m

NAME  						TYPE 			CLUSTER-IP  	EXTERNAL-IP PORT(S)  												 					AGE
service/hello-world-service LoadBalancer 	10.100.159.38 	a2c68e692ec944c48a22d7a8b10aff98-2831416.eu-central-1.elb.amazonaws.com 80:30955/TCP 	4m
service/kubernetes  		ClusterIP  		10.100.0.1  	<none>  443/TCP  																		17m

NAME 									READY 	UP-TO-DATE AVAILABLE 	AGE
deployment.apps/hello-world-deployment 	2/2 	2  			2 			4m

NAME  												DESIRED CURRENT READY	AGE
replicaset.apps/hello-world-deployment-574fbf949b 	2 		2 		2 		4m
```
Here, we can see all resources deployed to the cluster, including our two instances and the service. For `service/hello-world-service`, we can see it has been assigned an external IP address. Using that, we can test our app:

```sh
$ curl a2c68e692ec944c48a22d7a8b10aff98-2831416.eu-central-1.elb.amazonaws.com
Hello World!
```

As we can see, everything is working correctly. With this, we've finished our deployment.

You can find the complete project from this article here: https://github.com/lexis-solutions/kubernetes-demo.

### Conclusion
This article covers the basics of Docker and Kubernetes, essential components in modern application deployment. However, it's important to note that Docker and Kubernetes are vast and intricate topics with numerous advanced features and capabilities waiting to be explored. While we've provided a solid foundation to get you started, there's much more to discover and master in these powerful technologies.


Lexis Solutions guides you through the process of containerizing and deploying your application on an Amazon Web Services Kubernetes cluster using Elastic Kubernetes Service.

Deploying Your App to AWS Kubernetes with EKS: A Step-by-Step Guide

There are many good reasons why you should consider creating your own website for your business. From reaching more people and customers from all over the world to increasing your overall sales, having a website is crucial to your success in the digital age. Don’t let this opportunity slip away, get to work and start developing your own website with the support of our Lexis Solutions team.

We're on a mission to create amazing digital products for innovative ideas. Since 2017, we have worked with thriving businesses as their technological partner. Our skilled staff is dedicated to offering custom software solutions that properly match your vision while assuring excellent project management and transparent communication.

And today, we are delighted to announce that our team has recently accomplished a massive milestone for this year. Our company has been recently named one of the most-reviewed web development companies in Bulgaria by none other than The Manifest.

The Manifest, for those of you who don’t know, is [a business blog and reviews platform ](http://themanifest.com/bg/web-development/companies?utm_source=directory&utm_medium=blog&utm_campaign=TM+Awards)that aims to gather and verify the hard data, expert insights, and actionable advice that you need to build your brand and grow your business – to provide the practical business wisdom that manifests in your success.

This award wouldn’t have been possible without your support, yes you! You, our clients and partners, played a significant role in helping us bag this award. Our team is thankful for supporting our business throughout the years, you guys are awesome! 

[Let’s talk about your project.](https://www.lexis.solutions/contact-us) We’re a team of developers, designers, and strategists who work with companies of all sizes to design, build, and grow digital products.

The Manifest highlights another achievement by Lexis Solutions' team! 

From the front lines

Unleashing the Power of AI in Business Intelligence: Document Classification using OpenAI and ChromaDB

Latest articles

Lexis Solutions is a Clutch Top Web Development Company in Bulgaria for 2024

Decoding the Dilemma: Freelancer or Software Development Agency?

Programming in Аutomation: Why is it as Еssential as having a Compass in the Wilderness?

Innovating with AI instruments - Part Two

Unleashing the Power of AI in Business Intelligence: Document Classification using OpenAI and ChromaDB

Lexis Solutions Joins the DigitalOcean Partner Pod Program

Cypress insider: How to set your Testing Environment and run your First Test

Deploying Your App to AWS Kubernetes with EKS: A Step-by-Step Guide

The Manifest Recognizes Lexis Solutions as one of the Most Reviewed Web Developers in Bulgaria