This content originally appeared on DEV Community and was authored by Wade Zimmerman
Are you are ready to deploy your first web server and need to make a decision?
No fear, this is not a tutorial. This is more of a strategic guide. Decision makers will continue reading. Apply these concepts to your project.
How Different are Tech Stacks?
Opinion. After deploying countless websites, you will see the narrow difference between tech stacks. Python, PHP, JavaScript, Elixir, Ruby, and others all write HTTP responses. This uniformity means developers can pass all HTTP handling through a standardized web server interface like Apache/NGINX.
Web servers are a MUST and highly optimized for driving web traffic. Apache/NGINX fulfill common needs such as simultaneous requests, encryption, and "path rewriting" (sales). Businesses that do not use quintessential web servers are doomed to face early scaling issues.
Should you Dodge Vendor Lock-in?
Standardization allows any executable file to act as a web application. Shoot, you could write a website entirely in bash scripts or Fortran if desired. Thinking abstractly is key, or face some form of vendor lock-in. Ask yourself, how would a competitor tackle this problem? Should I really put all my eggs in one basket?
Vendor lock-in means you pay to think the same as someone else. Deviating from vendor culture means you are wrong. Or does it? Perhaps, beforehand, it is better to innovate.
By understanding the foundation of success, production will reap financial benefits!
Why Does Server Rendering Seem Familiar?
All server rendering is similar. In the end, data is interpreted or compiled to produce static content for consumers. The consumer may be an end-user, client, or the server itself (caching). The decision is when/how to render the content.
The biggest driving factor of server rendering decisions is Search Engine Optimization (SEO). How well known are you? Can ad networks find you? You MUST thrive in reach for success.
Client applications put users first, and web servers safely execute requests. The choices come down to static content or dynamic scaling. You can even mix and match! This means, you could default to executing scripts (slow) otherwise return content from a cache (fast, money!).
What are Server Specification?
The driving value of computing power. Just like your work station, the server system specs are vital for success.
Memory, CPU, and storage are all highly important. Here are some quick tips when to prioritize a spec. Choose wisely:
-
Memory.
- Forums.
- Buying/selling.
- Caching.
- Analytics.
-
CPU.
- Tickers, scores, stocks, etc.
- User-specific content.
- Robust applications.
- Algorithms.
-
Storage.
- Content generation.
- Processing & handling.
- Large scale operations.
- Data warehousing.
Who Plans Ahead?
Smart software engineers plan ahead without over-engineering. When your website goes viral, do not cheap out on servers. Even the smartest developers, tend to panic during crunch time in a production environment. Act now!
Buy the next round, of server specifications, and you will thank yourself later. It's like insurance.
Overthinks will pay early. The industry is built on dooms day. Buying the latest "best practice" stack will shoot the money through the roof! Think twice before going with containerization, cloud functions, or other forms of redundancy. How mission critical is your infrastructure?
Believe or not, most developers like DigitalOcean and other Virtual Private Servers (VPS) providers. Scaling to millions of users is feasible. The Fortune 500 use VPS, yet shared hosting is still great for kick-starting blogs and forums.
Success comes from the quality of code. It is easier to make way in code rather than infrastructure. Every team needs a guide for the rule book because code is the way of the game!
Why Opting for Version Control is Beneficial?
Version control is a MUST for value added. Systems like Git and Subversion allow for continuous integration and resiliency. With the right setup, developers should migrate to any production environment with ease. With the right culture, rollback easy.
Leaders react to watches for events (hooks). For example, when a commit occurs, the production environment will refresh resources and send out an email. After all, work smarter not harder.
Where Does Security Need Attention?
Focus efforts on hardening your server infrastructure. With zero enemies, you will be a victim of random cyber-attacks.
Ransomware is impossible to solve and often means total loss of business records and judicial hearings. Find the right people to lock down your server as much as possible and prevent attacks to your business, or involuntary recruitment to "botnets".
DOs and DON'Ts of Web Security.
- DO use a password protect when available.
- DO use multi-factor authentication when available.
- DO encrypt when available.
- DO disable unused services.
- DO load balancing.
- DO dedicated users for web services.
- DO prevent distributed attacks, with services like CloudFlare.
- DON'T use default port numbers.
- DON'T use weak passwords.
- DON'T execute services as root, admin, or master.
- DON'T trust every tutorial you read.
- DON'T store passwords in plain text.
- DO stay updated on security best practices.
- DO security for hire
Conclusion
Think abstractly when deploying your website for success.
Remember selling insurance is easy. Dodge bullets, and you
will be aye okay because winners apply existing concepts to new ideas.
This content originally appeared on DEV Community and was authored by Wade Zimmerman
Wade Zimmerman | Sciencx (2021-12-05T21:05:51+00:00) How to Go Public With Your Website. Retrieved from https://www.scien.cx/2021/12/05/how-to-go-public-with-your-website/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.