Java is still the first choice when it comes to software development for business use . However, the development of Java software alone is not enough: machines, operating systems, JREs, application servers, etc. are required for productive use - and large frameworks and libraries are also required as the basis for code functionality. This overhead hurts more the simpler the required functionality is, because it makes development, testing, and operation more difficult. The alternative concept: Serverless.
In his session at Serverless Architecture Conference 2019 in Berlin Sheen Brisals shares his experience with Serverless and explains how he and his Shopper Engagement Technology team at LEGO migrated the legacy monolith eCommerce platform onto a cloud based solution on AWS.
What once seemed unthinkable is now common practice: databases are moving to the cloud. In this article, Ales Zeman, Sales Engineering Manager for Central Europe at Quest Software, explains what to look out for and how to make the migration successful.
Knative is a Kubernetes-based platform that comes with a set of building blocks to build, deploy and manage modern serverless workloads. Knative consists of three major areas: Build, Serving and Eventing.
In this article we want to secure an Azure Functions — serverless — implemented API with modern means by adding a JSON Web Token (JWT) validation. Experience with OAuth , JWT  and Identity Provider (IDP)  is advantageous, but not necessary.
Approaching problems with a serverless first mindset means rethinking, re-architecting, and rethinking again. Serverless isn’t just FaaS, it isn’t just about the cloud. How can you build a model for thinking serverless and practice applying it? We've asked an expert about it.
In this article, Kamesh Sampath shows us how to master the first steps on the journey towards a serverless application. He shows how to set up the right environment and takes us through its deployment.
There’s no doubt about it, testing serverless applications is a difficult job. Although the fundamental principles you’re familiar with from traditional architectures remain the same, the fact that your application exists entirely in the cloud and consists of a whole host of managed services tied together by your code, requires an entirely new testing paradigm.