{"id":55881,"date":"2020-01-31T00:00:00","date_gmt":"2020-01-30T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/sovety-i-istochniki-informatsii-dlya-sozdaniya-besservernyh-prilozhenij"},"modified":"2020-02-18T14:04:02","modified_gmt":"2020-02-18T11:04:02","slug":"sovety-i-istochniki-informatsii-dlya-sozdaniya-besservernyh-prilozhenij","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/sovety-i-istochniki-informatsii-dlya-sozdaniya-besservernyh-prilozhenij","title":{"rendered":"Tips and information sources for building serverless applications","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Tips
\nAlthough serverless technologies have rapidly gained popularity in recent years, there are still many misconceptions and concerns associated with them. Vendor lock-in, tooling, cost management, cold start, monitoring, and development lifecycle\u2014these topics are actively discussed when it comes to serverless technologies. In this article, we will explore some of the mentioned topics and share tips and links to useful resources to help newcomers create powerful, flexible, and cost-effective serverless applications.
\n<\/a><\/noindex><\/p>\n

Misconceptions about Serverless Technologies<\/h2>\n

\nMany people believe that serverless and Function as a Service (Functions as a Service<\/a><\/noindex>, FaaS) are almost the same. This suggests that the difference is not that significant, and it is worth adopting the innovation. While AWS Lambda was one of the 'stars' of the serverless technology boom and one of the most popular elements of serverless architecture, this architecture is more than just FaaS.<\/p>\n

The main principle of serverless technologies is that you do not need to worry about managing and scaling infrastructure; you pay only for what you use. Many services fit these criteria\u2014AWS DynamoDB, S3, SNS or SQS, Graphcool, Auth0, Now, Netlify, Firebase, and many others. Overall, serverless means leveraging all the capabilities of cloud computing without the need to manage and optimize infrastructure for scaling. It also means that infrastructure-level security is no longer your concern, which is a huge advantage considering the difficulty and complexity of meeting security standards. Finally, you do not need to purchase the infrastructure provided for your use.<\/p>\n

Serverless can be seen as a 'state of mind': a certain mentality when designing solutions. Avoid approaches that require managing any infrastructure. With a serverless approach, we spend our time solving problems that directly impact the project and provide benefits for our users: creating resilient business logic, developing user interfaces, and designing adaptive and reliable APIs.<\/p>\n

For example, if we can avoid managing and supporting a full-text search platform, that is exactly what we will do. This approach to application assembly can significantly speed up time to market, as you no longer need to worry about managing a complex infrastructure. Eliminate the responsibilities and costs associated with infrastructure management and focus on creating the applications and services your customers need. Patrick Debois referred to this approach 'servicefull'<\/a><\/noindex>, a term adopted in the serverless community. Functions should be seen as a connective link for services in the form of deployable modules (instead of deploying an entire library or web application). This provides incredible granularity in managing deployments and changes in the application. If you cannot deploy functions in this way, it may indicate that the functions are handling too many tasks and need to be refactored.<\/p>\n

Some are concerned about vendor lock-in when developing cloud applications. The same goes for serverless technologies, and this is unlikely to be a misconception. From our experience, creating serverless applications on AWS combined with AWS Lambda's ability to integrate other AWS services partially forms the merits of serverless architectures. This is a good example of synergy, where the result of the combination is greater than just the sum of its parts. In trying to avoid vendor lock-in, you might encounter even greater problems. When dealing with containers, it is easier to manage your own level of abstraction between cloud providers. However, when it comes to serverless solutions, the efforts may not pay off, especially when considering cost-effectiveness from the very beginning. Be sure to find out how vendors ensure service delivery. Some specialized services rely on integration points with other vendors and may provide plug-and-play connectivity out of the box. It is easier to invoke Lambda from an API Gateway endpoint than to proxy a request to some container or EC2 instance. Graphcool offers simple configuration with Auth0, which is easier than using third-party authentication tools.<\/p>\n

Choosing the right vendor for your serverless application is an architectural decision. When building an application, you do not expect to return to server management one day. Choosing a cloud vendor is no different from choosing to use containers, databases, or even programming languages. <\/p>\n

Consider the following:<\/p>\n