So yes - it's even makes sense in terms of pricing On the other hand - decoupling them will allow us to track every resource group and pay only for what we are using. Coupling these 2 different apps may cause using expensive resources just to handle landing page loads. Yes, we want to gain as much flexibility as possible, but we also want to pay the lower price possible as well. These parts have no benefit to the landing page in terms of functionality and also - resource usage Apps that require login, will mostly need to use a solid gateway and some sort of identity management solution.In terms of logs - incoming traffic is different when dealing with identify users and when handling anonymous access - both in terms of cyber security as well of data analysis.so they should be deployed in an elastic high availability manner which means - when high loads occur - please use more resources to handle these loads (and please automatically decrease them when loads return to normal levels) Landing page websites loads may change drastically and without any warning.Also, in most use-cases, these websites should handle very high loads (way more than the app itself, which is login protected). This is why these websites are mostly hosted behind a waf, gateway or any other tier that help these websites to protect themselves from being hijacked. no login is required) they are at a high risk level for ddos and other malicious attacks. It mainly depends on the technological stack that your websiteĪs landing pages are opened to the general public and using anonymous access (e.g. You can select a CDN from your hosting cloud provider (such as aws, azure, gcp, etc.) or use a completely external service (such as max cdn).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |