POSTS CATEGORIZED UNDER

fugue

March 6th, 2017

12 minute read

Fugue uses Python extensively throughout the Conductor and in our support tools, due to its ease-of-use, extensive package library, and powerful language tools. One thing we've learned from building complex software for the cloud is that a language is only as good as its debugging and profiling tools. Logic errors, CPU spikes, and memory leaks.
January 10th, 2017

5 minute read

 

“It worked on my laptop!”

 

Seven weeks into your latest project, you’ve gotten to the point where management wants a demo. Your first spike was run from a node server that you ran on your laptop. When another developer joined, you moved the environment to Vagrant so you could share an image. When the third and fourth bodies were assigned,.

November 22nd, 2016

2 minute read

Harry Weller, General Partner leading NEA’s east coast venture practice, passed away unexpectedly on November 19, 2016. Please see NEA’s words for Harry.

 

J. R. R. Tolkien, one of Harry’s favorites, said, “A safe fairyland is untrue to all worlds.” Harry never counted on life or decisions or business being safe. He looked into this world and.

October 10th, 2016

10 minute read

 

The approach taken by Fugue is to allow cloud infrastructure to be treated as code. This concept is required if developers are to generate applications that can exploit the cloud's capabilities and deliver on the promise of immutable infrastructure.

 

Fugue provides simplification of your life on the cloud.

August 8th, 2016

7 minute read

As we migrate applications to the cloud or build there natively, cloud computing itself is changing how we compose and operate our systems. We increasingly compose systems of elastic collections of services running on many compute instances. We now commonly employ application statelessness in order to exploit cloud system elasticity and to.
November 11th, 2014

9 minute read

We at Luminal are launching our new vision for computing: Fugue. Fugue embodies a set of core computing patterns that rely upon:
 
  • Automating the creation and operations of cloud infrastructure through a no-touch runtime environment. This uses an active infrastructure OS under users’ control and within their environment.
  • Short-lived compute.
September 15th, 2014

3 minute read

In two previous posts, I explored the concepts of "Minimum Viable Clouds" and "More than Minimum Clouds."

 

To recap, a Minimum Viable Cloud must:

 

  • be an SOA
  • hide implementation
  • be fully automated
  • be a utility
  • have global fault tolerance
  • be Opex

 

A cloud that is More than the Minimum must:

 

  • promote stateless, distributed compute
August 27th, 2014

3 minute read

The M in MVC (Minimum Viable Cloud) implies that there are additional capabilities in a mature cloud implementation beyond those outlined in our previous post, which introduced MVC . Recall those sine qua non MVC requirements:
 
  • Clouds are APIs
  • Clouds are SOAs
  • Clouds Hide Implementation
  • Clouds are Fully Automated
  • Clouds are Utilities
  • .
August 10th, 2014

5 minute read

Every time a new, hot technology appears on the scene, many companies with old, boring technologies slap a sticker on the front of their product, proclaiming it to be a torchbearer for the new tech. It's something of a parlor trick. Certainly this has been the case with cloud technologies. As a result, there's a need to differentiate things that.

Jump to Page

1 2 3

Secure Your Cloud

Find security and compliance violations in your cloud infrastructure and ensure they never happen again.