KintoHub

@hnshah thanks for the support. Being a team of developers, we're excited to share what we've built and looking forward to the developer community driving the next generation of a feature economy around microservices.

@tommytcchan Thanks for Q's Tommy! Looking forward to supporting your project on KintoHub. 0) SLA -- We're in Alpha and will have proposed SLAs once we get to Beta. We're expecting beta in Q4 this year. We're planning to prio multi-cloud deployment to ensure the best SLAs, especially for crypto related projects 1) Monitoring - Yes, monitoring is on the way. We paused this feature because there are too many ways to do this. We're having an open Q&A / AMA later this month to open up the question to the community. Would love for you to participate - if you signed up, you'll receive an email next week about it. 2) Pricing - We're free today and will always have a free tier. We are planning to have a mix of a tier based system starting at ~10 USD up to a "pay as you go" model. The pay as you go will be a pay-per-second model thanks to serverless. To increase resources/instance size, we look at these as "Addons" which would be a monthly fee. You can also add-on databases or analytics in the near future as well. We'll be sharing more August 2018 and hope to have an open discussion with the community about this. 3) Yes - Contact us via slack or email and we can discuss this. We're tested on AWS/Google/Azure so far and can do private managed or unmanaged solutions. Today, all services you create on KintoHub are private to the members of a workspace by default if you want to start now on https://www.kintohub.com

@bhatnagar_san Great question and example context! Quick answer, KintoHub will should you a ton of dev time and money from day 0 to IPO of your company. To keep things simple, I'm only going to share some of Twitter's features that can be broken down into microservices: - Authentication/Login - Emailing - Profile / Account / Settings - Notifications - Private Messaging - Feed/Posts ***UNIQUE*** The only microservice you would need to code is the Feed/Posts. You may agree that the rest of the services exist in 100's of thousands of apps / websites today. The Kinto community will most definitely share different flavors of these services/features you can choose from which will be one-click deployable to the cloud of your choice. Leaving you with plenty of time to focus on your secret sauce algorithms for your new Twitter. Each Kinto microservice (KintoBlock) is made to support an unlimited amount of apps. So if all the up-voters are using the same authentication service, it's a much more affordable solution for the community to share functionality versus paying for individual hosting. We're also serverless first, so these services are online only when they are needed and scale to 1000's of nodes if demand is high. We've taken this question so seriously, that we built KintoHub itself with KintoHub! We plan to expose 100% of the tools we use to enable developers to build Twitter scale platforms. You can read more here: https://docs.kintohub.com/docs/t...

@codingcoop thanks for the great explanation. i will definitely explore it more now!

@peter_theill please try again and this should work.

@codingcoop awesome. Thanks. It works now. I'm looking forward to test it

@olga_ruban Thanks for the question! Yes, our pods scale based on load. Currently the scaling system is limited to CPU/Memory, but we preemptively spawn services so that when a service is in need, it takes a second to load versus waiting a minutes like on traditional auto scale systems. The next step will be to do it based on incoming load, such RPS/QPS algorithms describe (which I'm guessing you're talking about). Great read here which may tickle your interest. https://medium.com/netflix-techb... In the future, we will have features to fine-tune your scaling. Some use cases is that during high traffic periods, people like to keep reserve resources (let's say 20 CPUs) ready during 7-9PM. Otherwise, we can solve this with machine learning as well! We're investigating the best tools to provide you all as we discuss them in the Kinto community.

@cedricamaya Hey there! Thanks for the question! That's correct, we do not have any relation to Kinto Storage. We saw them after we came up with the name kintohub (originally we were thinking kintocloud), almost decided not to go along with it, but fell in love with it, especially since some of the team (mostly me) was addicted to Dragon Ball Super. Fun fact - Kinto is short for Kinto'Un which is Japanese for the flying nimbus that Goku rides. This cloud and Goku both go back deep into Chinese mythology where Wu Kong, The Monkey King, and has his magic cloud as well.