Zazler's unique architecture speeds up building mobile apps, JavaScript heavy interfaces and integrations by reducing amount of code and todo list. In team it reduces developers interruptions.
Zazler is webserver designed to work with relational databases and bring more value on client-side.

Read more

Understand Zazler

Get Zazler

Ubuntu
  wget http://www.zazler.com/beta/ubuntu/zazler_1.0-1_amd64.deb
  apt-get install libpq-dev libmysqlclient-dev libsqlite3-dev zlib1g-dev libncurses5-dev
  dpkg -i zazler_1.0-1_amd64.deb
  zazler
Debian
  wget http://www.zazler.com/beta/debian/zazler_1.0-1_amd64.deb
  apt-get install libpq-dev libmysqlclient-dev libsqlite3-dev zlib1g-dev libncurses5-dev
  dpkg -i zazler_1.0-1_amd64.deb
  zazler
Fedora
  wget http://www.zazler.com/beta/fedora/zazler-0.1.0.0-1.fc20.x86_64.rpm
  yum install zazler-0.1.0.0-1.fc20.x86_64.rpm
  zazler

Benefits of Zazler

Easy to start

Zazler is webserver and very easy to configure. That's why you can start using data in minutes.

Less code (if any...)

Traditional approach is develop all the SQL connection handling, authentication etc. And this can be needed for websites we have been building for years. But with data integration, mobile apps and javascript the situation is completly different. We need API.

Zazler has all basic functionality (connection handling, authentication etc) and it has API ready for you.

Shorter todo list

Environments where client has to a lot of requests backend have to be changed often, really often. And with every change API has to be changed.
Zazler takes another approach. It enables queries from client side but does it securly and in comfortable way. And on server side there can still be filter what data can be accessed and how.

With Zazler there are less communications between developers and in this case it is good because everybody can concentrate on their work.

Integration for different platforms

With API-s one main question is what is the format for data exchange?

Zazler approach is defferent: data is presented as table and then there is matter in what format it is. Any well known format like JSON, XML, HTML etc.

Integration can be not only with some specific client but also with RSS reader, google maps or any other platform. If Zazler is not prepared for some platform you can do it by yourself.

If you need more than table then it can be done faster than from scractch.

Integration with Excel

As Zazler supports XML, HTML and CSV export on-the-fly you are able to integrate your database with Excel in minutes.

Zazler documentation for integration

With Zazler you can give our documentation and your data source URL and you are done.

Compare Zazler with...

Model-View-Controller

Model - Usually is model main task to compile SQL and produce results.
Zazler makes it very easy to run SQL combining filters, authentication etc.

View - How data is presented; one data layout have one view usually
Zazler provides template language to create specific view. Although Zazler belives that it is up to client how consume data. So it provides many templates that are usable on the fly with any relational table in database.

Controller - To handle authentication, URL and stuff
Zazler want to provide flexibilty to client-side. Therefore there are standard URLs and expressions that Zazler can handle. You can drive data access and lot more from configuration.

SOAP

SOAP is Simple Object Access Protocl.

  • Zazler allows you to request data without writing any code. SOAP always needs coding.
  • Zazler can produce results for different clients (JSON, XML, HTML, RSS...) but with SOAP the client has to be also SOAP.
  • Zazler is client-friendly allowing to define query as needed and formatting results as needed. SOAP interface is fixed.