Serverless is not just a buzzword; it’s a state of mind. Serverless and Functions as a Service (FaaS) rapidly change the way we develop, maintain, and operate software applications. Most of the current engineering techniques and well-known best practices will become obsolete in the future.
For the first time, it’s really about business logic, core domains, workflows, and events. IT is finally not about how to operate the shiniest infrastructure anymore. If you spend time with writing code for something that’s not part of your business, you are wasting time and money.
GraphQL is the perfect addition for serverless architectures! Focus on your data, instead of the HTTP interface to access it. Read more about GraphQL Consulting …
With serverless architectures, you only pay for what you use, not for what you hope might need somewhere in the future. You do not need to worry about traffic; if you pay more for your architecture, you have more users on your service. It’s that simple, and it should have always been that simple. The only disaster is a success disaster. Having a large invoice for a serverless architecture means your service has a broad audience.
It’s not simple to migrate existing applications to a serverless architecture and mindset. You will spend more time on getting used to the way of thinking, than with writing code for your new serverless environment. However, less source code means less maintenance and operational tasks. Both are not part of your business anyway.
You want to focus on your business and core domain as much as possible. Focus on what you can control, not on the things that only affect you. Optimize what matters and do not run somebody’s core domain as a side project. If you do, you will end up with problems or incidents in a field you are no expert in …
