Header image

TypeScript – How To Avoid “Any”?

26/09/2022

1.7k

  • The harmful effects of any
  • Avoiding any
TypeScript - How To Avoid "Any"?

How to avoid any?

In the previous blog – Typescript and “any” type, I introduced TypeScript and what exactly is any type.

In this blog, I’d like to show more about the harmful effects when using any and introduce some built-in types, features and customs types that you can use to avoid any.

The harmful effects of any

While TypeScript is a type checker, any type tells TypeScript to skip/disable type-checking. On the other hand, due to the nature of JavaScript, in some cases providing accurate types isn’t a simple task. In such situations, programmers are tempted to use any.

In most situations using or implicit any – a type that allows to store anything and skip type checkers, programmers can’t guarantee what type the value is stored and how it will be used. Furthermore, when the code is executed at runtime, errors may occur even though they were not warned before. For example:

let result; // Variable 'result' implicitly has an 'any' type.
result = 10.123; // Number is stored at 'result'

console.log(result.toFixed()); // `toFixed()` is a method of `number`

result.willExist(); // `willExist()` isn't a method of `number`, but no errors appear.

Because of that, the use of any is something that should be minimized as much as possible, to ensure the source code does not encounter any errors.

Avoiding any

Based on the basics of TypeScript and Everyday Types, in this blog, I’ll be sharing what I learned and used to write code without any.

Type aliases & Interfaces

A type alias is exactly a name for any type, you can actually use a type alias to give a name to any type at all, not just an object type. For example:

// Type alias
type Point = {
  x: number,
  y: number
};

type ID = number | string;

An interface declaration is another way to name an object type:

// Interface
interface IPoint {
  x: number,
  y: number
};

Differences between Type Aliases and Interfaces:

// Override
type Point = { // TypeError: Duplicate identifier 'Point'.
  a: string
};
interface IPoint {
  a: string
};

Union & Literal types

A union type is a type formed from two or more other types, representing values that may be any one of those types.

// Union types
let anyNumber: string | number;

// Usage
anyNumber = '123';
anyNumber = 123;
anyNumber = true; // TypeError: Type 'boolean' is not assignable to type 'string | number'.

In addition to the general types of string and number, you can refer to specific value of strings and numbers.
By combining literals into unions, you can express a much more useful concept. For example:

// Literal types
let direction: 'top' | 'left' | 'right' | 'bottom';

direction = 'top';
direction = 'top-right'; // TypeError: Type '"top-right"' is not assignable to type '"top" | "left" | "right" | "bottom"'

Type assertions

Sometimes you will have information about the type of a value that TypeScript can’t know about.

For example, if you’re using document.getElementById, TypeScript only knows that this will return some kind of HTMLElement, but you might know that your page will always have an HTMLCanvasElement with a given ID.

In this situation, you can use a type assertion to specify a more specific type:

// Type assertions
const myCanvas = document.getElementById('main-canvas') as HTMLCanvasElement;

Generics

// Example
const getRandomNumber = (items: number[]): number => {
  let randomIndex = Math.floor(Math.random() * items.length);
  return items[randomIndex];
};
const getRandomString = (items: string[]): string => {
  let randomIndex = Math.floor(Math.random() * items.length);
  return items[randomIndex];
};

// Generics function
const getRandomGeneric = <T>(items: T[]): T => {
  let randomIndex = Math.floor(Math.random() * items.length);
  return items[randomIndex];
};

// Usage
const teams: string[] = ['frontend', 'ios', 'android'];
const numbers: number[] = [1, 2, 3, 4, 5, 6, 7, 9, 10];

const randomResult1 = getRandomGeneric<string>(teams);
const randomResult2 = getRandomGeneric<number>(numbers);

In the example above, the getRandomGeneric is the generic identity function that worked over a range of types.

The type of generic functions is just like those of non-generic functions, with the type parameters listed first, similarly to function declarations:

const identity = <Type>(param: Type): Type => {
  return param;
};

