Skip to main content

Kalix-NoOps High-performance Microservices and APIs

 What Kalix Platform-as-a-Service promises is massive - a way to write cloud applications based on Kubernetes under a unified API abstracting the lower layers away.

We know that Kubernetes is magic, but at the same time hard - hard to setup, hard to configure, hard to operate, hard to write applications on, and this difficulty is a reason of why many are reluctant to let go of their monolith for the microservices world:

“Complexity in the cloud ecosystem is slowing down engineering and development teams,” said Jonas Bonér, Lightbend’s founder and CEO. “Kubernetes does an excellent job managing, orchestrating, and ensuring availability and scalability of containers, but that’s only half the story.

”There needs to be an equal investment in the application layer to make it easier for the developer to build complete applications that take full advantage of all the excellent underlying cloud infrastructure we have at our disposal. Kalix is the solution to this critical issue.”

Under the current state of cloud infrastructure application developers are also burdened with managing.....

full article on i-programmer:

https://www.i-programmer.info/news/80-java/15434-kalix-noops-high-performance-microservices-and-apis.html

Labels:

Comments

Post a Comment

Popular posts from this blog

Making GraalVM Based Executables Easy with Liberica Native Image Kit

  Liberica Native Image Kit is a utility for making native images for the JVM, letting you compile applications to executables using the GraalVM native-image compiler. As a refresher on what a native image is Native image is the executable binary file that contains your application, all its dependencies, and runtime components, allowing you to run your JVM based program on any supported configuration without the need for installing runtime or any setup. Native image is the easiest way to distribute your program and start it up faster. Native images have several advantages over JVM interpreted applications:  Almost instant startup time Optimized resource consumption and smaller static footprint Does not require JVM for execution  But why go for GraalVM over packaging your app with say Launch4J or javapackager?  full article on i-programmer: https://www.i-programmer.info/news/80-java/15284-making-graalvm-based-executables-easy.html
Post a Comment
Read more

pg_ivm - Materialised Views On Steroids

 pg_ivm is an extension module for PostgreSQL 14 that provides an Incremental View Maintenance (IVM) feature.That means that materialized views are updated immediately after a base table is modified. pg_ivm gives answer to the age old problem of when to refresh the materialized view. As a refresher or reminder, a materialized view versus a normal view is that the former keeps a copy of the data referenced to speed up querying since you actually query that copy, while the latter performs a live query every time. That might be great, but not ideal as you have to decide when to refresh that copy in order to avoid querying stale data.Until now in Postgres this could be done when running the command REFRESH MATERIALIZED VIEW. But again, when is the right time to run it, given the performance aspect of the time it takes for the operation to complete? full article on i-programmer: https://www.i-programmer.info/news/84-database/15470-pgivm-postgres-materialised-views-on-steroids.html
Post a Comment
Read more

Azul's Cloud Native Compiler - Why Share The JIT Compiler?

  Azul's Cloud Native Compiler is targeted at organizations with multiple dev teams who share a common environment. Instead of compiling on their local machines, the process is offloaded to a cloud that shares a JIT compiler. Why is that beneficial? As we all know, when compiling code on the JVM there's a JIT compiler that turns the bytecode into machine code. Typically this happens locally at each dev's PC. What Azul offers is to offload this JIT compilation to a cloud-native Kubernetes-based compiler; this has distinct advantages over lone local compilation. Firstly the local resources are not stressed as much because they now engage less CPU and RAM resources. Another advantage is that as a lot of libraries and code is common amongst local dev machines, sharing their compilation in a common repository allows for caching, better dynamic resource optimization, faster compilation and less memory requirements. full article on i-programmer: https://www.i-programmer.info/news/
Post a Comment
Read more