How to develop a website like Bittrex.com in java? Which libraries or third party api's will be used for cryptocurrencies (bitcoin/ethereum/etc)?
For faster response time which language is preferable for front-end and back-end.
If you are looking to develop a website to display current prices, graphs and integrate Shapeshift, you can try using the API provided by CoinCap and Shapeshift. They are pretty easy to use and also fast. I used it to develop plugin for my clients on WordPress and it works pretty well.
Related
I'm currently using Next.js for my front-end framework. I've been considering on using another javascript framework for my back-end, however it occured that me that existing CMS solutions like BigCommerce and Shopify exists.
I'm aware they have their own API reserved for developers, but from what I can see these are API usually made to develop tools and themes for other users on the platform itself. Is it possible that I can somehow leverage the power of these ecommerce CMS on my Next.js website? I don't know how these work because I've always seen them as softwares for non tech-specialists to build e-commerce without having the need to code. To know that an API for software exists is quite extraordinary
There's a lot that goes into building an e-commerce website, mainly the things that I am looking for is inventory management and supply chain management. Building these on top of a fullstack e-commerce website would take me too much time and goes beyond the constraint of the project. Do these API let you leverage their technology? But most importantly, do you have to pay a subscription fee to use their API as well as other features such as inventory management?
I am particularly interested in BigCommerce, because the Next.js commerce starter kit comes with BigCommerce integration out of the box (I'm not sure why they chose BigCommerce, as opposed to other CMS such as Shopify). Answers directly referring to BigCommerce are greatly appreciated.
The benefits and drawbacks of using an eCommerce CMS API can be pretty subjective. I have a large amount of experience with BigCommerce, and I can clarify with you that the BigCommerce API is used for much more than just building tools or themes for other BigCommerce users. I mostly see it used for custom integrations and extending the platform functionality.
Combining the API with your own back-end services can really give you unlimited possibilities in terms of functionality with the platform, especially where the platform may fall short in its native functionality. For example, if you feel like the store-credit system is lackluster natively - guess what? There are plenty of APIs that give you the potential to make your own store credit system and integration that suits your needs better.
To answer these questions:
Do these API let you leverage their technology?
The BigCommerce API has quite a bit of freedom in terms of which technologies you get to leverage. Pretty much every aspect of the platform has an API that can be used for your own needs.
Do you have to pay a subscription fee to use their API as well as other features such as inventory management?
There isn't any sort of subscription fee to use the BigCommerce API, and inventory management comes natively in the platform, as well as an API to manage your product inventory. There is also a large community of developers that have built apps for the platform that offer more advanced inventory management as well.
Whether or not you want to use the native BigCommerce functionality instead of a NextJS headless storefront all depends on your personal preference and goals. Using the built-in BigCommerce storefront is more simplistic and requires less development experience (if any at all), whereas if you wanted a headless storefront with BigCommerce using NextJS, this would ultimately give you more control, but would also require more coding/development knowledge.
I would like to create my own web chatbot and i like to integrate my app with wit.ai for natural language classification.I need to know how to integrate wit.ai service(through api call) with my application(any language in backend).i am using C# in front end.I have gone through the integration part Which posted in wit.ai website.But i don't know how to connect it .Could anyone send me a integration details little briefly
I think the short answer is its similar to how you would call any other APIs from your application server components. Wit exposes multiple APIs like message, speech and converse which you can call by passing the Authorization token and other payloads and make use of the API response in your application.
You can use message API if you are only interested in extracting
intent and other atributes of the sententense
Use speech for building voice based application and
Converse if you want to build a little more smarter app. Currently you can only pass text for converse APIs.Hoping they will introduce voice option for this soon.
Now to make things simpler, they have also provided SDKs in various languages like node-wit, pywit etc. So if you want to build your server side logic using on nodejs or python you can use these SDKs. The advantage is that you dont have to manage raw APIs calls and instead it is all managed by SDK. Also, other big advantage is that you can make use of runActions method which encapsulates converse API and make things simpler. If you want to build in nodejs then the messenger example is a good starting point. You can borrow all this logic/concept in your app and replace FB related calls etc with your custom bot. For Python you can look at the below link
https://github.com/wit-ai/pywit/pull/55
Also, you can explore the options like using other frameworks like botkit if you plan to integrate wit with other chatbots like FB messenger or slackbot as these frameworks provide more flexibility and ability to easily switch to different chatbots in future. But they don't seem to properly support the converse API of wit.
You are specifically looking for integration details. Since you are using c# for frontend app, natuarally the best option would be to use c# for backend as well. In which case you will be left with directly calling wit APIs from your backend as I think there are no SDKs in c#. If you want to make use of SDK in node or python etc then you will have to build a rest based backend (for example) which can be invoked from your c# application. I am currently working on a nodejs app and integrating it with wit using node-wit. I can share some code once its ready but i dont know when I will be able to finish it. For bootstrapping my application I have used this node application. If you have some understanding of node then you can look at the /server/controllers logic. Similar to this application I have built a witController which uses runAction to interact with wit and I am calling this from front-end when user submits a message to your bot. The biggest challenge in runAction is to figure-out a way to send back the wit response to your front-end and get follow up response from user. Wit sends the response in Send method as you can see in the node-wit's messanger example.
Hope this helps!
Anyone having trouble building API's with the new Kimono Desktop app. When I click create API the browser just stays on create API screen loading but nothing happens.
I even tried building an API that is the same as one I built when Kimono was still in business and no luck.
My existing api's still run and pull data fine.
Working just fine here.
Just a shot in the blue...did you install the new extension specifically for the desktop app? The old one can't work anymore since Kimono disabled the online service.
You can't build new APIs I think - only existing ones. :( Said something like it was not the acquiring company's policy to provide this publiclu available service but since they did not know how many businesses depended on their APIs they decided to allow existing APis to run.
You can also use their software for replace the online API. But it's an abandonware.
It's working great but on some website I can create new API because of an error.
I just find a possible (free) product that can replace Kimono : Datascraping.co.
They will include an REST FULL API within few days / weeks, as they said here.
It's a good software, but comparing to Kimono Desktop it's a little much more complicated.
Kimono got bought out and it's not working anymore.
Import.io is good but it kinda expensive for me. I've tried the free trial before but see the price starts from $249, so... https://www.import.io/standard-plans/
I don't have any progamming skills so I know very little about some web scraping frameworks like Scrapy.
You may want to look at this new web scraping software called Octoparse.
In case you want to know, here is the link:http://www.octoparse.com/
It takes a little time to begin. But they have rich tutorials on the website. Plus it doesn't require programming skills.
They provide cloud-based scraping service and API access.
You can use it to create API but you have to pay for the service. Free version doesn't have the API and cloud service.
I've been using it for 2 month with the Standard plan $89, which a lot cheaper than import.io. So far so good.
Hope it would be helpful for you.
I'm working on a project which involves a website, and after that is done, mobile applications (most probably will be built using a cross-platform tool like Phonegap or Sencha).
The overall application is heavily data-driven, all of which will be stored in MySQL databases on our webserver. I know that I will be setting up a REST API as a service layer for the mobile applications, but what I'm not sure about it - Should I be using this API for the main website as well?
I need to know this before I can begin the project, because if I do intend to eat my own dogfood, then the API will be the first priority.
In case it matters - the API will never be exposed to third party developers.
Sure, why not? It means that you'll have only one entry-point to test and monitor, it follows the DRY principle, and it will encourage better API design if you consume it too.
Yes you should use the API for the website. It simplifies your codebase and encourages code reuse, since you only deal with one API and not two (REST + MySQL). Furthermore, it makes life easier on the developers (that includes you!), because there is only one set of API calls to keep in mind at once.
Also, in the future you may build your mobile apps with HTML (perhaps using PhoneGap, recently open-sourced and renamed to Cordova). If your website uses the REST API, you can more easily port the web code to HTML5 for mobile.
Nitpick: This isn't really a matter of eating your own dogfood. Dogfooding typically refers to using pre-release code from the perspective of a user rather than a developer, to make finding bugs easier.
I am getting familiar with Google Sites. What I want is, building a Site front-end for a Google Spreadsheet.
I want to Display data from the Spreadsheet in the Google Site, later maybe some graphics as well. To my knowledge there are two ways to accomplish this, Apps Scripts and Gadgets. Building a Gadget seemed much more easy in the beginning, however gives me some trouble. After reading more about Apps Scripts I finally found a way to access the Spreadsheet and display data.
But reading a lot of google documentation, I wonder what really is the difference? In what cases should one use Gadgets and in what case Apps Scripts?
Maybe I am just a little overwhelmed but it would be nice to get some feedback from experiences developers in that field!
Thanks a lot.
Cheers,
Daniel
Google Apps Script is javascript, but run in server side. So it is not client side javascript like javascript Gadget or any HTML.
Google Apps Script use GWT, which generate client side Javascript.
Gadget is XML code containing HTML inside
which means gadget is text.
Google Apps Script is kinda JavaScript
which means GAS is code.
Might be the main difference.