这个问题的目的是测试应试者对RESTful API标准的了解程度. 构建端点时的一个常见错误是在路径中使用描述性动词. For example:

• GET /users/search
• GET /posts/create

Instead, 真正的RESTful路径应该只包含名词——端点上使用的方法应该决定操作. For example:

• POST /users (create a user model)
• PUT /users/{id|slug} (replace a user model)
• PATCH /users/{id|slug} (update part of a user model)
• DELETE /users/{id|slug} (delete a user model)
• GET /users/{id|slug} (retrieve a user model)

确定资源是否存在是api中经常需要的操作, 但很少按照RESTful和行业标准正确地完成. The commonly accepted way to determine if a resource exists, using the above “user” resource as an example, is like so:

• HEAD /users/{id|slug}

此请求将使用最少的带宽，因为它将不返回任何数据，仅返回一个 200 (resource exists) or 404 (resource does not exist) HTTP status.

The key issue with the proposed table design are the object_id_X and object_type_X fields. 当数据可以像这样存储在相关表中时，增加命名字段被认为是糟糕的设计:

Notifications Table

CREATE TABLE `notifications` (
	`id` INT NOT NULL AUTO_INCREMENT,
	`type` INT(8) NOT NULL,
	`notifiable_id` INT unsigned NOT NULL,
	`notifiable_type` VARCHAR(10) NOT NULL,
	`updated_at` TIMESTAMP NOT NULL,
	`created_at` TIMESTAMP NOT NULL,
	PRIMARY KEY (`id`)
);

Notification Relations Table

CREATE TABLE `notification_relations` (
	`notification_id` INT unsigned NOT NULL,
	`relation_id` INT unsigned NOT NULL,
	`relation_type` VARCHAR(10) NOT NULL,
	PRIMARY KEY (`notification_id`)
);

The most effective way to solve this problem is to use queues.

当向我们的API发出请求时，将创建一个单独的作业并将其添加到队列中. 然后，该作业将在请求的端点上独立执行, thus allowing the server to respond without delay.

There are many queue providers but the most notable are:

• Amazon SQS
• Redis
• Beanstalkd

尽管这个问题的答案存在争议，但广泛接受的做法是使用 409 Conflict HTTP status code.

It would also be acceptable to return a 422 Unprocessable Entity.

Some may argue that a 400 Bad Request is acceptable, but we discourage this, 因为它通常意味着服务器不理解请求, which in this case is not true.

If the data within the API is publicly accessible then, technically, it is not possible to completely prevent data scraping. However, 有一个有效的解决方案可以阻止大多数人/机器人:速率限制(也称为节流)。.

节流将阻止某个设备在规定时间内发出规定数量的请求. Upon exceeding the defined number of requests, a 429 Too Many Attempts HTTP error should be thrown.

注意:使用不止一个IP地址来跟踪设备是很重要的，因为这不是设备唯一的，并且可能导致整个网络失去对API的访问.

Other less-than-ideal answers include:

• 基于用户代理字符串阻止请求(很容易绕过)
• 在前端为访问者生成临时“会话”访问令牌. 这并不安全:在前端存储秘密可能会被逆向工程, thus allowing anyone to generate access tokens.

首先，也是最重要的，答案应该包括一个，而且只有一个查询. 达到预期结果的方法有很多，但正确的方法是:

SELECT
   posts.*,
   COUNT(post_likes.user_id) AS likes 
FROM
   posts 
   LEFT JOIN
      post_likes 
      ON posts.id = post_likes.post_id
WHERE posts.user_id = 'XXX'
GROUP BY posts.id

The key attributes here are srcset and sizes. 这些属性允许开发人员为一个图像指定多个图像大小 , for example:

By using srcset and sizes, 然后，浏览器将根据访问者视口的大小智能地选择要使用的正确图像源.

任何基于视口大小使用JavaScript更改图像源的建议都应该被视为危险信号. 这表明开发人员没有跟上最新的CSS特性支持和/或最佳实践.

There are technically various ways to achieve this. However, nowadays, there is one “correct” way to do this: using display: flex and margin: auto.

Other methods include position: absolute;, top: 50%, and margin-top: -Xpx，但是自从引入了 display: flex.

为了建立一个网站优化的有机搜索引擎排名, it is important to implement certain standards throughout the code. These include:

• Specifying an alt tag on images
• Using the correct HTML tags for content hierarchy i.e.,

  /

  /

  and p

• Connect the site to the company’s social pages
• Add an XML sitemap
• Avoid broken links
• Use vanity/friendly URLs (human readable)
• Add a robots.txt file
• Integrate Google analytics (or alternative)
• Specify a favicon, bonus for specifying browser specific icons
• Ensure lightning fast page load time
• Avoid JavaScript errors
• Optimize assets (including minification)
• Enable and force SSL
• Specify unique titles for each page without exceeding 70 characters
• Include a meta description on each page
• 确保有足够的内容和足够的相关关键词(如果所有页面都是一句话页面，搜索引擎会惩罚你的网站)
• Leverage browser caching
• Avoid W3C markup validation errors
• Specify relevant meta tags

Optimizing websites is an art that few are familiar with. The more the engineer is able to list off the top of their head, 他们就越有可能在编写代码时自然地执行以下所有操作，而不必稍后返回.

(此外，通常一个专业构建的网站在分析时应该得分超过75% gtmetrix.com, which can also serve as a checklist.)

• Optimize all assets
• Place all assets on a separate, cookie-free domain. Using a CDN is best
• Avoid inline JavaScript and CSS
• Enable gzipping
• Ensure all code is minified
• Defer parsing of JavaScript
• Use srcset for responsive images
• Leverage browser caching
• Reduce DNS lookups
• Avoid duplicate code
• Avoid URL redirects
• Enable HTTP keep-alive
• Serve scaled images
• Use image sprites where appropriate
• Prefer asynchronous resources
• Specify the character set at server level
• Avoid CSS @import
• Specify a cache validator
• Minimize request size
• Avoid bad requests and 404s
• Specify image dimensions
• Reduce cookie size
• Make fewer HTTP requests, i.e., load as few external resources as possible
• Avoid unnecessary images; where possible, use CSS
• Ensure no validation errors with W3C