Tag : Serverless (3)
With the serverless approach, the problem about the server that the software developer confronts with has disappeared. Now we write our code and call the provider to run it. We are not dealing with server configurations, scalings etc. And pay as you go. This is a great opportunity.
AWS's Lambda, GCP's Cloud Function, Azure's Azure Function etc., these services provide us this service. But this time, different kind of problem appears. These services do not support all languages. Even if it supports the language we want, it may not support the version we want. For example, AWS Lambda does not support the upper versions of .NET Core 2.1 yet. This is a problem. Nobody can restrict us :)
The Cloud Run service that Google built on Knative completely solves this problem. We give Cloud Run a docker image and Cloud Run runs our serverless service from this image. So whether we develop in PHP or .NET Core, it doesn't matter. There is no limit as long as we can make dockerize. This is awesome.Read more
This article will be about how to develop the messaging system with the serverless approach. We will use AWS as a cloud provider. We will prefer .NET Core as the language.
In this part, I will set up the scenario and give preliminary information about what will be the result.
Our RESTful API endpoints will be as follows.
We will use the AWS services below.Read more
This article series is about how to develop RestfulAPI with a serverless approach. We will use AWS as a cloud provider.
In this part, i will show the scenario and give information about what will be the result.
Our RESTful API endpoints will be like below.
- ASP.NET Core
- Actor Model
- Continous Integration
- E2E Tests
- Event Sourcing
- Event Store
- Integration Tests
- Microsoft Orleans
- Smart Contract
- Unit Tests