Serverless – what it means for your company.
In a recent a post on serverless applications I explained what it is from a technical point of view.
Technicality a side I wanted to give you an idea about what it means to you to go ahead with a serverless application and how you benefit from it.
Typically you need to serve both web and mobile users and more commonly have mobile apps to provide meaningful service to your customers. So the server, typically needs to support the administrative and client side of the web application and the client mobile applications.
Having to go with a serverless architecture changes the way your business logic is implemented. Your server is now a collection of independant tasks which run in parallel and may request eachother as and how needed.
We have the ability to simplify and reduce any complex architecture in to series of processing streams delegated to handle cases either specific or more generic depending on the logic.
There is no one size fits all for a solutions architecture. I’d be long out of a job if it were so.
Another neat trick we can do in a serverless architecture is to trigger task execution streams independent of server’s usual workload. The server can do as much heavy lifting as you need it to, but still serve you seemlessly.
At Tivoga, we developed a good number of serverless applications and I can whole hartedly recommend it, if you are contemplating that as a choice.
The architecture and the development fits very well with agile methadology and being a micro service architecture, it is best suited be used in applicaitons requiring fault tolerance, high availability, and scalability.
As I discussed in the previous post, The monetary benifits are pretty straightforward – The agile methadology for web and mobile app development means you have a project that’s sticking to schedule and cost. More to it, the server development is considerably faster and cheaper than a monolith.
These are some non ignorable points to any company startup or enterprise.
My experince with AWS and lamdba functions shows me that lambda offers just so much out of the box. Logging, maintainance, deployment scaffolding, Access permissions to name a few.
We use lambda pretty fluently and given the nature of interconnectivity need to frutfully implement a company’s stringent requirements, we fully exploit lamdba’s quick access to services and controlable fine grained security permissions.
Serverless architecture is even being used to develop PCI DSS complient solutions. I.e it provides a stable platform to build security in to the application at the code level, taking security above and beyond what can be provided just by permissions and ACL.