Architectures for cloud solutions

Cloud applications have been the talk of the town for several years now. Especially when it comes to cost reduction and more efficient use of available resources, the cloud is hard to beat. Its true potential only becomes apparent when cloud-optimized architectures and design patterns are used. This enables stable software to be developed and complex requirements to be broken down into small, manageable solutions. But this advantage comes at a price. Questions start to arise like: "How can services communicate with each other when systems fail?" and "How do I deal with peak loads?"

Keynote: Why local development for serverless is an anti-pattern | Gareth McCumskey

It’s been a few weeks since we wrapped up another great edition of the Serverless Architecture Conference but we still remember the amazing talks! One of them was Gareth McCumskey's keynote, “Why local development for serverless is an anti-pattern”, where he argues that in the serverless community, there is no need to waste a lot of time and effort building an environment that is a replica of the cloud. 

With AWS Lambda to Multicloud

In the future, many companies will try to grow their IT infrastructure with the help of the cloud or even move it completely to the cloud. Larger enterprises often call for multicloud. In terms of serverless, there are a few ways to achieve multicloud operation. Using AWS Lambda, a function can be made available and the whole thing can be made cloud-independent with Knative.

Serverless, not Headless!

Serverless architectures are the next step in the evolution of cloud services. The first attempts at walking with them are easy. However, you should know the stumbling blocks in order to be able to avoid them. This article presents the typical challenges with corresponding possible solutions.

Serverless Java: Reduce Infrastructure Overhead

Java is still the first choice when it comes to software development for business use [1]. 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.
Stay tuned!
Learn more about Serverless
Architecture Conference 2020

Behind the Tracks

Software Architecture & Design
Software innovation & more
Architecture structure & more
Agile & Communication
Methodologies & more
Emerging Technologies
Everything about the latest technologies
DevOps & Continuous Delivery
Delivery Pipelines, Testing & more
Cloud & Modern Infrastructure
Everything about new tools and platforms
Big Data & Machine Learning
Saving, processing & more