When calling identity a function, you now will also need to specify the type of param that the function will use.

The detail above just Generic identity functions, you can read more generics Generic link

Unknown

unknown is what should be used when you don’t know a proper type of object. Unlike any, it doesn’t let you do any operations on a value until you know its type (skip/disable type-checker).

When you unknow something, you need to check before executing. For example:

const invokeAnything = (callback: unknown): void => {
  if (typeof callback === 'function') {
    callback();
  }
  if (typeof callback === 'number') {
    console.log(callback);
  }
  if (typeof callback === 'string') {
    console.log(callback.toUpperCase());
  }
};

// Usage
invokeAnything('typescript'); // Result: TYPESCRIPT

Record for basic object

Probably, nearly every JavaScript developer at some time has used an object as a map-like collection. However, with strict types, it may not be that obvious how to type this. So, you may use interface, but this way you can’t add anything to the object. Then, you need to think about using Record.

The definition:

type Record<K extends keyof any, T> = {
  [P in K]: T;
};

And the usage:

// Usage
const dict: Record<string, number> = {};
dict.a = 1;
dict.b = 'a'; // TypeError: "a" is not assignable to type number

let obj: Record<string, number>;
obj = {
  a: 1,
  b: 2
};

As you can see, it means that the developer can enter any key, but the value has to be of a specific type.

Conclusion

The TypeScript compiler is so powerful. There are so many things we can do with it.

any type can be avoided with more advanced technics such as interface, type intersection, and the use of generics, etc.

Hope you like it! Enjoy TypeScript and make the code without any!

Author: Anh Nguyen

Related Blog

prd-thumb-draft-product

Software Development

