神刀安全网

Serverless meets Microservices

Serverless meets Microservices
Serverless + Microservices = ♥

S erverless computing has been a hot buzzword for quite a while now. And it’s not hard to see why. There is an increasing demand for cloud app development and relatively little DevOps workforce to support it. According to the Stack Overflow survey there is 1 DevOps for every 30 developers. Other data suggests even worse stats: 1 in 70. Although this might be skewed, we believe this highlights both a skill gap and a trend for adhoc operations — DevOps work carried out by the developers themselves.

The serverless concept solves this problem, because it requires no DevOps to build and deploy applications at scale. But so far, this kind of technology has only been available exclusively from cloud vendors, like AWS, Azure and Google Cloud Platform, forcing users into proprietary technology and having no freedom to run it in private clouds or locally, for development.

… until now.

Introducing Lever OS

Today, we’re super excited to announce Lever OS version 0.1 ! Lever OS is the open-source serverless platform that allows dev teams to build and deploy microservice-oriented backends with zero DevOps involvement. It abstracts away complicated infrastructure and leaves developers with very simple, but powerful building blocks that handle scale transparently.

With Lever OS, you don’t think about servers. You think about services. Lever takes care of distributing your code on multiple nodes and bringing up as many instances as necessary, depending on real-time demand. It routes and load-balances traffic transparently so you don’t need to configure complicated reverse proxies or service discovery. It’s all built-in.

Serverless meets Microservices
A backend made out of multiple Lever services

You can combine multiple Lever services to form complex backends. Give each service to different teams and you have a clean way of delimiting responsibility. Everything interconnects seamlessly through the built-in RPC system.

Each service is made out of a few exported functions that you develop and then deploy onto Lever. In JavaScript, for example, you export the functions as part of a .js file and then point Lever to that file. The functions become the API of your service and you can trigger them using HTTP.

Serverless meets Microservices
Crazy fast dev-test cycles

And, because Lever OS is open-source, you can try all this on your own laptop, without having to deploy to the cloud each time you make changes. This allows for really really fast dev-test cycles. What’s more, this also helps maintain consistency between dev and prod environments, which reduces the works-for-me type of bugs.

A simple example with code

Suppose you want to create a backend that responds to requests with “Hello, <name>!”. To build this, you will need the JS function that returns the string, and a simple config file, lever.json, that describes the service to Lever:

To deploy it you can run

$ lever deploy

That’s it! You can then invoke the service in various ways, as shown in this screen cast

When you are ready to dive deeper, head over to our GitHub page , give us a star and start hacking!

This is the first release of Lever OS. We will continue to iterate, make improvements and, most importantly, incorporate user feedback. We can’t wait to see what you build with it!

Note that Lever OS is in beta . If you have any problems, please open a GitHub issue .

See also

转载本站任何文章请注明:转载至神刀安全网,谢谢神刀安全网 » Serverless meets Microservices

分享到:更多 ()

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址