What is a Modern Fullstack Platform to you?
Hey Everyone -
I'm trying to build a modern fullstack platform at www.kintohub.com. But I'd like to connect with this community to understand what are the NEEDS and wants of such an idea?
So far we are finding people like being able to "do everything in one place" Databases, Backend APIS, websites without going to 3rd parties, or using complex cloud platforms.
Additionally, we are finding that although Firebase and AWS Amplify are great stacks to build against, some people want to use their own fullstack tooling of their choosing and not code against a framework/API.
And finally - Regarding serverless, we are finding Lamda is totally great and growing a lot of adoption. But again, its a learning curve to get the cost savings... But when it's done, it's absolutely awesome. I'm thinking of introducing a "sleep mode" button to auto sleep services and wake them like lambda, but no need to change your existing code to get the benefits of this cost savings.
With that said - I hope it gives you some context of the crazy world of fullstack. Curious what you guys love and what you'd want to see improved in the space?
This is such a large topic that I feel your explaining KintoHub's ideas would be the faster route.
Good question - I was hoping for just general ideas, and I keep hearing documentation is soooo critical as well, we have a lot more work to do on ours.
React /w promises goes into Framework land. If I were to say Kinto's ideas, we're definitely not wanting to be a framework nor contributing to the way you code.
We want to be the glue between your services and provide tools to make it easier to allow services to work together. For example, maybe you want to process the leaderboard of top 100 for some competition based on yesterday's results. You can use A job on kintohub and task it to run once every 24 hours, query data, and then output the results on a table.
KintoHub's ideas would be:
Still way too high level I'm afraid. Here's an article Uclusion wrote about glue logic we had to write to handle multi-repo deployment. How would KintoHub help us or are we forced to use a mono-repo?
Thanks again for replying ;) Most people give up at this point.
I'm starting to sense that a lot of people like "show by example" How to do X on KintoHub. What activities can be achieved on KintoHub, etc. Do you think if I pumped out 20-30 of these in the next 30 days that would be more helpful?
--
Regarding your question, we support both mono-repo and multi-repo.
Everything in KintoHub is focused around combining "services" into an "environment". This environment is where an entire "version" of your app lives which includes your MongoDB Database, Redis Cache, A few Backend API microservices, and your frontend Web App.
For a mono-repo structure by putting multiple projects in a single repository with subfolders, you can:
You can repeat these steps above on the same repo to use subfolders as a mono repo.
Preferably, I like working in multi-repo. So in this case you would just do step (1) when you add a service on KintoHub and it would be unique since its one repo per service.
To see a full workflow, you can take a peek at https://docs.kintohub.com/getting-started/fullstack-example
Yes I think examples are the way to go - that's how we got started on CircleCI (though I'm not crazy about them). Definitely better than page not found - https://docs.kintohub.com/getting-started/fullstack-example/examples/nodejs/nodejs-example
True 😅
I really enjoy working with Django. There are a lot of really good cookie cutter templates to get you running and in production quickly. You an auto set up an smtp server, asynchronous tasks, redis, and postgres . You can create an API and use an FE framework, or use a cookie cutter to utilize Vue with a multi page app paradigm.
Personally, I use digital ocean. I like the simple pricing and ease of use. I used to use AWS for everything since I'm an AWS Certified Developer but even for me, with a few years of AWS experience and a certification, I always end up with random weird unexpected charges.
Thanks for sharing!
When you say you can auto setup X,Y,Z, do you mean, its easy to setup and configure/connect? I took a look and it seems Django makes it easily to perform tasks such as emails, queues, etc like you're mentioning, but I couldn't find anyhting about auto setup.
This inspired me to write an example on Django + KintoHub and connecting it to Redis/S3 Storage (images/content)/Postgres/etc. But before I do, please advise me if there is some auto setup somewhere :)
I believe this is the future. I really like gcp cloud run / aws fargate where one can run docker in serverless mode. Is that something similar you are thinking about ?
Really happy to come across kintohub, I believe we can work together. At XgeneCloud we instantly generate REST/GraphQL APIs over any database. In a way, we are open source alternative to Firebase and likes.
How do I get in touch with you ?
Cool, I'm a big fan of hasura and parse and would love to learn more on your stuff. Always looking to show off new tools on KintoHub!
Reach out to us on the support channel and I'll make sure it gets directed to my personal email: https://www.kintohub.com/contact-us/
This comment was deleted 3 years ago
Google cloud is great, KintoHub is built on top of cloud providers and started off on Google Cloud.
But it takes a large team of people who have to focus on cloud related activities to ship a product. KintoHub handles this for you (build, deploy, scale, optimize costs, link services together, promote safely to production, rollback, etc) so that you can just build an app versus build tools to build an app.