skar5151

Great article. Looking forward to the workshop

Great use case ! The first tier compute would however need to move to the edge to ensure realtime actions. Longer term down analytics still stay on the cloud. I would really like to see containers move to the edge for localized apis which Synch offline with APIs on the cloud.

Is a Dapp the equivalent of a Microservice with its own contract ?

Is this the right math ? 1 microservice = 1 REST API endpoint = 1 container = 1 node process ?

After reviewing hundreds of applications from talented tech innovators, we’re pleased to announce the 2nd annual Node.js and Docker Innovator Program finalists. Follow along during coming year as we highlight these tech innovators, learn why they selected Node.js and Docker, and share their production best practices and user stories. One of these finalists will also be honoured with the Innovator of the Year award. Congratulations to each of this year’s finalists!

Would be very surprised if there is a CIO/CTO without a public/private/hybrid cloud adoption roadmap to show...well maybe if your main business is operating legacy data-centers. Even the later gang is wondering how to turn the decade long infrastructure investment into a cash cow. But need to be careful, cloud does not mean AWS or lockins into popular public cloud. You are right API driven architectures are the way to go in any combination cloud you build. Be it provisioning, scheduling, orchestration, scaleout...APIs are the new delivery bus.

The writing is on the wall. Traditional services just won't cut it for mobile and IoT. Who is willing to wait for 2-3 seconds for each service call to respond and be parsed per mobile event. I think this is also driven by SPA style programming where micro data segments need to be served almost at realtime vs. loading the entire service data. Microservices are the clear winner

Question is what is the migration path for enterprises from SOA to Microservices? And how much heavy lifting in terms of rewrite is needed.

I like kubernetes, but it is not well supported commercially and still has stability issues at large scale. And I absolutely hate running on AWS or even on my own VMs as it just kills the performance and server density vs running schedulers on bare metal. Are you planning on supporting other schedulers like Marathon ? Kinda BYOS - bring your own scheduler ?

Like the thought leadership. However predicting costs in Serverless environments can be a challenge. Infrastructure costs, even if elastic are more predictable. Thoughts on how to project spend or determining compute resources per function ?

Good article. Would love if you share thoughts on tracking container density during scheduling and orchestration. Containers on VMs is like going backwards in design. VM tools have made life easy with auto-scaling et all on public clouds, however the future is containers on bare metal. Gets you much higher performance and server density #vmless.

Are you ruining on Lamda? I like serverless, but hate AWS bill sucking up my cash runway. Not economical in Production...maybe at lower scale. I would prefer to deploy LB on a private cloud serverless architecture. Tips ?