vTual v.0.1 is (kinda) Almost Ready For Public Launch

Personally the year 2024 has proven to be both long and challenging for me, as various circumstances have compelled me to embrace the role of an "indie" -- whether as a small-scale content creator or even as a professional programmer. In a rough sentence, I might be considered as NEET.

But despite the hurdles, this journey has led me to the realization of something quite rewarding and fulfilling.

What Is Going On?

I am so thrilled to announce that the vTual Project, a simple pilot concept that I have envisioned since 2022, finally come to fruition: It is almost ready for public launch!

The term "almost" is used because there are still a few minor adjustments needed before the project can be fully released to the public, as these adjustments primarily involve the implementation of certain development ideas and infrastructure improvements.

Development

In terms of feature implementation and system optimization, I can confidently say that vTual v.0.1 is essentially complete and aligns well with the initial targets we set. Like external needs, such as the request for an increase in API quota from the YouTube team, have also been successfully approved. Quota optimization for both Youtube and Twitch API is also done.

However, there are a few minor additional internal features, such as a fanbox, that I would like to incorporate into vTual.

If these enhancements do not disrupt our schedule, I plan to integrate them into v.0.1. However, if it appears that adding these features could potentially delay the release, I will prioritize them for inclusion in the roadmap for v.0.2 instead.

This approach ensures that we maintain our timeline while still considering valuable improvements for future versions.

Infrastructure

We all know that vTual, as a project, will need to store and process a significant amount of data. The volume of data involved may well exceed anything I have handled throughout my career as a programmer so far.

Furthermore, vTual will also play a crucial role as my portfolio as a programmer, showcasing my skills and real-life expertise in a tangible way.

And most importantly, I have a deep personal affection for vTual, embracing both its strengths and its shortcomings.

With countless reasons highlighting the importance of vTual to me personally, there is no justification that could deter me from splurging investing in its infrastructure.

The next paragraph will be particularly fascinating if you are a nerd intrigued by the foundational infrastructure utilized by vTual.

After conducting several experiments and carefully considering the operational costs, we can conclude that the current details of the infrastructure lineup are as follows:

Server for Web Server

To operate vTual effectively, the current server infrastructure designated for web server purposes has the following specifications: Powered by 4 cores of EPYC 9554 Genoa, equipped with 16 GB of RAM, NVMe storage and a premium network port of 2 Gbps. Premium DDoS protection is also included in the hundreds of Gbps figure.

The server operates on a high-availability cloud hosting model, which means that all components are designed to perform auto-healing in the event of a failure in any part of the system.

These specifications have been carefully selected to ensure optimal performance and reliability, allowing us to meet the demands of our users while providing a seamless experience.

Server for Database Server

To operate vTual more effectively, I have allocated specific server for database-management purpose that has the following specifications: Powered by 4 cores of EPYC 7443P Milan, equipped with 16 GB of RAM, NVMe storage and a premium network port of 2 Gbps. Premium DDoS protection is also included in the hundreds of Gbps figure.

The server provider and it's location is the same as that used for web server purposes that i mentioned above; however, the node are different to ensure redundancy in case of a failure in one of the nodes.

Data processing will also require intensive read performance for the database, which is why I have added two slaves servers with following specifications: Each of these slaves are equipped with 2 cores of EPYC 7401P Naples, 4 GB of RAM, NVMe storage and a network port of 1 Gbps.

This slave server comes from a different provider and does not offer significant performance or robust features compared to the main server. However, considering that it is intended solely as a supplementary server, I believe it is more than adequate for our current needs.

Unused Server

I have written before about the reasons for the changes in infrastructure used by vTual.

At present, there are approximately two unused servers that have been purchased for the long term. These idle servers are located in the Southeast Asian (SEA) region, specifically in Indonesia and Singapore.

The main reason for opting for a long-term purchase was the opportunity to benefit from discounted prices when acquired on an annual basis.

But tldr; The server market offered by Europe presents more "strength" with relatively stable pricing that is easier on the budget. As a result, the operational infrastructure has been relocated to Europe!

Nevertheless, these servers will still be utilized for other beneficial purposes that contribute to the advancement of vTual. One of the ideas currently being developed is to prepare them for use as game servers.

This initiative not only allows us to maximize the potential of our existing resources but also opens up new opportunities for engaging with our audience in the gaming community.

By repurposing these servers, we aim to enhance our offerings and create a more dynamic environment for users, ultimately driving growth and innovation within the vTual platform.

Absolutely Stupid

So far I must admit that the development of vTual has been quite an intense journey.

Beyond the fact that vTual is built on an open-source project (under Laravel, Composer and it's environment), I have undertaken all the research and development on my own, starting from the ground up as a newbie programmer. The process has been both challenging and rewarding, as it has required me to dive deep into various aspects and concept of software development.

I must also acknowledge that the expenses associated with running the infrastructure are neither cheap nor easy to manage. The development of vTual has indeed taken a toll on me, both physically and mentally, as well as financially.

Do you want to hear the craziest part? After all the effort, hard work, and investment I've put into this project; I have yet to even consider issues related to promotion and monetization strategies to ensure that the entire infrastructure can eventually be financially sustainable.

In short, the series of events surrounding vTual has been reckless and stupidly stupid. However, despite all the chaos, I truly love the journey it has taken me on.

Every effort I make is aimed at ensuring that vTual operates smoothly and meets the necessary requirements, so one or hundreds of trials seem necessary to face in order to achieve maturity for vTual as a product.

Public ETA

November will conclude with the organization of our infrastructure, and December is likely to be dedicated to testing sessions.

Given this timeline, the earliest estimated time of arrival (ETA) I can provide for public access is early 2025.

Memento

From overthinking...

...to countless brainstorming that won't fit the image...

...VNS, the foundation of vTual was born.

Fucking big thanks to these two distinguished middlelight resident.