Aslında yazının başlığı “Yayın Akışı Uygulaması iPhone’a Port Edildi” olacaktı ki Mart’ta Android uygulaması olarak çıkardığım bu uygulama hakkında daha önce blogda yazı yazmadığımı fark ettim. O zaman ikisini birden aradan çıkaralım. [caption id="" align=“alignright” width=“200” caption=“iOS sürümü”][/caption]
Oda arkadaşım Uğur, önceden geliştirdiğim Android için Yayın Akışı uygulamasını iPhone/iPad’e port etti. Oldukça güzel çalışıyor ve şirin görünüyor. Kendisinin kendi hesabından App Store’a yolladığı ilk app oldu. Onu da buradan tebrik edelim, **ücretsiz **uygulamayı indirmeyi ve oy vermeyi unutmayalım. :P
Biraz da teknik konulardan bahsedelim:
Android uygulamasını Mart’ta 2 günde yapıp 1 ayda market’e submit etmiştim.
Sistem ilk etapta Google App Engine altyapısını kullanıyordu, ta ki Google kızdırana kadar. Sonradan Heroku‘ya geçtik.
Server tarafı Java ile Play Framework üzerinde kodlandı, veritabanı için PostgreSQL kullanıyor.
As some of you may know Hazelcast is an open source distributed cache and distributed in-memory data structure storage for Java. It is developed by a small team in Turkey. It is kind of inspirational since it is a successful, mature and robust product and used by many large companies worldwide as a distributed caching solution. For those interested, source code is here.
Today, I asked a few questions that you might find interesting to Fuad Malikov, co-founder and developer of Hazelcast. Hope you enjoy.
**When did Hazelcast project begin, when was the first code written? **
Talip Ozturk started the project in the Spring of 2008 and the initial version had “distributed Queue” implementation. Later we implemented distributed Set, List, Map, Executor Service and Native Client etc. Read More →
For our new startup we looking for a good database that we can store schema-less data of different entities. Last year I had started reading the book MongoDB: The Definitive Guide but I ended up with stop reading since it didn’t sound much interesting. However one year later with more solid knowledge of database systems, it sounded cool.
First of all I started reading Bret Taylor’s article How FriendFeed uses MySQL to store schema-less data. What he does is to store entities as JSON objects in MySQL column and then manage indexes in separate tables to refer those JSON objects. Read More →
RSS guys might not have noticed, recently I have changed appearance of my blog to a minimalistic theme. Theme is named Cleanr and I have changed it a lot and open-sourced the changes. Removed sidebar, all those Facebook, Twitter etc buttons, GitHub and Google Reader badges, much more readable (especially for long posts).
Hope you liked it.
Older crappy themes of my blog: Read More →
The problem comes from the following story: You have an application that stores incoming data in a database. However someday you have noticed that your database schema is not quite well-designed or there was a problem with your computation all the time which you have just noticed. So how exactly you can migrate your existing data to your new database schema or calculate something with your fixed computation logic?
The answer is replaying the logs. What I would sug logic gest is, for every user action that affects your database, you should have a separate “log table” or “log file” which you can parse and replay very easily. It can help you to migrate our database or recover from serious application logic mistakes. I would call this an architectural pattern.
Let’s see how it may be helpful in a few cases: Read More →
We all know Google is full of talented engineers and great hackers, but it is not always the case about company strategy and marketing stuff. From a developer’s point of view, Google is very problematic about its cloud computing services strategy. Maybe I’m not an expert in this area but something is really obvious.
Google was one of the kick-starters of this cloud computing business. Google was doing everything today’s cloud sync services like Apple’s iCloud does in 2006 or so with Gmail, Google Calendar, Picasa etc. Those services are SaaS part of the cloud and it is for all users. Not so impressive. Then in 2006, Google came up with the idea of Google Apps, serving mails, calendars, chats on the cloud for companies, institutions and schools. It means almost nothing for a developer. 70% of companies with 500+ computers use Microsoft Exchange Server, so Google Apps share shouldn’t be that much, right?
Then Google developed bunch of developer tools, this time aimed developers, but again those services were not promising at all. I can count BigQuery, Cloud SQL, Cloud Storage, Prediction API and most important of all Google App Engine. Read More →