+0

    TypeScript And “Any” Type

    TypeScript is a strongly typed programming language that builds on JavaScript, giving you a better ability to detect errors and describe your code. But sometimes you don't know the exact type of value that you're using because it comes from user input or a third-party API. In this case, you want to skip the type checking and allow the value to pass through the compile check. The TypeScript any type is the perfect solution for you because if you use it, the TypeScript compiler will not complain about the type issue. This blog will help you understand the any type in TypeScript, but before doing that, let's begin with some basic concepts! What is TypeScript? TypeScript checks a program for errors before execution and does so based on the kinds of values; it’s a static type checker. Superset of JavaScript TypeScript is a language that is a superset of JavaScript: JS syntax is, therefore, legal TS. However, TypeScript is a typed superset that adds rules about how different kinds of values can be used. Runtime Behavior TypeScript is also a programming language that preserves JavaScript's runtime behavior. This means that if you move code from JavaScript to TypeScript, it is guaranteed to run the same way, even if TypeScript thinks the code has type errors. Erased Types Roughly speaking, once TypeScript’s compiler is done with checking your code, it erases the types to produce the resulting compiled code. This means that once your code is compiled, the resulting plain JS code has no type information. An easy way of understanding TypeScript A languageA superset of JavaScriptPreserver the runtime behavior of JavaScriptType checker layer JavaScript + Types = TypeScript Basic typing Type annotations TypeScript uses type annotations to explicitly specify types for identifiers such as variables, functions, objects, etc. // Syntax : type Once an identifier is annotated with a type, it can be used as that type only. If the identifier is used as a different type, the TypeScript compiler will issue an error. let counter: number; counter = 1; counter = 'Hello'; // Error: Type '"Hello"' is not assignable to type 'number'. The following shows other examples of type annotations: let name: string = 'John'; let age: number = 25; let active: boolean = true; // Array let names: string[] = ['John', 'Jane', 'Peter', 'David', 'Mary']; // Object let person: { name: string; age: number }; person = { name: 'John', age: 25 }; // Valid // Function let sayHello : (name: string) => string; sayHello = (name: string) => { return `Hello ${name}`; }; Type inference Type inference describes where and how TypeScript infers types when you don’t explicitly annotate them. For example: // Annotations let counter: number; // Inference: TypeScript will infer the type the `counter` to be `number` let counter = 1; Likewise, when you assign a function parameter a value, TypeScript infers the type of the parameter to the type of the default value. For example: // TypeScript infers type of the `max` parameter to be `number` const setCounter = (max = 100) => { // ... } Similarly, TypeScript infers the return type to the type of the return value: const increment = (counter: number) => { return counter++; } // It is the same as: const increment = (counter: number) : number => { return counter++; } The following shows other examples of type inference: const items = [0, 1, null, 'Hi']; // (number | string)[] const mixArr = [new Date(), new RegExp('\d+')]; // (RegExp | Date)[] const increase = (counter: number, max = 100) => { return counter++; }; // (counter: number, max?: number) => number Contextual typing TypeScript uses the locations of variables to infer their types. This mechanism is known as contextual typing. For example: document.addEventListener('click', (event) => { console.log(event.button); // Valid }); In this example, TypeScript knows that the event the parameter is an instance of MouseEvent because of the click event. However, when you change the click event to the scroll the event, TypeScript will issue an error: document.addEventListener('scroll', (event) => { console.log(event.button); // Compile error }); // Property 'button' does not exist on type 'Event'. TypeScript knows that the event in this case, is an instance of UIEvent, not a MouseEvent. And UIEvent does not have the button property, therefore, TypeScript throws an error. Other examples of contextual typing // Array members const names = ['John', 'Jane', 'Peter', 'David', 'Mary']; // string[] names.map(name => name.toUpperCase()); // (name: string) => string // Type assertions const myCanvas = document.getElementById('main-canvas') as HTMLCanvasElement; Type inference vs Type annotations Type inferenceType annotationsTypeScript guesses the typeYou explicitly tell TypeScript the type What exactly is TypeScript any? When you don’t explicitly annotate and TypeScript can't infer exactly the type, that means you declare a variable without specifying a type, TypeScript assumes that you use the any type. This practice is called implicit typing. For example: let result; // Variable 'result' implicitly has an 'any' type. So, what exactly is any? TypeScript any is a particular type that you can use whenever you don't want a particular value to cause type-checking errors. That means the TypeScript compiler doesn't complain or issue any errors. When a value is of type any, you can access any properties of it, call it like a function, assign it to (or from) a value of any type, or pretty much anything else that’s syntactically legal: let obj: any = { x: 0 }; // None of the following lines of code will throw compiler errors. // Using `any` disables all further type checking, and it is assumed // you know the environment better than TypeScript. obj.foo(); obj(); obj.bar = 100; obj = 'hello'; const n: number = obj; Looking back at an easier-to-understand any: A special type.Skip/Disable type-checking.TypeScript doesn't complain or issue any errors.Default implicit typing is any. Note that to disable implicit typing to the any type, you change the noImplicitAny option in the tsconfig.json file to true. Why does TypeScript provide any type? As described above, while TypeScript is a type checker, any type tells TypeScript to skip/disable type-checking. Whether TypeScript has made a mistake here and why it provides any type? In fact, sometimes the developer can't determine the type of value or can't determine the return value from the 3rd party. In most cases they use any type or implicit typing as any. So they seem to think that TypeScript provides any to do those things. So, is that the root reason that TypeScript provides any? Actually, I think there is a more compelling reason for TypeScript providing any that the any type provides you with a way to work with the existing JavaScript codebase. It allows you to gradually opt-in and opt out of type checking during compilation. Therefore, you can use the any type for migrating a JavaScript project over to TypeScript. Conclusion TypeScript is a Type checker layer. The TypeScript any type allows you to store a value of any type. It instructs the compiler to skip type-checking. Use the any type to store a value when you migrate a JavaScript project over to a TypeScript project. In the next blog, I will show you more about the harmful effects of any and how to avoid them. Hope you like it! See you in the next blog! Reference TypeScript handbookTypeScript tutorial Author: Anh Nguyen

    07/09/2022

    1.19k

    Software Development

    +0

      TypeScript And “Any” Type

      07/09/2022

      1.19k

      Our culture

      +0

        From Seeking The Path to Leading The Way: Phuoc’s Journey at SupremeTech

        Are you curious how someone with no IT background made a bold leap into tech and ended up leading a team? Starting with no formal IT background, Phuoc took a leap of faith into the world of Infrastructure at SupremeTech. What began as a fresh start during the pandemic has become an inspiring tech career journey from entry-level newcomer to the leader of our Infrastructure team. In this inspiring interview, Phuoc shares the lessons learned, the power of making mistakes, and how embracing challenges helped shape his career in tech. First Impressions That Last Hi Phuoc! What was your first impression when you joined SupremeTech?I still remember my first day at SupremeTech. What impressed me most… was the smell of a brand-new office! (laughs)It might sound funny, but that paint smell felt comforting. It reminded me of my first job after graduation, working at a new construction site—filled with excitement, hope, and anticipation. Whenever I catch that same scent, it brings back the feeling of a fresh start. From Tourism to Tech: A Career Switch Sparked by Fate We heard you used to work in the tourism industry. What made you switch to IT?Yes, I worked as an admin in the tourism sector. Shifting careers felt like fate. Honestly, it might sound silly, but I chose SupremeTech mainly because they offered a MacBook! (laughs).At the time, I was looking to change my career to IT Infrastructure and had passed interviews at two companies. But when I discovered SupremeTech would provide a MacBook, I was so excited I couldn’t say no.Back then, I felt like a blank sheet of paper. Starting in a completely new field was a huge challenge. But thanks to the support from my teammates, I slowly adapted and began to grow. Starting During COVID: Remote Work and Early Struggles Changing industries isn’t easy. What was the toughest challenge for you?I joined SupremeTech during the COVID pandemic, so the biggest challenge was starting remotely. I didn’t know anyone, and everything was done over Google Meet. Building connections, understanding the work, or communicating effectively was hard. When we finally returned to the office, I was so happy to meet my teammates, mentors, and colleagues in person. That’s when my real learning journey began.One of the most memorable challenges? Making mistakes. I’ve never been afraid of being wrong—in fact, I enjoy it. I made many mistakes initially, but each one taught me something. Most of them happened because I didn’t think far enough ahead. Over time, I learned to be more thoughtful and less overconfident. Lessons from Mistakes: Learning the Hard Way How did you manage to get through those mistakes?Mistakes are valuable lessons. Now, I even create small “traps” in internship assignments based on the mistakes I once made. It helps them encounter real problems and learn through hands-on experience. You remember things better when you figure them out yourself, rather than just reading about them. After every project, our team writes a retrospective report noting what could have been done better. One mistake equals one lifelong lesson. Facing Challenges with a Grateful Mindset You talk a lot about challenges—what does that word mean to you?To me, challenges are a kind of “fate”. They don’t just happen by chance. You have to find a way to overcome them when they show up.They might feel overwhelming at the moment, but when I look back, I feel grateful—even thankful for the people who gave me those challenges. Every company has its problems. What matters is how you deal with them and what you learn along the way. From Fresher to Team Leader: A Role Earned Through Action You’re a team leader now. How did that role come to you?Honestly, I didn’t expect to become a leader so soon. But I’ve never been the type to wait around for task assignment. At the associate level, I tried to help interns and share my experience. I focused on building strong communication and genuine connections.As a mentor, I always try to lead by example. So when I was promoted, I already felt ready. When you sincerely help others, good things naturally come your way. A Culture of Calm and Growth What’s something special about the work environment at SupremeTech?SupremeTech has a very peaceful work environment. There’s no office politics or unnecessary drama. It’s a safe and supportive place where people can grow. But that doesn’t mean the work is easy. During projects, it can feel like going into battle. Everyone has to stay sharp and take ownership to solve problems. It’s an outstanding balance—our culture is kind, but our work ethic is fierce. That reflects SupremeTech's core values: be kind in life and embrace Passion and Challenge at work. Words of Advice for Young IT Professionals What would you say to young people just starting their careers in IT?Make mistakes while you still can. Don’t be afraid to be wrong. You’ll learn more from your errors than from any books.Don’t be afraid to try. Don’t avoid difficult things, especially if you want to grow beyond your comfort zone. Looking Back: Any Regrets? Looking back at your tech career journey, do you have any regrets?Not at all. Every step I’ve taken has been worth it. Skills are essential, but the environment shapes who you become. I love investigating new problems and finding solutions. My curiosity has given me more experiences than most people at my level haven’t had, which helps me grow every day. Final thought Thank you, Phuoc, for sharing your honest and inspiring story. We wish you continued passion, positivity, and success on your tech career journey with SupremeTech!

        11/04/2025

        68

        Our culture

        +0

          From Seeking The Path to Leading The Way: Phuoc’s Journey at SupremeTech

          11/04/2025

          68

          Our success stories

          +0

            How to Upgrade Aurora MySQL Databases: Lessons Learned from SupremeTech

            Upgrading a critical database like Aurora MySQL can feel daunting. We want better performance and a smooth system, but downtime and data risks can loom large. At SupremeTech, we’ve tackled this challenge head-on and shared our proven approach.  This insight comes from Mr. Phuoc Pham, our Infrastructure Manager, who presented at the morning session of "Harnessing AI on AWS: Transforming Software Builders for the Future" event by AWS and MegazoneCloud. The event focused on giving software companies tools, strategies, and real-world solutions to innovate, boost performance, and grow globally with AI. In his talk, Mr. Phuoc revealed our 6-step process that minimizes risks, protects data, and increases efficiency. Here’s how we did it, key lessons learned, and how you can ensure a smooth and risk-free database upgrade. Mr. Phuoc Pham, our Infrastructure Manager, presented the lesson learned from Aurora MySQL upgrades SupremeTech’s contribution to the AWS and Megazone event SupremeTech partners with AWS and MegazoneCloud to share our expertise in tackling technical challenges. In the morning session, Mr. Phuoc Pham delivered a presentation on lessons learned from Aurora MySQL upgrades, offering practical tips for software companies to optimize their infrastructure. In the afternoon, our chairman, Mr. Truong Dinh Hoang, joined a panel discussion on future trends for ISVs, highlighting strategies for growth and innovation. These contributions underscored SupremeTech’s commitment to helping businesses enhance performance and scale smarter. In the afternoon panel discussion, Mr. Truong Dinh Hoang shared about the market expansion and future trends for ISVs. The Challenges of Upgrading Aurora MySQL Mr. Phuoc kicked off by sharing real-world challenges we faced with a client’s Aurora MySQL upgrades: Minimal downtime: We had to finish in under 2 hours, including rollback time if needed.System stability: Our database powers multiple services, so it had to stay reliable post-upgrade.Fast rollback: We needed a quick way to revert without losing data if something went wrong.User impact: Our process had to keep disruptions low and customer trust high. These hurdles might sound familiar if you’ve upgraded a system. The key to achieving this is a structured and well-tested upgrade process. Mr. Phuoc Pham presented the challenges of upgrades for our client’s system. The 6-Step Database Upgrade Process At SupremeTech, we follow a 6-step upgrade process to ensure a smooth transition. Step 1: Collect and Analyze Data Before the Upgrade Preparation is everything. Before making any changes, assessing your current database setup is essential. This helps identify potential risks and prepare for a smooth transition. Mr. Phuoc emphasized checking: Database Schema & Objects – Make sure there are no conflicts with the new version.Connected Applications – Identify all services using the database.Custom Database Settings – Compare parameter changes between versions.Performance Metrics – Monitor CPU, memory, query latency, and transaction speed. We gather this information using tools like database logs, security groups, and queries like SHOW FULL PROCESSLIST. This step prepares us for a smooth upgrade. Mr. Phuoc shared one of our 6-step upgrade processes. Step 2: Choose the Right Upgrade Method with C.I.D.D.E.R Framework Not all upgrade methods are the same. Depending on your system’s needs, you may choose one of the following: Snapshot Restore – Reliable but requires full backup and longer downtime.Clone Cluster – Fast rollback but requires additional storage.In-Place Upgrade – Minimal downtime but higher risk.Blue/Green Deployment – Safest rollback option but costly. At SupremeTech, we use the C.I.D.D.E.R framework to decide the best method based on: Complexity: How hard is the upgrade?Infrastructure Cost: What’s the budget hit?Downtime: How long will it take?Dependencies: What else relies on our database?Expertise: Do we have the skills?Rollback Strategy: How easy is it to undo? Choosing the right upgrade method can reduce risk and save time. For this case—a 10GB database, multiple services, and a team still building experience—we chose an in-place upgrade with a clone cluster backup for quick rollback by renaming the database cluster. It kept the endpoint intact and downtime under 2 hours. Step 3: Test with a Dry Run “There’s no place like production,” Mr. Phuoc quipped, stressing the need for practice.  A dry-run is a test upgrade performed in a staging environment to catch problems before they affect real users. We run dry runs on a cloned database and DEV/STG environments to: Detects issues before they impact production.Reduces unexpected downtime.Helps estimate the actual upgrade time. This extra step can save hours of troubleshooting later. Step 4: Fine-Tuning Based on Dry-Run Results After testing, we adjust the process: Adjust database settings.Fix errors from the dry run.Shorten execution time for less downtime.Refine rollback procedures.Update guides for our team. A few small tweaks before the upgrade can prevent major issues after it. Step 5: Deployment – The Actual Upgrade With everything tested and fine-tuned, it's time to execute the upgrade in production. How we ensure success: Perform the upgrade during low-traffic hours.Keep the rollback plan ready.Monitor logs in real time for any errors. Having a clear step-by-step deployment plan prevents last-minute surprises. Step 6: Monitor After the Upgrade Post-upgrade, we track key metrics like: Resources: CPU, memory, disk usage.Performance: Query response time, QPS, TPS.Errors: Any glitches or slow queries.Data Integrity: No data loss or corruption. Continuous monitoring after the upgrade helps us spot issues quickly, reducing troubleshooting time and minimizing the impact on our customers. We monitor key performance metrics for both the new and old databases to compare. We also watch the four golden signals—latency, traffic, errors, and saturation—to get a full picture of system health. At SupremeTech, we use AI-powered tools like Amazon Q to analyze database logs and detect anomalies faster than manual monitoring. Why post-upgrade monitoring matters: Quickly identifies hidden performance issues.Ensures the upgrade was 100% successful.Helps optimize for better database efficiency. Boosted performance and customer trust are critical criteria when we implement upgrades. Results & Lessons Learned Our Results By following this 6-step process, SupremeTech successfully upgraded Aurora MySQL with: Done in under 2 hours of downtime.Lowered infra costs with smarter planning.Boosted performance and customer trust. Key Takeaways Mr. Phuoc wrapped up with these gems: Prep is everything: Gathering and analyzing info before the upgrade is critical to spot risks early.Plan for data checks: We ensure data integrity with a solid verification plan.Pick the right approach: We choose deployment and rollback methods that fit our clients’ operations.Keep monitoring: Continuous tracking helps us stay ahead of issues.Automate with AI: Using AI and tools speeds us up and cuts errors. Wrapping Up Upgrading a database doesn’t have to be a risky, stressful process. You can confidently upgrade with the right preparation, testing, and monitoring. Thanks to Mr. Phuoc Pham’s presentation at the AWS and MegazoneCloud event, our 6-step process at SupremeTech proves you can keep risks low, protect data, and emerge stronger when doing Aurora MySQL upgrades. If your company is planning a database upgrade and needs expert guidance, contact our team at SupremeTech. We help businesses upgrade critical databases without disruption. Want to learn more about cloud database best practices? Stay tuned for more insights from our tech experts! Related articles about AWS: Mastering AWS Lambda: An Introduction to Serverless ComputingCreate Your First AWS Lambda Function (Node.js, Python, and Go)Triggers and Events: How AWS Lambda Connects with the WorldBest Practices for Building Reliable AWS Lambda Functions

            21/03/2025

            138

            Our success stories

            +0

              How to Upgrade Aurora MySQL Databases: Lessons Learned from SupremeTech

              21/03/2025

              138

              Our success stories

              +0

                SupremeTech Partners with AWS and MegazoneCloud to Drive AI-Powered Business Growth

                SupremeTech is pleased to announce our collaboration with AWS and MegazoneCloud for an upcoming event, Harnessing AI on AWS: Transforming Software Builders for the Future, scheduled for March 20, 2025, in Da Nang. This event is about giving software companies the tools, strategies, and real-world solutions they need to spark innovation, boost performance, and even take their businesses global with AI. The software world is changing fast, and Artificial Intelligence is leading the charge. Companies that tap into AI on AWS are finding new ways to grow, streamline their workflows, and stay ahead of the game. This event offers software firms in Da Nang and beyond the chance to see how AI can level up your business and prepare them for the future. SupremeTech’s Contribution to the Event In partnership with AWS and MegazoneCloud, SupremeTech will share valuable insights from our experience mastering complex technical challenges, such as Aurora MySQL upgrades. We will break it down into practical tips and solutions that software companies can use to fine-tune their infrastructure and grow smarter. The SupremeTech partners with AWS and MegazoneCloud event is structured into two key sessions: Morning Session: Accelerating Technical Performance Enhancing Product Value with AI/ML Services: Attendees will learn how AWS’s advanced tools, including Amazon SageMaker and Bedrock, can optimize infrastructure, improve performance, and reduce time to market.Real-World Solutions: Megazone will present hands-on demonstrations of AI services on AWS, offering insights into seamless integration and proven strategies derived from their own expertise. Afternoon Session: Strategic Growth Expansion Scaling with AWS Programs: Discover how AWS initiatives such as the ISV Accelerate and Workload Migration Program (WMP) can accelerate market expansion and support rapid business growth.Global Opportunities with MegazoneCloud: Explore how MegazoneCloud’s extensive partner network and the AWS ecosystem can help software companies bring their products to international markets. This event is more than a technical gathering; it represents a strategic opportunity for software businesses to advance their capabilities and adopt AI effectively on AWS. Why You Should Attend Actionable Strategies: Gain practical knowledge to integrate AI into your business operations.Expert Insights: Benefit from the expertise of SupremeTech, AWS, and MegazoneCloud leaders with proven success in the AI landscape.Networking: Connect with industry peers and potential partners within Da Nang’s growing tech community.Global Expansion: Access tools and programs to scale your business internationally. Event Details Date: March 20, 2025Location: Voco Ma Belle Danang - 168 Vo Nguyen Giap Street, Son Tra Da Nang, Vietnam Register Today to Stay Ahead in the AI Era Do not miss this opportunity to leverage AI on AWS and position your software business for success. Join the event that SupremeTech partners with AWS and MegazoneCloud on March 20, 2025, to grab the insights and tools you need to lead the charge in innovation and growth. Click Here to Register Now and take the first step toward a future of innovation and growth. Related articles about AWS: Mastering AWS Lambda: An Introduction to Serverless ComputingCreate Your First AWS Lambda Function (Node.js, Python, and Go)Triggers and Events: How AWS Lambda Connects with the WorldBest Practices for Building Reliable AWS Lambda Functions

                11/03/2025

                178

                Ngan Phan

                Our success stories

                +0

                  SupremeTech Partners with AWS and MegazoneCloud to Drive AI-Powered Business Growth

                  11/03/2025

                  178

                  Ngan Phan

                  Customize software background

                  Want to customize a software for your business?

                  Meet with us! Schedule a meeting with us!