Netlify for the frontend, Micro for the backend

Post by turtlebits » Thu, Nov 12, 2020, 5:28 PM UTC

asim wrote: post #22

jfengel wrote: post #20

Your page doesn't show any of the backend code being deployed. I don't even know what language it's in. So it's a little hard for me to compare it to Netlify, which does have backend support in the form of lambdas, and a database in the form of FaunaDB. That's fairly limited, but it's also very easy. Clicking through to the github page, it looks like the examples are in Go... though I also see a Dockerfile. For me, I…

Thanks for the feedback. I'm assuming you mean the website. We have info and tutorial in docs but agree we could provide more clarity on the website. There is a redesign coming in the next few weeks. There are tutorials in the docs and many code examples in https://github.com/micro/services . The blog post also links to this code. But again I agree we could do more to showcase it. This post was more to demonstrate po…

Post by cxr » Thu, Nov 12, 2020, 5:31 PM UTC

friendly_chap wrote: post #23

cxr wrote: post #21

Earlier quoted context omitted.

> One concern is your pricing seems too reasonable (free)! Is that reasonable? Building anything on top of obvious loss leaders is risky. And the costs here for a year of service are either $0 on the free plan or $420 for the cheapest paid plan. There's a chasm of difference there. I can't understand people offering platforms and services with a pitch that tries to describe what sets $THING apart from others, but whe…

> Is that reasonable? Building anything on top of obvious loss leaders is risky. And the costs here for a year of service are either $0 on the free plan or $420 for the cheapest paid plan. There's a chasm of difference there. The dev tier is free, which is a capped environment with much laxer SLAs than the production tear. Prod tier is paid.

Post by pwdisswordfish4 » Thu, Nov 12, 2020, 5:51 PM UTC

wetpaws wrote: post #40

Yow dawg, you fleed to netlify to avoid insane over-engineered technology stacks, so we brought you insane over-engineered technology stack with protobuffs and gRPC

Post by DJHenk » Thu, Nov 12, 2020, 6:16 PM UTC

mindfulmark wrote: post #15

hans0l074 wrote: post #2

When I read about such abstractions and "simplifications" (which usually end up with a 10 box diagram simplified to a 2-3 box diagram), I often hesitate to start building something new, always wondering "Am I doing this in the most " upvoted" way of implementing such a thing? Some of this tech feels like if you switch on, and stare at your monitor long enough, a "Hello World" API will be deployed on the cloud for you…

I think it's a good point and something I find myself worrying about as well. The hype around GraphQL and Apollo, for example, made me feel that I was losing serious time developing a REST APIs until I finally committed and decided to use it on a project. Obviously there ended up being a lot of trade-offs but in the end it was hard to tell if I saved any time at all. More generally, after falling for this a couple ti…

Post by marcosdumay » Thu, Nov 12, 2020, 6:54 PM UTC

DJHenk wrote: post #47

mindfulmark wrote: post #15

Earlier quoted context omitted.

I think it's a good point and something I find myself worrying about as well. The hype around GraphQL and Apollo, for example, made me feel that I was losing serious time developing a REST APIs until I finally committed and decided to use it on a project. Obviously there ended up being a lot of trade-offs but in the end it was hard to tell if I saved any time at all. More generally, after falling for this a couple ti…

I like to call this the: Law of Conservation of Complexity. It does not matter how slice and dice things, the real world is a complex environment and as a result your application will be complex in some way too. You just can't sweep complexity under the carpet and pretend it's not there. It will always come back and bite you, in some way or the other.