COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: Archive Team: URLs

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20201201234226/https://dev.to/cdthomp1/serverless-or-server-4knp

Serverless or Server?

#discuss #serverless #server

Cameron Thompson Dec 1 ・1 min read

This post is to generate some discussion on why you prefer to use either the traditional backend (NodeJS, EfCore/ASP, PHP, etc.) or the Serverless Architecture.

Let me know you thoughts in the comments below on why you use what you use!

Discussion

arnoson • Dec 1

For simple websites (not web apps) I still prefere a PHP based CMS (like Kirby, Grav or Processwire). Nearly every webspace supports PHP and I like to self host as much as possible.

Nov	DEC	Jan
	01
2019	2020	2021

Serverless or Server?

Discussion

Read next

September 24th, 2020: What did you learn this week?

How I created a door bell with AWS Serverless

What tech-stack do you use for your portfolio?

What was your win this week?

Read next

September 24th, 2020: What did you learn this week?

How I created a door bell with AWS Serverless

What tech-stack do you use for your portfolio?

What was your win this week?

Log in to continue