altsang

5 ms·

1.
If you're doing “full stack” you're doing APIs whether or not you know it(thecodebarbarian.com)
1 points by altsang 9y ago|0 comments
2.
by altsang 9y ago
for sure, it's like the Golden Gate bridge too - once you're done on one end of painting it's time to start re-painting from the beginning again
3.
APIs: Developing in 3 Dimensions(lunchbadger.com)
9 points by altsang 9y ago|4 comments
4.
Salesforce as part of your API and APP - easy example using OSS(lunchbadger.com)
4 points by altsang 10y ago|1 comments
5.
Enterprise APIs: An Unexpected Bridge from Proprietary to Open(lunchbadger.com)
4 points by altsang 10y ago|1 comments
6.
Making Practical Ethereum Dapps – Off-Chain and Verification Pattern(lunchbadger.com)
8 points by altsang 10y ago|1 comments
7.
by altsang 10y ago
LoopBack.io powers the Compose capabilities in LunchBadger. We're built entirely on open source! Super productive for API development - we just fill in the rest of the blanks in the lifecycle
8.
Going “off-chain”, how to make your Ethereum dapp scale and successful(lunchbadger.com)
13 points by altsang 10y ago|3 comments
9.
APIs and Microservices in IoT: a small case study(lunchbadger.com)
9 points by altsang 10y ago|2 comments
10.
by altsang 10y ago
it gets better over time :)
11.
by altsang 10y ago
Not exactly in the traditional sense, a Dapps is a decentralized app that runs on Ethereum, to bridge the gap beyond blockchain execution, the embodiment of a Dapp across all of its smart contracts to a traditional application is ideally -
12.
Ethereum Dapps and microservices and APIs case study: adChain(lunchbadger.com)
10 points by altsang 10y ago|4 comments
13.
by altsang 10y ago
thx! been a fantastic and learning experience, we've found a sweet spot for blockchain backed APIs and orchestrated microservices with our offering and it's been very exciting!!!
14.
Ethereum, Dapps, APIs and Microservices Disrupting AdTech – Yup AdTech(lunchbadger.com)
9 points by altsang 10y ago|3 comments
15.
by altsang 10y ago
There are no hard rules about how to divide up your microservices and how atomic each one can be. This is an example at the lowest level as projected by Nginx. We recommend deploying microservices that are encapsulated by domain because 1.
16.
Fluffy Clouds Have API Backbones Pt.2(lunchbadger.com)
6 points by altsang 10y ago|3 comments
17.
by altsang 10y ago
We're talking to many new gen cloud companies that are already in production and have a burgeoning business that they have to support. They're all "sensitive" to cloud lock in and portability is definitely of concerns. W
18.
Fluffy Clouds Have API Backbones(lunchbadger.com)
4 points by altsang 10y ago|3 comments
19.
by altsang 10y ago
Everyone who's been in the trenches know that scorched earth big bang replatforming rarely succeeds and never gets completed. Use scripting to wrap around your existing services, carve out microservices with clean interfaces, intense d
20.
APIs versus Services – Simple Examples to Understand(lunchbadger.com)
3 points by altsang 10y ago|2 comments
21.
by altsang 10y ago
We've standardized on docker containers, so any scheduler should be able to run your APIs and microservices. For now we've used Kubernetes for deployment and managing those containers. If you have your own scheduler it would be po
22.
Kuberntes for API and Microservice Orchestration(lunchbadger.com)
6 points by altsang 10y ago|2 comments
23.
by altsang 10y ago
Thanks! We think what we've built can potentially give you the best of both worlds. No one is going pigeonhole your entire API solution into just serverless infrastructure. But a portion of it can be and should be if you want the most
24.
by altsang 10y ago
Very very true. Cost of compute is already published per cloud provider. For example, on AWS, it's currently first 1M is free. After that it's a million per $.20. At some point of volume depending on your use case there's goi
25.
Serverless – Passing the Buck? Pt.2(lunchbadger.com)
5 points by altsang 10y ago|4 comments
26.
by altsang 10y ago
That's true to a certain degree. Bare metal VMs running containers server give you OS ioslation but at a cost of an abstraction layer that is not necessarily needed if your interest is only at the container level. That's pretty mu
27.
Container orchestration for APIs and microservices(lunchbadger.com)
4 points by altsang 10y ago|2 comments
28.
by altsang 10y ago
We run on top of AWS Lambda - if you choose. Lambda is great but there's still a TON of scaffolding and boilerplate to get your APIs up and running including: model mappings, routing, point to point connection to either HTTP based prox
29.
by altsang 10y ago
if you're on a AWS, we utilize Lambda to get cost efficiency and predictable cost of execution, we also have a container based runtime that can run your APIs along with everything else that's part of the LunchBadger infrastructure
30.
Serverless APIs – Passing the Buck (part 1 of 2)(lunchbadger.com)
6 points by altsang 10y ago|4 comments

More ›