Welcome to BeerMoneyForum.com - BIGGEST MAKE MONEY FORUM ONLINE

[happietappy]

With serverless application getting very popular recently, just wanted to know what you guys think.

Regular Hosting: Your traditional PHP, Apache, NODEJS hosting package.
Serverless Architecture:You only host your HTML files and then make calls to specific cloud services for resources/computation (naive explanation). E.g Google Firebase, Azure Lambda etc.

Personally i think serverless application are really great if you are building a custom web app with high traffic in mind cause in that case you don't have to worry about migrating or purchasing more servers when traffic get high cause you pay for the amount of resource use/calls you make.

Will like to know what you guys think and how can a web app running on serverless architecture be protected from regular web attacks lile DDOS.

 

[naomi1999]

With regular hosting, you rent space on a physical server that is shared with other users. This is the more affordable option, but it can be less reliable and less secure. With serverless architecture, there is no physical server instead, your website is hosted on a virtual server that is spun up on demand. This is typically more expensive, but it's also more reliable and secure.

 

[BaleegNajar]

Serverless architecture offers scalability and cost-efficiency, ideal for high-traffic web apps. It eliminates constant server management, adapting resources dynamically. Despite the inherent security of cloud providers, serverless applications still face risks. To guard against DDoS attacks, services like AWS Shield or Azure DDoS Protection are vital. Implementing rate limiting and securing APIs enhance protection. The choice between traditional hosting and serverless depends on your project's complexity and anticipated traffic patterns. Each architecture has merits, requiring consideration of your application's goals and requirements.

 

[Obedientasteful]

Please, be more specific... I mean requirements: disk space, bandwidth, server location, budget?

 

[kayode10]

Regular hosting involves managing and maintaining servers to run applications, requiring upfront infrastructure setup and continuous monitoring. Serverless architecture abstracts server management, allowing developers to focus solely on code. With serverless, you pay only for the resources consumed during execution, scaling automatically based on demand. It offers greater flexibility, scalability, and cost-effectiveness, but may introduce limitations in certain use cases.

 

[Golemos]

A level of technical support should also be taken into consideration. It happens that many web site hosting services providers don't actually provide the 24/7 support they are boasting they have. There are different kinds of the support, but the most widespread is a 24/7 online support. It's better to choose those web hosting companies that provide online technical support. It's more convenient. Of course one of the key factors is how quickly they respond to your request.